| Ali Shah
A daily stand-up meeting of team members, including the Product Owner, lasting no more than 15 minutes. Each participant must answer the following three questions:
- What did I do yesterday that helped the team reach its sprint goal?
- What will I do today to help the team reach its sprint goal?
- Do I see any obstacles preventing me or the team from reaching the velocity goal?
This meeting is to ensure that backlog is refined and the priorities are already set and the backlog is in the correct order while estimates are done according to the priority. Duration of this meeting should not be longer than 2 hours for a 4 week sprint. Could have backlog grooming each week or before the sprint planning meeting.
is a time-boxed to a maximum of 8 hours for a 4 weeks Sprint. The new sprint starts with this meeting. A set of user stories from the top of the Product Backlog are estimated into story points, then decomposed into tasks and estimated in hours. Finally the Team, based on the Team Capacity, selects a set of these stories into the new Sprint Backlog (that may contain also unfinished user stories from the previous Sprint).
At the end of each sprint there is a review/demonstration session. During this meeting, the team shows what they achieved during the sprint. This usually takes the form of demonstrating new features or the underlying architecture. The duration of this meeting should be a maximum of 4 hours for a 4-week run.
Is a meeting that helps the team to fine-tune the process. This is a time for each team member to reflect on what went right and areas for improvement. Clear action items should be defined. The duration of this meeting should be maximum 3 hours for a 4 weeks Sprint
Join us next time, as we continue our journey of learning canvas apps.Click here to learn more about Imperium's Power Apps Services. We hope this information was useful, and we look forward to sharing more insights into the Power Platform world.