Planning Meetings
- 2015-09-11 10:15:59
- azalea
- 11750
- Last edited by Taotao on 2018-11-14 16:41:02
- Share links
According to Scrum, development teams should hold sprint planning meetings regularly. Usually, the planning meeting should be done within one day and divided into two parts. In the first part, product managers explain stories, define their priorities and make a list of stories that will be done in this sprint. In the second part, development teams decompose stories into tasks.
Sprint planning meeting workflow
- Project managers prepare the meeting in advance and then inform others the time and place of the meeting.
- Product managers can categorize the stories in advance and link the stories that will be done to projects in the sprint.
- Product managers explain the stories to everyone. And all the people present at the meeting should listen carefully and give their own opinions.
- After explaining all the stories, an estimation of the workloads should be made and the priorities should be set based on the workloads of each story.
- Adjust the stories linked to projects according to priorities and workload. Unlink the unnecessary stories and link new stories.
The outcome of sprint planning meetings
Sprint planning meeting is to link stories to projects in ZenTao.
If you have more questions, leave a message below or email us at Renee@cnezsoft.com.
Write a Comment
Support
- Book a Demo
- Tech Forum
- GitHub
- SourceForge
About Us
- Company
- Privacy Policy
- Term of Use
- Blogs
- Partners
Contact Us
- Leave a Message
- Email Us: support@zentaoalm.com