3 of 25

Design Team Member Names:

Team Roles and Norms

As a team, discuss what roles are important for the success of your design task and assign the roles to the members.

List the norms that you want your team to follow during the whole design process.

Team Norms:

Write Norms for working together
Remember our group Norms

Role	Team Member
Lead Designer Interview the user, inform the engineers and programmers to users, interface back with the user, lead design brainstorming, provide feedback for prototypes
Lead Engineer Work with the designer to make something that will actual work, identify the actions and technology needed for the design, process maps the actions
Lead Programmer Create the code to use the technology and program any actions, process map the code
Lead Communicator Interview the user, Run Kanban Board, check on tasks, make sure everyone is documenting and communicating, lead on the design pitch and progress presentations
Whole Group Construct prototypes

D2A4 S

4 of 25

Empathize: Get to know your product users

Interview your mentor to get information about your design plan.

Choose a mentor who is working for a company focusing on designs like yours.

Design Team Member Names:

Design Attributes

What are the attributes of your design?

Looks:

Size:

Emotions (if any):

Movements (if any):

Sounds (if any):

How can the users interact with the design (if possible)?

Get to know the intended users

Who are the intended users of your design?

What are the needs of the users?

Purpose of the design

What is the purpose of your design?

How will your design help the intended users (if applicable)?

D3A2 S

5 of 25

User Problem Statement: *User* needs a way to…..

Which Micro:bit inputs and features do you need to use? (Buttons, LEDs, Accelerometer, etc.)

What are the required tools and materials needed for the project? (Add-ons to Micro:bit: Servo motors, external buttons, sensors, lights, paper, tape, etc.)

Are there any constraints to the design based on resources?

Are there any other details you need to ask the mentors about the design materials and constraints?

Design Team Member Names:

Define: Set design criteria for the product

D3A2 S

6 of 25

Design Team Member Names:

Ideate: Brainstorm initial designs

Draw 4 versions of what your design could look like based on the interviews. Label the parts of the design.

Draw what each of the actions (sensors, movements, etc.) will look like. Note in the drawing which inputs would start each of the actions.

Brainstorm a few names for your product:

D3A2 S

7 of 25

Ideate Mentor Feedback: Get feedback from your mentor or teacher. Identify and make any design changes after the feedback.

What I like about the design

Questions I have about the design

What I do not like about the design

I want the creator to know…

For Design Group - Identify Refinements

What I agree with about the feedback:

What I disagree with about the feedback:

What is going to change about the design in the next version:

D3A2 S

Test and Refine: Feedback to make refinements

8 of 25

Ideate Peer Feedback: Get feedback from another design group. Identify and make any design changes after the feedback.

What I like about the design

Questions I have about the design

What I do not like about the design

I want the creator to know…

For Design Group - Identify Refinements

What I agree with about the feedback:

What I disagree with about the feedback:

What is going to change about the design in the next version:

Test and Refine: Feedback to make refinements

D3A2 S

9 of 25

Prototype: Build and test different designs

PROTOTYPE 1

Design Team Member Names:

D3A2 S

Instructions:

Grab a blank sheet of paper and label it: PROTOTYPE 1 with your name at the top
Create 2 process maps for the (1) ACTIONS of the Micro:bit and the (2) CODE you are going to use to create the design. Label the process maps.
Begin building a prototype of your design based on the ideas you came up with in the ideate stage.
Add any additional resources you may have used to the DEFINE page of the design plan.
Answer the questions on the REFINEMENT page to track the changes in your design

Actions Process Map

Code Process Map

Example Paper

Names

Prototype 1

10 of 25

Prototype 1 Mentor Feedback: Get feedback from your mentor or teacher. Identify and make any design changes after the feedback.

What I like about the design

Questions I have about the design

What I do not like about the design

I want the creator to know…

For Design Group - Identify Refinements

What I agree with about the feedback:

What I disagree with about the feedback:

What is going to change about the design in the next version:

D3A2 S

Test and Refine: Feedback to make refinements

11 of 25

Prototype 1 Peer Feedback: Get feedback from another design group. Identify and make any design changes after the feedback.

What I like about the design

Questions I have about the design

What I do not like about the design

I want the creator to know…

For Design Group - Identify Refinements

What I agree with about the feedback:

What I disagree with about the feedback:

What is going to change about the design in the next version:

Test and Refine: Feedback to make refinements

D3A2 S

12 of 25

