2 of 62

Process Mapping

Morning Routine

Alarm

Wake Up

Turn Off Alarm

Start Day

Check Phone

Go to bathroom

Brush teeth

Get Breakfast

What do you notice about this process map?

What do you see? What do you think it means?

Are there any patterns?

D1A2.1 S

3 of 62

Process: A sequence of activities intended to produce particular results

Steps to Building a Process Map

Identify the process
Determine the boundaries: inputs (start) and outputs (end)
Start with the big picture steps
Add in the details: Actions, Decisions and Questions, Relationships to map flow
Complete the ENTIRE map before refining
Assess the map for improvement areas: Ask questions and make notes to locate possible problem areas
Get feedback from peers or users

Map the process to make a PBJ sandwich

Name:

Process Mapping

Inputs

Outputs

Decisions

Actions/

Steps

Process Map Key

The start of your process

The end result of your process

The steps in the process: how to get from the start to the end

Questions or choices that can change the flow of the process

Show the direction of the steps in the process

D1A2.1 S

4 of 62

Jelly

Print & cut these to use to help students map their process

D1A2.1 S

5 of 62

Name & Icon Badge

Look at the code blocks under the “Basic” section of MakeCode. Identify which code blocks you think you would use and the order you would put the block in to match the process map

Inputs

Outputs

Decisions

Actions/

Steps

Process Map Key

The start of your process

The end result of your process

The steps in the process: how to get from the start to the end

Questions or choices that can change the flow of the process

Show the direction of the steps in the process

Forever

Show Name

Show Icon

Name & Icon Badge

Pause

Clear Screen

D1A2.2 S

6 of 62

Name & Icon Badge

Look at the code blocks and identify which code blocks and the order to match the process map

Press Button A

Show Name

Play Song

Name & Icon Badge

Show Icon

Which

order?

Flash Icon (Loop)

Show Icon

Flash Icon

(Loop)

Play Song

Press Button B

Stop all sounds

Silent Name Badge

D1A2.2 S

7 of 62

Name & Icon Badge

Explore the different types of code in MakeCode.

Which blocks of code would you use to…

Display your name?

Display the icon?

Play sound or music?

Repeat code?

Make the icon flash?

D1A2.2 S

8 of 62

Logic

Let’s talk through examples of Logic. This is how computers are programmed to make decisions based on different inputs or conditions.

We are going to talk about Ice Cream.

IF/THEN

One action to happen in response to an input

Set Ice Cream to 1

Happy

Have Ice Cream

IF Ice Cream = 1

THEN

If Ice Cream = 1

D1A2.3 S

9 of 62

Logic

Let’s talk through examples of Logic. This is how computers are programmed to make decisions based on different inputs or conditions.

We are going to talk about Ice Cream.

IF/ELSE

Is for two actions to happen depending on the input

Have Ice Cream

Happy

Sad

IF Ice Cream = 1

THEN

Set Ice Cream to 1 or 0

ELSE

Ice Cream = 0

THEN

If Ice Cream = 1

If Ice Cream = 0

D1A2.3 S

10 of 62

Logic

IF/ELSE IF/ELSE

Is for options of 3+ actions to happen depending on the input

Happy

Upset Stomach

Sad

Set Ice Cream =

0, 1, or 2

Have Ice Cream

IF Ice Cream = 1

THEN

ELSE IF

Ice Cream = 2

THEN

ELSE

Ice Cream = 0

THEN

If Ice Cream = 1

If Ice Cream = 0

If Ice Cream = 2

D1A2.3 S

11 of 62

Troubleshooting and Debugging

Code

Compare the actions process map and the given code to find the bug. Can you find the bug before seeing the code on the Micro:bit?

Actions Process Map

Show a Random Number 1-10

Forever

ELSE

THEN

IF Button A is Pressed

Show A Number

Show

“Hold A”

Show Button Command

Clear Screen

Pause 1 Second

D1A2.4 S

12 of 62

Troubleshooting and Debugging

Compare the actions process map and the given code to find the bug. Can you find the bug before seeing the code on the Micro:bit?

Code

Actions Process Map

On Shake

ELSE

IF Input ≤ 5

THEN

Play Joke Music

Set Input to pick random number 0-10

Show Number

Input

Pause 3 second

Play Scary Music

Show Number

Input

Pause 3 second

D1A2.4 S

13 of 62

Troubleshooting and Debugging

