123ArticleOnline Logo
Welcome to 123ArticleOnline.com!
ALL >> Hardware-Software >> View Article

Breathing New Life Into The Sprint Retrospective Meetings – Part 1

Profile Picture
By Author: mrugesh panchal
Total Articles: 48
Comment this article
Facebook ShareTwitter ShareGoogle+ ShareTwitter Share

Sprint retrospective meetings, important “ceremonies” in the scrum process, are powerful mechanisms which allow the scrum team to reflect upon the prior sprints, and share feedback for improving future sprints. Whenever a scrum project is planned and executed, it is generally observed that in the initial stages the team remains very enthusiastic and collaborates active to participate in and uphold the scrum process. However, as the project starts extending itself over numerous sprints, the team starts losing its focus and concentration levels.
The excitement and collaborative nature of the team members seen in the early stages of the project start receding and apathy sets in, prompting the team to function as mechanical tools and development cogs in the production machinery. Gone is the fervor which is so very essential if the sprint velocity is to improve with time. Scrum advocates adaption and improvement. Activities in scrum should better themselves as the project proceeds, and if this fails to happen, it is not a good sign for scrum. The success of a scrum project depends a lot upon the attitude of the product owner, and how the scrum master facilitates the entire process. These individuals should keep a wary eye and be on the lookout for signs which indicate stagnation in the team performance.

It is worth thinking about new way of doing things in scrum if the project is to be rejuvenated and new life is to be breathed into the project.

Planning for the retrospective

Current practice
At the end of the sprint iteration, the scrum master sends invitations to all team members for attending the retrospective. During the meeting, the scrum master initiates the proceedings by asking the team to clarify the three fundamental aspects which are so important and need to be essentially discussed at all costs during the retrospective:
• What worked well in the sprint (Activity to be promoted and continued in the next sprint)
• What should be stopped (Harmful practices and habits to be avoided in the next sprint)
• What can be improved upon or introduced as new (New suggestions from the team and learning from the lessons learnt in prior sprints)

Recommendation
• The sprint retrospective is held after the sprint review meeting, after a particular sprint finishes. It should offer an opportunity for the team members to discuss freely about their experiences during the sprint and how they tackled the technical issues faced by them. The meeting should function as a forum and allow a free flow of new ideas and thoughts, and above all it should be fun-filled with each member raring to speak and discuss his or her part played during the sprinting process. The team should feel motivated and concerned.
• It is important that the retrospectives be linked together and not exist as individual and independent ceremonies or events. The findings and call-to-actions of retrospectives should be carry-forwarded to future retrospectives so a proper analysis can be carried out as to what is working well and what should be prevented. The self-correction and learning process which is so important in scrum can only continue if the lessons learnt can be made available in all future retrospectives.

• Set up a simple but effective agenda involving the following aspects:

o Availing individual feedback from the team members
o Invite group feedback for common issues faced by the team
o Identifying important work priorities
o Discuss top priority topics
o Plan proper and effective call-to-actions
• Invite suggestions for making the daily scrum meetings (daily sprint meetings), or the daily stand ups, more interesting and goal oriented.

The team can also use anonymous methods of volunteering suggestions and suggesting future call-to-actions for controversial or sensitive topics. In case of disjointed teams, web based tools and utilities can be used to improve participation levels.

Total Views: 261Word Count: 644See All articles From Author

Add Comment

Hardware/Software Articles

1. Top Smart Home Systems Vendors
Author: Sonali

2. Microsoft Outlook Causing Issues? Here’s What To Do
Author: Angel Smith

3. How To Work On Your Brilliant App Idea
Author: Syeda Umama

4. The Advantages Of Hms
Author: CIMAC Marketing

5. Ipad Or Macbook For University?
Author: Flowsophic

6. How To Find A Reliable Software House
Author: Syeda Umama

7. Simplify Your Online Marketing With Product Information Management
Author: Sreejith Angamuthu

8. How Is Erp Software Helpful For School Management?
Author: SriRam Soft Solutiosn Pvt Ltd

9. Best Smart Homes Systems Market Leadership
Author: Sonali G

10. Cover All Possible Risks With Insurance For Musical Instrument Repairers
Author: victor Johnson

11. The Ultimate Guide To Find The Best It Solution Provider
Author: Netlogyx

12. Developing A Handy Grocery Delivery App For Your Business
Author: Kelseyharris

13. Six Timesaving Tips For Editing Photos
Author: Hemanta Maharjan

14. How To Use Cyclonis Password Manager Instead Of Keychain On Iphone
Author: Benjamin Jones

15. Why Choose Vyprvpn?
Author: James Conway

Login To Account
Login Email:
Password:
Forgot Password?
New User?
Sign Up Newsletter
Email Address: