Greatness can’t be imposed; it has to come from within. But it does live within all of us – Jeff Sutherland
First, you need to select your team members. Scrum teams consist of 3 roles:
* The Product Owner – The Product Owner is the spokesperson for your customer who will share the vision and priorities with your team.
* Scrum Master – The Scrum Master is not a manager, but a facilitator between the Product Owner and Development Team.
* Development Team – The Development Team develop the product in increments. The Development Team are self-organized, as opposed to many teams that use a more traditional hierarchical system.
Once you have your selected your Scrum team members, it is time to start planning the sprint. A Scrum sprint is a time-boxed iteration in which to develop the product. The optimum length of a sprint is typically 2-4 weeks but can be as little as 1 week. Your sprint planning should begin with the Product Owner creating a product backlog. A product backlog is a broad list of items that need to be completed by the Development Team. Each task is assigned a priority. The highest priority items (user stories) can then be presented to your Development Team, who can decide what they can complete within the timeframe of the sprint. After breaking down the user stories into tasks and estimating the required effort, the Development Team should move their tasks into a sprint backlog.
Now that you have your plan for the sprint, it is time to start completing the work. During a sprint cycle, the Development Team works through the user stories from the sprint backlog. Daily team meetings should be held to share progress, plans and highlight any issues. These meetings are to be kept within 15 minutes and overseen by the Scrum Master who should keep everyone focused. Progress must be tracked continuously during the sprint. This can be done with the use of a burndown chart. During the sprint, your Development Team must prepare the product increment for review. They need to make sure that the increment is potentially shippable, as no incomplete work can be shown at a sprint review.
At the end of every sprint, a sprint review must be held. This gives the Development Team the opportunity to demonstrate the finished product increment to the Product Owner and customer. Everyone should be encouraged to share their feedback, suggestions and new ideas. It is at this point that the customer can change their mind about what they want.
At the end of every sprint, you should also hold a sprint retrospective. During a sprint retrospective, the whole team evaluates the sprint. They should ask each other what went well this time and highlight any improvements that need to made for the following sprint.
The next step is to deliver the product increment. The product increment is the output of all the user stories completed during the sprint and previous sprints. It must be in a good working condition, whether the Product Owner decides to release it or not.
When the customer receives the product increment, they will test it and decide whether it is complete. If it is incomplete, the Development Team should prepare for another sprint to add more features to the increment. They need to delve back into the product backlog and pick another set of high priority user stories. The sprint cycles should then continue until all user stories are complete to the Product Owner’s satisfaction.
Completing the product will take you several sprint cycles. Once the Product Owner is satisfied with the product increment, it is ready for final delivery to your customer.
This should give you a simple overview of how Scrum works. To see how Scrum works in more detail, take a look at the graphic below. You can also download a large-scale poster version to print for your office!
Simon Buehring is the founder and Managing Director of Knowledge Train, an accredited PRINCE2 training organization based in London, UK. For over 25 years, Simon has worked as a project manager for a wide range of organizations, both in the UK and internationally, including the BBC, HSBC and IBM.
Help the growth of this blog
The latest The Program Manager's Paper! paper.li/SaverioLosi… Thanks to @SusanneMadsen #pmot
The latest The Program Manager's Paper! paper.li/SaverioLosi… #pmot
The latest The Program Manager's Paper! paper.li/SaverioLosi… Thanks to @SusanneMadsen #pmot #leadership
The latest The Program Manager's Paper! paper.li/SaverioLosi… #pmot #pmpodcast
Che fai domenica?
Quelli che... Il Budget Healthy 2020!
#lifeatreply #healthyreply #budget2020 pic.twitter.com/Taef…
My week on Twitter 🎉: 5 New Followers. See yours with sumall.com/performan… pic.twitter.com/2EVi…
Un saluto al gran capo!!! Questo è il nostro stile, lo stile Healthy! #lifeatreply #healthyreply #reply instagram.com/p/B3Fl…
At Healthy Reply we build amazing solutions and connected products experiences also based on mobile and machine learning.
If you are up for the challenge, apply here:
#AppHealReply #TiCuroReply #IoMT #IoT #job #Reply #Healthy #digitalHealth lnkd.in/gCqatvB
The latest The Program Manager's Paper! paper.li/SaverioLosi… #pmot #pm
The latest The Program Manager's Paper! paper.li/SaverioLosi… Thanks to @corneliusficht #pmot
My week on Twitter 🎉: 1 Mention, 13 Mention Reach. See yours with sumall.com/performan… pic.twitter.com/Rgt4…
The latest The Program Manager's Paper! paper.li/SaverioLosi… Thanks to @SusanneMadsen @BarryHodge #pmot #projectmanagement
The latest The Program Manager's Paper! paper.li/SaverioLosi…
The latest The Program Manager's Paper! paper.li/SaverioLosi… #pmot #pmo
My week on Twitter 🎉: 3 New Followers. See yours with sumall.com/performan… pic.twitter.com/acR0…