Top 5 ways to make scrum meetings productive

Daily Stand-up Meeting-


  1. Are team members committed to the goal of the Sprint ? This should be verified by showing the taskboard to team possibly a Kanban board and let the team team provide their opinion on where they stand. Additionally, show them the burndown chart trend on the daily basis in the meeting, if the chart is deviating from ideal graph.
Sprint Planning Meeting
    
     2.  Are the team members doing some pre-planning and preparing themselves for the planning meeting. This should be verified by checking that team is very sure about the user stories and they know what stories to be delivered and how.

Sprint Refinement/Grooming Meeting

    3.  Are the user stories are prepared well prior to this meeting? Are the user stories understood to PO before explaining to team? This  can be verified by ensuring that sizing of the stories are happening for the planned stories for this meeting.

Sprint Review Meeting

    4. Are the team well prepared to deliver the demo? Do they have stable environment where working software is present? Are the stakeholders are getting involved and interested to know /understand what team has done in the review meeting?

Sprint Retrospective Meeting

    5.  Are the discussions are happening without any fear and opinions are expressed freely? Are these documented and action plan prepared? Are the improvement happening by looking at previous action plan?

These are some of the tips to make the meetings productive however the most important point is to understand that we must have a goal set for each meetings.


Comments

Post a Comment

Popular posts from this blog

Scrum Answer to Top 10 Software Project Risks

Source: (The Standish Group, 2011) Lack of top management commitment Scrum demands commitment from the top management through the assignation of a full-time cross-functional self organized team. The team is protected and can take their own decisions about the project with the support of the top management. Failure to gain user commitment In Scrum, the team constantly show working software to the users, which increase the commitment and feedback. Misunderstanding the requirements Scrum knows that is not possible to fully understand all the user requirements. In each iteration, the team work in the more important and clear requirements. As the software is developed, the team get better insights about the project goals and have more clarity about the following requirements. Lack of adequate user involvement Constantly working software makes the users more involve in the process. Lack of required knowledge/skills in the project personnel In Scrum, the teams are cros...
Read more