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

Product Manager vs Product Owner

Both the product manager and the product owner work towards a common goal, to build and improve products that create meaningful value for customers and all stakeholders within the company. This usually happens by delivering and optimizing product features. Product Manager Product Owner The product manager discovers what users need, prioritizes what to build next, and rallies the team around a product roadmap. The product owner is responsible for maximizing the value of the product by creating and managing the product backlog. This person creates user stories for the development team and communicates the voice of the customer in the Scrum process.      Product Manager and Product Owner's work on below vacuum. Product manager focus on: Business Strategy Long term Product Vision Long term Product Strategy Product Roadmap Alignment with Product Owner Product owner focus on: Release Plan (Product Backlog ie: ...
Post a Comment
Read more

New way of product development

Today is the era of fast-paced world and competitive world. Companies are realizing that the old sequential approach to developing new products won’t get the job done and product can’t be reached to market when compared to competitors. The 4 stages of product development are as follows – R&D, Growth, Maturation, and Decline. Instead of sequential approach, companies are using holistic approach – as in rugby game, the ball gets passed within the team as it moves as a unit up the field. This holistic approach has six characteristics: 1)     Build-in-instability 2)   Self-organizing project teams 3)   Overlapping development phases 4)   Multi-learning 5)   Subtle (very clear and strong) control 6)   Organizational change to explore and learning The above six characteristics forming a fast and flexible process for new product development with advantage of act as a change agent, creative, market driven ideas, flexi...
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