Create a simple code to with a bug for your partner to find. Make a process map of the actions your code is supposed to do. Code your program in MakeCode then switch code with your partner. Can you find the bug before you partner? Can you fix the code so it runs correctly?

Code

Actions Process Map

Make a bug. Find a bug. Fix the bug.

D1A2.4 S

14 of 62

List some situations that you think could be solved with the help of computers.	Would finding a solution to this problem help the world?	Would finding a solution to this problem help your local community?	Would finding a solution to this problem help you or your family?	Do you think the problem is solvable?

Map a process to solve one of the problems you listed above

Name:

Problem Solving

D1A2 S

15 of 62

Rock Paper Scissors

Process Mapping

Review the process map for the ACTIONS we created for the Micro:bit to play Rock, Paper, and Scissors.

Recall the process map symbols
What is the input? What is the output?
Which actions do you think need to happen to get the end result?

Create a process map for the CODE you will need to make the actions happen

What kinds of code blocks will you need?
What kind of input do you want use to start the game?
What is the sequence the code needs to run in?
How could you use Logic to make different actions happen based on different inputs?

Program Requirements

Micro:bit needs a countdown to start playing the game – just like you say “Rock, Paper, Scissors, Shoot!”
Micro:bit needs to randomly choose between Rock, Paper, or Scissors
Micro:bit needs to display an icon for Rock, Paper, or Scissors
Micro:bit needs an input to know when to start the game

Add More to the game!

Micro:bit needs to have at least one of the following:

Different number of flashes for each of the Rock, Paper, or Scissor icons
Play different tones for Rock, Paper, or Scissors
Display different lights or flashes of lights for Rock, Paper, or Scissors

Code It!

Use the MakeCode editor to map out code to play rock, paper, and scissors.
Test your code periodically using the simulator or Micro:bit to identify any bugs or test your sequence.

Pick Random

Rock, Paper, Scissors

Shake to Start

Show Different Icons

Play Rock, Paper, Scissors

Actions Process Map

Show Countdown to start game

D1A3.1 S

16 of 62

Rock Paper Scissors

Process Mapping

Review the process map for the ACTIONS needed for the Micro:bit to play Rock, Paper, and Scissors.

Recall the process map symbols
What is the input? What is the output?
Which actions do you think need to happen to get the end result?

Create a process map for the CODE you will need to make the actions happen

What kinds of code blocks will you need?
What kind of input do you want use to start the game?
What is the sequence the code needs to run in?
How could you use Logic to make different actions happen based on different inputs?

D1A3.1 S

17 of 62

Data Collection

Background

Light intensity (lux) is determined by how much light (lumens) there is within a certain area (m²).

Model

Look at the model of the light:

Is the brightness of the light the same at points A, B, and C distance away from the source?

Why do you think it is the same or different?

Can you use an example from real life?

Automatic Light

D1A3.2 S

18 of 62

Data Collection

Clear Screen

On Push Button A

Show Number Level

Collect Light Intensity Data

Plot bar graph of Level up to 255

Set “Level” to Light Level

Pause

Process Map

Automatic Light

Code 1

Code 2

D1A3.2 S

19 of 62

Data Collection

Automatic Light

Instructions: Experiment with collecting data using the light sensor in the Micro:bit.

Each of you will program your Micro:bit to measure light intensity. Each of you will take turns measuring light intensity for 5 different distances. Distances = 2in, 4in, 6in, 8in, 10 in

You will each cycle through the roles to support your groupmates: (1) Programmer, (2) Data Collector, (3) Data Recorder

The Programmer builds the program to collect their light intensity data using their Micro:bit. The programmer will collect their data with the support of their group members.

Data Collection Steps:

Programmer stands at the first location and shines the flashlight at the LED screen of the Micro:bit where the sensors are. This is important for an accurate measurement.
The Data Collector will Push A to collect light intensity when the Programmer is ready
The Data Recorder will write down the light intensity reading from the Micro:bit in the data table
Repeat steps 1-3 for the remaining distances. When finished the programmer will download their data from the Device Console in Micro:bit

Students will rotate roles and Repeat steps 1-4 until all students have collected and exported their own light intensity data
After the data is collected and exported, each student will import the data into a spreadsheet program: Google Sheets or Excel. Google Sheets, Open New Sheet, File, Import, Select Data from downloads, import data
Then you will need to rename the Time readings to their respective distances

When exporting data from Micro:bit the data is saved as time and light intensity
The times are affiliated with the different distances the students stood at

Rename the Columns to Distance (Column A) and Light Intensity (Column B)
Create a chart to display the data using a line graph
EACH student will explore the relationship between distance and light intensity from their data that they graphed

