first sprint in Scrum- what is expected??

Before launching a project, organization need to include a first cut as per the below list:

  • 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

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros
Read more

Sense of urgency the Agile way

“You must take action now that will move you towards your goals. Develop a sense of urgency in your life.” H Jackson Brown Jr Why sense of Urgency: In a complex product development especially which is just not an enhancement but development from the scratch, a sense of urgency is very much needed.  In today's fast changing world, if there is no sense of urgency then there is a high possibility that customer will leave you soon.  Who builds the sense of urgency: Leadership team need to build this and this is done by communicating the vision and value the product development will give. if the core team who is in charge of development do not know why they are building and what is the motivation then there is a high possibility that your development team will lose focus in building a world class product. How does Scrum/Agile helps: Product owner /Scrum Master in a typical Scrum model work in a aggressive mode especially with the dependent stakeholder
Read more