Posts

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 ask the question, “How much bigger the second bucket is as compared to the first one (relative estimate)?” Usua

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