Testing and making experiments to validate core ideas is what you do to make sure the requirements you are aiming for are the right requirements. This basically means making sure that you are doing the right thing. Once you have scoped your project to decide how your next release will be, what features will have, what architecture, design and specifications based on your validations, the idea is that you commit to a set of features.
Goal of the week
- Learn to prioritize and scope releases
- Plan and start running a sprint based on your defined priorities
Tip: Scope a sprint that you can run in 2-4 weeks
Assignments
- Define the scope statement for your participation in the program
- Prioritize your work based on feasibility and relevance, using the github project board
- Decompose your test cards in achievable activities in a timeline (or tasks)
- Move these tasks into the sprint backlog planning.
- If you have new hypothesis and ideas update your canvas. What would you do to validate these ideas, what experiments would you design?
Tip: It is possible that two test cards require several steps that you might want to break down into separate issues and assign them to different people in your team.
| Tools | Use it for | Examples & tutorials |
| Program schedule | Define what you will and will not be able to deliver by the end of the program, within the big picture of your project. | MicroNugget: What is the Project Scope Statement for Project Managers? |
| Scrum board setup | Use it to timebox and decide what you are going to work on and prioritize in your first sprint (You don’t have to fully follow the scrum rituals, but is good to use it as a reference to scope and timebox your project) | Scrum in 10 minutes |
| Github Project board | Use it to plan your sprint and let people know what you are working on, move your issues in the board to sprint backlog | Github Project Management |