Scrum Check list

-

Comments

Post a Comment

Popular posts from this blog

Relative Estimation

-
Image
Relative Estimation In a traditional software development method, estimations are done in absolute numbers like hours or days. In this approach, by applying the Work Breakdown Structure, a big project is divided into small tasks and each task is estimated in hours. These estimates depend on the skills of the resources. Estimation of technical tasks in absolute number is not always easy. Sometimes for a technical task, debugging will take 6 hours but the actual code fix will be done only in 10 minutes. Relative Estimation could be useful in estimating complex tasks. To understand more on relative estimation, let’s take an example of buckets mentioned in the picture below.                                         If we ask how big is the first bucket and how big is the second bucket (absolute estimate)? We may not answer this question in absolute numbers. But if we as...
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 · ...
Read more

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, Dependen...
Read more