first sprint in Scrum- what is expected??
Before launching a project, organization need to include a first cut as per the below list:
Scrum is about managing the development of a project after it has been defined, reviewed, budgeted and launched. Every sprint includes refining all the information that is listed above in light of what has been learned the previous sprint. The first sprint is a special case because there are no previous sprints for people to have gained a shared understanding and learn some things that refine that understanding.
So, the first sprint has much more review work that the others, but it should still deliver some working software. If the first sprint does not deliver any working software to prime the feedback pump, then it is not a sprint at all, but instead a kickoff, JAD session or whatever that is part of the launching process rather than the development process.
- Product vision
- Product roadmapping
- Feature selection (feasibility, WSJF-Weighted Shortest Job First, etc)
- Story mapping / initial product backlog
- MoSCoW / slicing / MVP
- High level architecture
- Technology stack selection
- Risk management (starting with identification)
- Some UX/UI as this needs to work a bit ahead of "coding"
- Test strategy
- Tool selection (CI, testing, build, code analytics etc)
- Scrum Team definition
- Skill gap identification + training / coaching plan
- Stakeholder Management (starting with identification)
- 1 pager Scrum Team charter + social contract
- User feedback strategy
- (outside) dependency management (starting with identification)
- PBR that makes the product backlog ready for sprint 1
- How to deal with (enterprise) governance
- Strategy for distribution / scaling + tools
- System access and tool setup for Scrum Team
- Team Building
- Training
Scrum is about managing the development of a project after it has been defined, reviewed, budgeted and launched. Every sprint includes refining all the information that is listed above in light of what has been learned the previous sprint. The first sprint is a special case because there are no previous sprints for people to have gained a shared understanding and learn some things that refine that understanding.
So, the first sprint has much more review work that the others, but it should still deliver some working software. If the first sprint does not deliver any working software to prime the feedback pump, then it is not a sprint at all, but instead a kickoff, JAD session or whatever that is part of the launching process rather than the development process.
Comments
Post a Comment