lab03 : Deliver Hello World, Plan for Retro, MVP

num	ready?	description	assigned	due
lab03	true	Deliver Hello World, Plan for Retro, MVP	Thu 01/31 04:00PM	Thu 02/07 07:00PM

What you need to finish TONIGHT

• Conduct a standup meeting (5-10 minutes)
• Choose a leader for next week’s sprint retrospective
  • Put the name of that leader in a card in the “TODO” column of your Kanban board, e.g. “Chris will lead team in first Retro”
  • Note, for full course credit, each of you needs to take a turn taking a leadership role in some activity.
  • If you don’t lead a retro, you’ll make a class presentation at some point.
• Review your deliverables for lab02
• Complete the sprint planning (generating user stories, issues) for a complete MVP that you can fully deliver by two weeks from tonight.
  • That MVP should go beyond a “hello world” and should deliver actual value to the end user

Choose the right size MVP!

You main task tonight is to adjust the user stories and issues that you want to include in the MVP.

There is more detail on how to do that below.

Conduct a standup meeting (5-10 minutes)

You are encouraged to conduct a standup meeting as a team.

Find a space in which to gather, standing in a circle, and answer three questions:

• What have you done since our last team checkin
• What are you working on now?
• Are there any barriers or blocks to your progress?

Direct your comments to the entire team (not to your mentor/TA/instructor, or a perceived peer team leader)

Suggestion: Set a timer for six minutes.

• If six minutes goes by and you are aren’t done, you are probably letting each member speak more than is ideal; try to focus just on answering the three questions.
• If there are issues that need to be discussed outside of standup, you are encouraged to NOTE THEM, and come back to them as a team AFTER standup.

Choose a leader for next week’s retrospective

Choose a leader for next week’s sprint retrospective. That sprint retrospective will take the entire lab period next week. Attendance at that lab is therefore particularly important.

• Put the name of that leader in a card in the “TODO” column of your Kanban board, e.g. “Chris will lead team in first Retro”

Note, for full course credit, each of you needs to take a turn taking a leadership role in some activity.

• If you don’t lead a retro, you’ll make a class presentation at some point.
• So you are encouraged to volunteer.
• Once you’ve led one retro, you’ll have fulfilled your duty to exercise leadership at least once.

Review committment to attendance and team norms

Note to each individual: If you cannot be at next week’s retro in person, discuss this with your team.

Teams generally understand that members may occasionally need to miss a single activity now and then. It is helpful to balance unavoidable occasional absences with renewed commmitment to team goals.

Any time you miss a team activity, you may want to consider making a special committment to be sure that you are present for other team activities in the future. Review your team’s norms in this regard.

Checking over your deliverables for lab02

Look at the green “Graded” boxes in the instructions for lab02 and review the due date for that lab. Tonight is likely your last oppportunity to get things together before the grading of those deliverables begins.

MVP Planning

To help your team (as well as your instructional staff) know what you are defining as part of your MVP—which you are delivering two weeks from today , we are asking you to do things process/tool wise:

• Create a new column on your Kanban board.
  • Call it MVP, and put everything (in terms of user stories and issues) from the TODO column that is part of MVP into that column.
  • Leave everything that is NOT part of MVP in the TODO column.

In addition, issues on Github can have tags. Github creates some predefined tags, but can edit these and add new ones.

• Add a new tag called MVP.
  • Add that tag to all of the issues that are in the MVP column, as well as any issues that are already in-progress or done that are part of your MVP.

Finally, while regular cards cannot be given “tags” in the same way that issues are, you can just use the letters (MVP) in parens as a kind of tag on the user stories that are part of your MVP.

In this way, anyone can look at your Kanban board, and see:

• What is, and what is not part of your MVP
• Which user stories and issues are still not started, in progress, or done, with respect to your MVP.

Deliverables and Grading for lab03

By the end of due date of this assignment (i.e. Thu, Feb 07 at 7:00PM), you should be halfway done with delivering a significant number of issues towards your MVP.

Here’s what we’ll be looking for and grading: