Skip to main content

Daily Agile Scrum stand-up meeting guidelines

Followers of the Scrum method of project management will typically start their day with a "stand-up meeting". In short, this is a quick daily meeting (30 minutes or less) where the participants share the answers to the three questions with each other:

• What did I accomplish yesterday? 

• What will I do today? 

• What obstacles are impeding my progress? 


Some people are talkative and tend to wander off into Story Telling. 

Some people want to engage in Problem Solving immediately after hearing a problem. Meetings that take too long tend to have low energy and participants not directly related to a long discussion will tend to be distracted.

These are the minimum number of questions that satisfy the goals of daily stand-ups. Other topics of discussion (e.g., design discussions, gossip, etc.) should be deferred until after the meeting. 

Here are few tips for running a smooth daily meeting: 

• Everyone should literally stand-up and no one should sit down on chair. Assuming that team is co-located & no team member has any physical problem

• Do limit problem solving. It should not be fully Problem Resolution Meeting. You can conduct separate huddle for Problem Resolutions.

• Whoever joins last to this meeting would start first

• ScrumMaster is responsible of removing obstacles in the path of the team, so that they form no hindrances in their regular work stack.

• If required, ScrumMaster will note down the MOM and circulate/share the MOM with rest of the members by End of Play (EOP).

• All members should be present on time for Standup meeting.

• Request all team members to refer the MOM/list of issues and risks before attending the Standup.

• Any member who can’t attend the Standup should give his updates to fellow teammate. Teammate will give the updates on her/his behalf in her/his absence.

• Don’t update tasks with new estimates at the meeting. It takes too much time, for one thing. The other reason not to do this is you can get a feel of the team members being accountable to the ScrumMaster. What you really want is a self managed team that is accountable to each other, not the ScrumMaster.

• Do make sure the tasks are updated with estimates before the meeting and the burndown is present at the meeting.

• Do make sure the individual tasks are descriptive and granular. It’s ideal when estimates for individual tasks are around one day. If the tasks are large and vague, it takes a long time for the team member to describe what she’s doing and for the rest of the team to understand.

• If a team member doesn’t burn down any time for a task because she discovered a new predecessor task that wasn’t accounted for, make sure the new task gets added to the sprint. That way you have a better history and a more accurate burndown chart.

Comments

Post a Comment

Popular posts from this blog

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - ar...
Post a Comment
Read more

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir...
Post a Comment
Read more

Delivering a project within budget

 Here are some tips for delivering a project within budget: Set a realistic budget Define the project's scope and necessary resources, and create a budget that's realistic. Cost estimate Segment the project into smaller tasks and milestones to plan how to use resources and provide clarity. Divide the project plan Break down the project into tasks to avoid late deliverables and over-budget projects. Monitor progress Regularly track the project's progress to identify and prevent cost overruns. Use progress reports to compare actual costs to the budget. Anticipate and revise changes Communicate with stakeholders to identify and assess risks, and assign owners to each risk. Consider different scenarios Estimation can be difficult for complex projects with many potential outcomes. Tracking: Tracking time spent on tasks, Tracking expenses per project, and Using project management software. Use Historical Data Your project is likely not the first to try and accomplish a specific o...
Post a Comment
Read more