Refinement: Making and tracking changes to the design

D3A2 S

Stage	What stayed the same from your previous design? How does it support the problem statement?	What changed from your previous design? How does it support the problem statement?
Ideate to Prototype 1	>	>
Prototype 1 to Prototype 2	>	>
Prototype 2 to Final Design	>	>

13 of 25

Present your User Problem Statement and users
Show and demonstrate your prototype
When presenting, show and explain the following:

The actions process map showing your prototype’s intended function.
The program (codes and sequence) on your MakeCode editor.
How your designs changed from ideate to prototype 1
What are your next steps?

Move the sticky notes on the Kanban board to show where you are on your Design Challenge and what needs to be done to complete it.

Progress Check In: Present Prototype 1

Design Team Member Names:

Present your prototype to the whole group. Use the following to guide your presentation.

14 of 25

What I like about the design

What I have questions about

Set Up on Chart Paper

15 of 25

Prototype: Build and test different designs

PROTOTYPE 2

Design Team Member Names:

D3A2 S

Instructions:

Grab a blank sheet of paper and label it: PROTOTYPE 2 with your name at the top
Create 2 process maps for the (1) ACTIONS of the Micro:bit and the (2) CODE you are going to use to create the design. Label the process maps.
Begin building a prototype of your design based on the ideas you came up with in the ideate stage.
Add any additional resources you may have used to the DEFINE page of the design plan.
Answer the questions on the REFINEMENT page to track the changes in your design

Actions Process Map

Code Process Map

Example Paper

Names

Prototype 2

16 of 25

Prototype 2 Mentor Feedback: Get feedback from your mentor or teacher. Identify and make any design changes after the feedback.

What I like about the design

Questions I have about the design

What I do not like about the design

I want the creator to know…

For Design Group - Identify Refinements

What I agree with about the feedback:

What I disagree with about the feedback:

What is going to change about the design in the next version:

D3A2 S

Test and Refine: Feedback to make refinements

17 of 25

Prototype 2 Peer Feedback: Get feedback from another design group. Identify and make any design changes after the feedback.

What I like about the design

Questions I have about the design

What I do not like about the design

I want the creator to know…

For Design Group - Identify Refinements

What I agree with about the feedback:

What I disagree with about the feedback:

What is going to change about the design in the next version:

Test and Refine: Feedback to make refinements

D3A2 S

18 of 25

Prototype: Build and test different designs

Final Design

Design Team Member Names:

D3A2 S

Instructions:

Grab a blank sheet of paper and label it: Final Design with your name at the top
Create 2 process maps for the (1) ACTIONS of the Micro:bit and the (2) CODE you are going to use to create the design. Label the process maps.
Begin building a prototype of your design based on the ideas you came up with in the ideate stage.
Add any additional resources you may have used to the DEFINE page of the design plan.
Answer the questions on the REFINEMENT page to track the changes in your design

Actions Process Map

Code Process Map

Example Paper

Names

Final Design

19 of 25

Design Team Member Names:

Present your plan for your final design to the whole group. Use the following to guide your presentation.

Progress Check In: Present Final Design Plan

Present your User Problem Statement and users
Show and demonstrate your prototype
When presenting, show and explain the following:

The actions process map showing your prototype’s intended function.
The program (codes and sequence) on your MakeCode editor.
How your designs changed from Prototype 1 to prototype 2 to Final Design
What are your next steps?

Move the sticky notes on the Kanban board to show where you are on your Design Challenge and what needs to be done to complete it.

D3A2 S

20 of 25

Progress Check In: Present Final Design Plan

Jigsaw – Each member of your design group will break off into a new group. You will represent your design group in your new small group. Each design group representative will present their design update and receive feedback.

What I like about the design

What I do not like about the design

Questions I have about the design

What I like about the design

What I do not like about the design

Questions I have about the design

What I like about the design

What I do not like about the design

Questions I have about the design

What I like about the design

What I do not like about the design

Questions I have about the design

D3A2 S

Printed

21 of 25

Create Pitch Presentation with your design team
Create a 5-minute pitch presentation to showcase their final design. They will use the following points as a guide for their presentation. Each student will be assigned one of the talking points below:

Introduce the problem statement, Introduce the Product: Name, the users, the purpose (Communicator)
How does your product meet the user’s needs? Demonstrate what your final product can do. (Designer)
Explain how the designs changed from the ideate, prototype stages 1 and 2, and the final design? (Engineer)
What was the biggest challenge or barrier your group had to overcome while moving from ideas on paper to a final product? (Programmer)
What could be improved about the product? (Communicator)

