![]() ![]() Usually we have very few changes, because we regularly discuss the features during the Backlog refinement, and the Product Owner keeps the boards up to date. The team uses one board as a central hub for the Sprint Planning meetings.Īt the beginning of the session, the Development Team checks whether the feature boards have any feature-related changes. ![]() All the Jira cards within the user stories are linked to the particular online boards containing the product feature details. ![]() Here’s how we managed to get our Sprint Planning down to half an hour.īefore the session begins, the Product Owner imports any Jira issues to the board and I add relevant Retrospective results. Usually our Scrum Team spends only half an hour every two weeks for the Sprint Planning meeting. Our Scrum Team consists of three developers, a Product Owner and a Scrum Master.
0 Comments
Leave a Reply. |