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

All About How To Hold Conventional And Non-conventional Scrum Meetings

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

In many ways, scrum is all about meetings. Once the product backlog is created by the product owner, the meetings starts, and keeps on occurring until the entire project is completed. While some of the meetings such as the sprint planning, sprint review, and the sprint retrospective are “planned” meetings, and the scrum guide lays down clear guidelines as to how they should be conducted and what should be availed from them, it may be required to hold special meetings as and when needed to streamline the scrum process. The scrum guide does not mention anything about non-standardized meetings, or those which have been called impromptu. It is important to plan and organize such meetings to make them effective in scrum.

1. Meet only if required
First and foremost, if the information can be conveyed through a memo, emails, or a small presentation, don’t conduct the meeting. One of the key management strategies is to identify the nature and requirement of conveying the information to team members. If the ...
... nature of information is “simplex” i.e. information needs to be conveyed only “one way”, a lot of time can be saved by just sending a memo. Typically, the scrum master or the product owner may need to brief up the team members regarding the feedback availed from the stakeholders, or just let the team know about the time a particular meeting is scheduled. In such instances, it is not required to hold a special meeting to convey “one way” information since a feedback or further discussion is not expected or required with respect to the message conveyed.

2. Set up clear objectives for the meeting
If a meeting is supposed to be held, it should have an objective! It is meaningless to conduct meetings where objectives are not clearly explained and the team does not have any idea why the meeting is called for, or what is planned to be done in the meeting. A proper agenda should be created beforehand and conveyed to the team well in advance so the team knows why the meeting has been called, and what is going to be discussed in it.

3. Instruct the members to prepare for the meeting
If you find it necessary to hold the meeting, and have prepared an agenda to explain what you plan to discuss in the meeting, it is recommended you instruct or inform the team members how they ought to prepare for the meeting. Ideally, a list should be prepared explaining what is expected from the team member, and what activities the particular member should carry out before attending the meeting. If you have team members belonging to specific groups depending upon their area of work and specialization, you could prepare a common list of instructions stating what and how each member in the group should do to ensure their participation in the meeting is a positive one.

4. Prepare a plan of action
Now that you have done everything to make your meeting a successful one, it is important you achieve the objective of holding your meeting in the first place. It is important to inform the team members what they are expected to do once the meeting is completed. More than often, people attend meetings and simply forget about what was discussed and whether the objective of holding the meeting was satisfied once the meeting is over. The reason why this happens is there is no “Call-to-action” linked with the particular meeting. Each member should know that he or she is supposed to do to complement the meeting, and ensure its objectives are properly fulfilled.

5. Learning from the meeting
Scrum is all about self-correction and self-learning. Each activity you do or carry out in scrum has a feedback activity associated with it. At the end of each meeting, a few minutes should be ideally spent to discuss what has been learnt through the meeting, and what should be done in the future to improve the scrum process. The team members should learn something new, or take back a certain benefit from the meeting. The meeting should result into something positive in the end.

Total Views: 601Word Count: 691See All articles From Author

Add Comment

Hardware/Software Articles

1. Soundwise.ai: The Intelligent Transcription Platform Transforming Digital Workflows
Author: Shawna

2. Why Do Large Enterprises Still Prefer Custom Development?
Author: Aimbeat Insights

3. Video Review Software: Streamline Feedback And Boost Creative Efficiency
Author: ayush

4. Can Helical Insight Be A Scalable Tableau Replacement For Start-ups And Enterprises?
Author: Vhelical

5. What Is Mvp In Software Development?
Author: Aimbeat Insights

6. Construction Quality Management Software: Why It Matters For The Industry
Author: QualityPro by TecWork

7. Top Free Apps Like Pocket For Offline Reading
Author: Ebrahim

8. Features Of Online Proofing Software To Streamline Creative Workflows
Author: ayush

9. Why Your Email Extraction Might Not Be Working
Author: vSoftware

10. Maximizing Roi: Smart Strategies For Cost-effective Erp Implementation
Author: Ashapura Softech

11. Content Review And Approvals Software: The Ultimate Guide To Streamlined Collaboration
Author: ayush

12. How To Choose The Best Odoo Partner For Your Business In 2025
Author: Alex Forsyth

13. Design Approval Software: The Complete Guide For Faster Creative Collaboration
Author: ayush

14. Is Microsoft 365 E5 Worth It In 2025? Here’s What Enterprises Need To Know
Author: ECF Data

15. E-commerce Development: Strategies, Trends, And Best Practices For Online Business Growth
Author: Milleniance

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