Wondering on how to estimate a set of business requirements into one or more Agile SCRUM Sprints? Go on reading further and let me know what you think.
If you are planning to work/develop software based on Agile SCRUM development model and are looking out for an estimation model, here it goes.
Quick Overview on Agile SCRUM
Before I go into presenting the model, let me present a quick introduction to Agile SCRUM development model.
Agile software development is a set of software development methods that are based on iterative and incremental method, where requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. Following is taken from Agile Manifesto website. Also, check some of the twelve principles of Agile development methodologies:
Scrum is an iterative and incremental agile software development framework for managing software projects and product or application development. Its focus is on “a flexible, holistic product development strategy where a development team works as a unit to reach a common goal” as opposed to a “traditional, sequential approach”.
Simply speaking, the way in which this works is that there are one or more SCRUM teams handling one or more application development. This team works in a SCRUM model thereby carrying out different activities/ceremonies such as pre-planning, planning, implementation, testing, and retrospectives. In planning phase, the team analyses the story and, estimate the complexity of the stories in form of points described below.
Estimation Technique
In my experience, SCRUM has been implemented in one of the three different sprint duration such as a 2-week, 3-week or a 4-week sprints. In these sprints, the developer and testers work together with a Scrum master and a product owner/business analyst on a set of stories (features/enhancements) taken from product backlog. Each of the story (from coding perspective) is estimated in form of following enumerations in points:
Once you have broken down the stories into complexities and estimated its completion in form of points, it is time to determine how many developers may be needed to release a set of requirements in a given time frame. This largely depends upon the velocity of individual developers’ velocity. Velocity is average number of story points that a developer can deliver in any specific sprint.
Assuming that developers have a velocity of 5 points in a 2 week’ sprint, and your set of requirements got estimated to a total of 120 story points, and you got 4 developers, following will be number of 2-weeks sprints:
120 / (4 developers x 5 points) = 6 sprints
Thus, the 120 points worth business requirements can be delivered in 6 x 2 = 12 weeks which is equivalent to 3 months.
Last updated: 2nd May, 2024 The success of machine learning models often depends on the…
When working on a machine learning project, one of the key challenges faced by data…
Last updated: 1st May, 2024 The bias-variance trade-off is a fundamental concept in machine learning…
Last updated: 1st May, 2024 As a data scientist, understanding the nuances of various cost…
Last updated: 1st May, 2024 In this post, you will learn the concepts related to…
Last updated: 26th April, 2024 In this blog post, we will discuss the logistic regression…