Questions (answer on next slide):

Does light intensity increase or decrease with distance?
What is the mathematical relationship between light intensity and distance from your plot?

D1A3.2 S

20 of 62

Data Collection

Distance	Time	Light Intensity
2 inches
4inches
6 inches
8 inches
10 inches

Automatic Light

Programmer 1

Programmer 2

Distance	Time	Light Intensity
2 inches
4 inches
6 inches
8 inches
10 inches

Programmer 3

Distance	Time	Light Intensity
2 inches
4 inches
6 inches
8 inches
10 inches

D1A3.2 S

21 of 62

Data Collection

Automatic Light

Programmer

Does light intensity increase or decrease with distance?

(2) What is the mathematical relationship between light intensity and distance from your plot?

D1A3.2 S

22 of 62

Design Challenge: Micro:bit Pet

23 of 62

Design Plan – Micro:bit Pet

Design a Micro:bit Pet

Empathize: Get to know your product users

Before you start designing a Micro:bit pet, you need to learn what its future owner would like in a robot pet. Interview your partner to learn about the kid of pet they would like to have designed for them.

What kind of pets does your partner want? (an Animal? Insect?)

What are the attributes they would like in their pet?

Looks:

Size:

Emotions:

Movements:

Sounds:

How does the owner want to interact with their pet?

Designer Name:

Pet Owner Name:

D2A2 S

24 of 62

User Problem Statement: *Pet Owner Name* needs a pet that…..

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: buttons, lights, paper, tape, drawing tools, etc.)

Are there any constraints to the design based on resources?

Are there any other details you need to ask the other team about for their pet?

Design Plan – Micro:bit Pet

Design a Micro:bit Pet

Define: the design criteria for the product

Designer Name:

Pet Owner Name:

D2A2 S

25 of 62

Draw 4 versions of what the Micro:bit pet could look like based on the interview. Label the parts of the pet.

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

Design Plan – Micro:bit Pet

Design a Micro:bit Pet

Ideate: Brainstorming the initial design

Designer Name:

Pet Owner Name:

D2A2 S

Printed

26 of 62

Group Leader Checkpoint: Get feedback from another group leader in the room. 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:

Design Plan – Micro:bit Pet

Design a Micro:bit Pet

Test and Refine: Feedback from users to make refinements

Designer Name:

Pet Owner Name:

Group Leader Name:

D2A2 S

27 of 62

Ideate User Feedback: Get feedback from your partner (the user). Make any design changes after the feedback.

Design Plan – Micro:bit Pet

Design a Micro:bit Pet

Test and Refine: Feedback from users to make refinements

Designer Name:

Pet Owner Name:

Feedback Partner Name:

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:

D2A2 S

28 of 62

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 pet and the (2) CODE you are going to use to create the pet. Label the process maps.
Begin building a prototype of your Micro:bit pet based on the design 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

Design a Micro:bit Pet

Prototype: Building and testing different designs

PROTOTYPE 1

Design Plan – Micro:bit Pet

Actions Process Map

Code Process Map

Example Paper

Name

Prototype 1

D2A2 S

29 of 62

Prototype 1 User Feedback: Get feedback from your partner (the user). Make any design changes after the feedback.

Design Plan – Micro:bit Pet

Design a Micro:bit Pet

Test and Refine: Feedback from users to make refinements

Designer Name:

Pet Owner Name:

Feedback Partner Name:

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:

D2A2 S

30 of 62

Design Plan – Micro:bit Pet

Design a Micro:bit Pet

Refinement: Making and tracking changes to the design

Designer Name:

Pet Owner Name:

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	>	>

D2A2 S

31 of 62

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 pet and the (2) CODE you are going to use to create the pet. Label the process maps.
Begin building a prototype of your Micro:bit pet based on the design 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

Design a Micro:bit Pet

Prototype: Building and testing different designs

PROTOTYPE 2

Design Plan – Micro:bit Pet

Actions Process Map

Code Process Map

Example Paper

Name

Prototype 2

D2A2 S

32 of 62

Prototype 2 User Feedback: Get feedback from your partner (the user). Make any design changes after the feedback.

Design Plan – Micro:bit Pet

Design a Micro:bit Pet

Test and Refine: Feedback from users to make refinements

Designer Name:

Pet Owner Name:

Feedback Partner Name:

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:

D2A2 S

