Scrum Sprint Retrospective Meeting
If this post helps you, click an ad
In the Scrum project management methodology, work is divided into 30 day Sprints. Following a Sprint, a retrospective meeting is held. Attendees are the Team and the Scrum Master. Each member of the team should be given an opportunity to answer:
- What went well during the Sprint?
- What improvements can be made on the next Sprint?
The team is given full latitude to discuss any factors that affect software development at the company. This could include such items as:
- Processes
- Policies
- Work environment
- Communications
The Sprint Retrospective is an opportunity to adjust the company’s Scrum approach as necessary to fit the realities of their situation. It is vital, therefore, that the feedback received at the retrospective be followed up on. Otherwise, the Team will quickly see it as a waste of time.
For one am glad for this amazing blog. Now and again, the greatest advice originate from the blog posts you may not expect. Until now, I did not give so much thought to posting comments on blog articles and have left opinions even less. Reading your valuable content, might encourage me to do this sometimes.
Be sure don’t limit yourself. Most folks limit themselves to what they think they are capable to do. Remember that you can easily go as far as your imagination lets you.