We will then hold a “pitch competition” where each design team will present their design products and receive votes.

Present Final Design

Design Team Member Names:

Present your final design to the whole group. Use the following to guide your presentation.

Design Name: _______________

D3A2 S

22 of 25

Final Design Presentation Rubric Chart

Product Name:
Category	Rating 1-5 (1 lowest, 5 highest)
The final product has a clear purpose.
The final product meets the users needs.
There was a clear progression in product design from each of the design stages. (Ideate, Prototype 1, Prototype 2, Final Design)
The design team was able to identify and explain how they overcame a barrier in the design process.
The design team had a firm understanding of where future improvements could be made.
The pitch presentation was organized and easy to understand.
Total Points	______/30 points

D3A2 S

23 of 25

Deisgn Group Kanban Board.

Team members decide which tasks are assigned to who and create sticky notes for each task and place them under To Do column.
At the end of each day, each member moves the sticky notes to the corresponding column.

Name	To Do	In Progress	Testing & Refining	Complete
Johnny
Sally

Task 1

Task 2

Task n

Task 1

Task 2

Task n

24 of 25

Whole Group Kanban board.

At the end of each day, students will move sticky notes containing specific tasks to the corresponding stage of the design process.

Interview mentor.

Define design criteria.

Brainstorm about design ideas.

Talk to mentor about design ideas and get feedback.

Talk to another group about design ideas and get feedback.

Build and test prototype 1.

Talk to mentor about prototype 1 and get feedback.

Talk to another group about prototype 2 and get feedback.

Build and test prototype 2.

Talk to mentor about prototype 2 and get feedback.

Talk to another group about prototype 2 and get feedback.

Present prototype 1.

Present prototype 2.

Build and test final design.

Talk to mentor about final design and get feedback.

Talk to another group about final design and get feedback.

Present final design.

Sample sticky notes to provide to students.

25 of 25

Design Rubric

	Capstone	Milestones		Benchmark
	4	3	2	1
Empathize
Define Design Criteria	Demonstrates the ability to construct clear and accurate design criteria with evidence of all relevant factors including design users, purpose, attributes and requirements to build the design.	Demonstrates the ability to construct clear and accurate design criteria with evidence of most, but not all relevant factors including design users, purpose, attributes and requirements to build the design	Begins to demonstrate the ability to construct clear and accurate design criteria with evidence of all relevant factors, but design requirements are incomplete.	Demonstrates a limited ability in constructing design criteria or defining relevant factors.
Identify and Propose Design Ideas	Proposes one or more design ideas that indicates a deep comprehension of the needs of the user.	Proposes one or more design ideas that indicates a superficial comprehension of the needs of the user.	Proposes one design idea that is “off the shelf” rather than individually designed to address the specific needs of the users.	Proposes a design idea that is difficult to evaluate because it is vague or only indirectly addresses the needs of the users
Test and Refine Design	Evaluation of design is deep and elegant (for example, contains thorough and insightful explanation) and includes, deeply and thoroughly, all of the following: user needs, reviews feedback from mentor and peers, examines doability of solution, and weighs impacts of solution.	Evaluation of design is adequate (for example, contains thorough explanation) and includes the following: user needs, reviews feedback from mentor and peers, examines doability of solution, and weighs impacts of solution.	Evaluation of design is brief (for example, contains thorough explanation) and includes some of the following: user needs, reviews feedback from mentor and peers, examines doability of solution, and weighs impacts of solution.	Evaluation of design is superficial and lacking explanation of one or more of following: user needs, reviews feedback from mentor and peers, examines doability of solution, and weighs impacts of solution.
Final Design Presentation/Implementation	Presents and desmonstrates the final design in a manner that addresses thoroughly and deeply multiple factors including all fo the following: user needs, reviews feedback from mentor and peers, examines doability of solution, and weighs impacts of solution.	Presents and desmonstrates the final design in a manner that addresses thoroughly and deeply multiple factors including some of the following: user needs, reviews feedback from mentor and peers, examines doability of solution, and weighs impacts of solution.	Presents and desmonstrates the final design but ignores relevant contextual factors such as user needs, reviews feedback from mentor and peers, examines doability of solution, and weighs impacts of solution.	Did not present nor demonstrate the final design.