33 of 62

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 pet and the (2) CODE you are going to use to create the pet. Label the process maps.
Begin building a prototype of your Micro:bit pet based on the design 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

Design a Micro:bit Pet

Prototype: Building and testing different designs

Final Design

Design Plan – Micro:bit Pet

Actions Process Map

Code Process Map

Example Paper

Name

Final Design

D2A2 S

34 of 62

Create a flyer advertisement using Word or PowerPoint to showcase the pet you designed for adoption.
The advertisement has to have the following information:

Description

A written description of the Micro:bit pet to create vivid images for the reader.

Use facts, specific information that can be proven, in the description.

Describe how to interact with the pet

Which inputs to use

Special Attributes and Features

Provide an example of something you think people would want to know about your Micro:bit pet.
Write an explanation to connect the design of your pet to the wants and needs of the users.

Picture

Image of your Micro:bit Pet

Personal Story

Write a personal anecdote, a short story, about an experience you have with the Micro:bit pet.

AFTER you create the flyer for the Micro:bit pet you designed, present your advertisement for the Micro:bit pet.
The presentation should include you talking about:

Introduce the problem statement
Introduce the Micro:bit pet

Description of the pet
How to interact with the pet
Special attributes

Why you should adopt this pet

A personal story/anecdote

How it met the owner’s wants and needs
A challenge you had to overcome when designing the pet from ideas to real-life

Adoption Advertisement

D2A2 S

35 of 62

Description

Write a description of the Micro:bit pet to create vivid images for the reader.
Use facts, specific information that can be proven, throughout the description.

How to interact with the pet

Which inputs to use

Personal Story

Write a personal anecdote, a short story, about an experience you have with the Micro:bit pet.

Picture

Special Attributes and Features

Provide an example of something you think people would want to know about your Micro:bit pet.
Write an explanation to connect the design of your pet to the wants and needs of the users.

Adoption Advertisement

Pet Name:

___________________

D2A2 S

Set Up on own PowerPoint slide

36 of 62

COMMUNICATE

Using the Bluetooth function (radio) of the Micro:bit, work with a partner to have your Micro:bit pets talk with each other.

Things to consider:

Need to have matching radio numbers (provided by group leader)
Need to send “strings” as inputs for different actions
Process map your actions and codes
Add loops and logic to support your actions

Micro:bit Pet Talk Process Map

Actions

Code Essentials:

Hear message from other radio

Push Button

Message sent

Audio sends to other radio

Talk into Radio

Design a Micro:bit Pet

Extend Challenge: Design a way for your Micro:bit pets to communicate, move, or sense its surroundings

Design Plan – Micro:bit Pet

Designer Name:

Pet Owner Name:

D2A3 S

37 of 62

MOVEMENT

Using a Servo Motor program the Micro:bit to move when commanded.

Things to consider:

Servo Motor write locations are 0-360
Wire the Servo correctly
Make sure you are programming the correct pin
Servo Motors work best in Pins 0-3

Micro:bit Pet Move Process Map

Actions

Code

Reset

Push Button (Input)

Action Complete

Motion 2

Motion 1

Design a Micro:bit Pet

Extend Challenge: Design a way for your Micro:bit pets to communicate, move, or sense its surroundings

Design Plan – Micro:bit Pet

Designer Name:

Pet Owner Name:

D2A3 S

38 of 62

SENSOR

This sensor is built into the Micro:bit and detects when the Micro:bit experiences different types of motion.

Things to consider:

Check the threshold and direction of the accelerometer sensor

Micro:bit Pet Movement Process Map

Actions

Code

Else: be happy

Input

(Movement)

Senses and reacts to motion

Show Reaction

Design a Micro:bit Pet

Extend Challenge: Design a way for your Micro:bit pets to communicate, move, or sense its surroundings

Design Plan – Micro:bit Pet

Designer Name:

Pet Owner Name:

D2A3 S

39 of 62

Group Design Challenge

40 of 62

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

41 of 62

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

42 of 62

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

43 of 62

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

44 of 62

Ideate Mentor Feedback: Get feedback from your mentor or the user. 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

45 of 62

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

46 of 62

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

47 of 62

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

48 of 62

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

49 of 62

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	>	>

50 of 62

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.

Presentation

51 of 62

What I like about the design

What I have questions about

Set Up on Chart Paper

52 of 62

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

53 of 62

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

54 of 62

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

55 of 62

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

56 of 62

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

Presentation

57 of 62

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

58 of 62

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

59 of 62

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

60 of 62

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

61 of 62

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.

62 of 62

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.