Daily stand-up

-


Daily stand-up

Attendees
Required: development team, scrum master, product owner
Optional: team stakeholders
When: Once per day, typically in the morning.
Duration: No more than 15 minutes. Don't book a conference room and conduct the stand up sitting down. Standing up helps keep the meeting short!
Agile Framework: Scrum and Kanban.
Purpose: Stand-up is designed to quickly inform everyone of what's going on across the team. It's not a detailed status meeting. The tone should be light and fun, but informative. Have each team member answer the following questions:
  • What did I complete yesterday?
  • What will I work on today?
  • Am I blocked by anything?
There's an implicit accountability in reporting what work you completed yesterday in front of your peers. No one wants to be the team member who is constantly doing the same thing and not making progress. 

Comments

Post a Comment

Popular posts from this blog

Agile Bug Triage Meeting

-
Agile Bug Triage Meeting Definition: Bug Triage meeting is discussion and analyses for all open bug, and agenda of discussion is set the priority to team for which bug should take up first, classify the bug in different category, find the where team struggle to get help to debug RCA, if RCA is available then assign bug to right team, find the recreation step from reporter and severity of bug.                             Procedure: Generally, below procedure is followed for Bug Triage Meeting QA lead sends out a bug report with the new Bugs introduced since the last meeting. Product owner calls out a meeting. During the meeting, each Bug is analyzed to see whether correct priority and severity are assigned to it. Priority and severity are corrected if need be.   Bugs are discussed by the team. This involves discussing RCA, Dependencies to resolved bug, risks   Assignment, rejection, reassignment of Bugs.   After meeting completion, minutes of meetings are used for the
Read more

Scrum Framework ( Scrum Methods)

-
Image
Scrum Framework A Scrum project involves a collaborative effort to create a new product, service, or another result as defined in the Project Vision Statement. Projects are impacted by constraints of time, cost, scope, quality, resources, organizational capabilities, and other limitations that make them difficult to plan, execute, manage, and ultimately succeed. However, successful implementation of the results of a finished project provides significant business benefits to an organization. It is therefore important for organizations to select and practice an appropriate project management methodology. Scrum is a framework rather than a methodology. It provides clarity of responsibilities through roles, visibility through artifacts, and opportunities for inspection and adaptation through its events. Within this structure, scrum is a container for other processes and tools that are appropriate for meeting the specific needs of a team, organization or pro
Read more

Release Planning in Agile

-
Image
Release Planning in Scrum organizations that use a Scrum process have a number of Scrum Teams that must collaborate to produce products. Issues that arise in moving to a Multiple-Team context include release ·        How to divide a large organization that use a Scrum process have a number of Scrum Teams that must collaborate to produce products. Issues that arise in moving to a Multiple-Team context include release ·        How to divide a large group of potential Team members into a specific set of Teams ·        How many Scrum Masters are needed to support the Teams ·        How many Product Owners are needed to support the Teams ·        How to develop requirements that span many Teams ·        How to plan, track, and enable successful coordination of work that spans many Teams ·        How to balance the competing needs for Product Management for both customer focus and Team focus ·        How to plan and track work for longer time horizons than one Sprint
Read more