Since you have already seen the principles of agile development, as well as how to merge Design Thinking and Agile, it is time to get a better understanding on how to manage your projects with the Scrum. This week we are providing the agile planning toolkit for you to start using the methodology. Download yours here! Now, check out a few tips on how to use your agile planning toolkit to obtain faster and better results.
The Scrum is based on stories and, to fill them out correctly, you need to answer questions in the format below:
“When (situation) , I need/want/should (motivation) so that it is possible to (result) ”
This way it is possible to identify the user profiles, what they would like to do and why. With this, the team has a clearer idea of what to implement.
When defining the priority of your stories, consider what adds the most value to the business in descending order. Another point to consider is the result that the story offers, because when a story has other smaller ones depending on it, its priority increases.
Scale the amount of effort it takes to complete the story. Do this for story points, by adding up all of them and reaching the amount of points set for the project. In an initial conversation, during Sprint 0 (project planning), the team discusses how many story points they can do in a first iteration. You can come to this conclusion quickly with planning poker, a game that uses different cards listed by Story Points, which represent an abstract size value.
This is how it works:
- Someone on the team reads a user story out loud;
- The team discusses the acceptance criteria (defined by the Product Owner) and clears any doubts surrounding it;
- Each member, except for the P.O., picks a number of story points and selects the card from his deck, without showing it to the others.
- All members see the cards at the same time;
- In case the values are different, each one presents a justification, generally from the highest value to the lowest one;
- Then, the team votes again until everyone agrees.
Refine the story, seek more details, understand the operation, and clear doubts with the PO. The Scrum works at different levels of abstraction, where it moves from macro to micro as requirements are being implemented. Stories that have a high macro level of detail are known as legends. These are stories that you believe can be dismembered in others, but since you do not want to work with them at that moment, you refine it throughout the project.
Stick around, because we will launch another toolkit next week to assist you in the agile monitoring of your project. Subscribe to MJV’s content to receive it first-hand!