Project Management

Please login or join to subscribe to this thread

How to approach Sprint planning?

linkedin twitter facebook   Agile   New Practitioners   Scrum  
avatar
Jonathan Lee Business Development Manager| Symphony Communication Services LLC Singapore, Singapore, Singapore
As someone who has had more experience with waterfall, how do I approach planning for sprints in an agile project? We do not currently have scrum masters in our part of the world. Any guidance at all would be helpful. Thank you!
Sort By:
< 1 2 >
avatar
Tabassum Mehmood ALIS Glenview, Il, United States
In Agile all user stories are added in backlog which is also called product backlog. Before approaching sprint planning meeting scrum master needs to prioritize the user stories, of course priority is set based on business and stakeholders needs. Once all are prioritized then in sprint planning meeting scrum master needs to choose user stories from top priority to bottom. Let's say scrum master choose user story 1, then ask developers how much time they need to finish it and is that story is complete means no clarity needed and acceptance criteria is there etc. .... then ask testers how much time they require to test it, this process is called story sizing, you can use many different methods but one popular is Fibonacci method (1,2, 3, 5, 8....), keep following this till you reach the average velocity, means if the team reach at 80% of the work then you stop and bring all user stories into Sprint, that will called now sprint backlog.
Always communicate with team members they are best source and will help in making things on ease.
Since they participating in sprint planning meetings they will know the process and most of the time they come prepared which saves your time
< 1 2 >

Please login or join to reply

Content ID:
ADVERTISEMENTS

"If you can't convince them, confuse them."

- Harry S. Truman

ADVERTISEMENT

Sponsors