Estimating Agile Tasks for Scrum Masters
In Scrum, a list of user stories is produced and put together to form a product backlog, and each of these user stories will need to be estimated to work out how many of these stories can be worked on during a given iteration. One of the responsibilities of the Scrum Master is to act as the facilitator in the estimation of the size of each piece of work.
The Use of Story Points
Story point estimation is different from the traditional method of sizing a piece of work based on the number of hours it will take. Instead, the estimate is derived from the complexity of the functionality being produced, and the figure assigned is based on the relative size and difficulty when compared to other user stories. The reason for this is that there are many variables that could have an impact on the amount of time that a piece of work takes to complete, such as the level of experience of the developer.
The How and Why of Story Points
Story points are important because they give a clearer picture of the size and complexity of a piece of work than the estimation of time required that is used in a waterfall lifecycle. They help the Scrum Master to work out the velocity (the number of story points that can be delivered in a single iteration) of the team. Using story points gives the Scrum Master a tangible representation of what they are dealing with. It also allows them to gauge how things are progressing when updates are given by each team member during the daily stand-up, and to keep a close eye on any of the more complex stories in order to resolve any issues early on.
59 Seconds Agile – Estimating Agile Tasks
Estimation Techniques
Planning Poker
T-Shirt Sizing
This estimation method can be used when the team seems to be spending too much time trying to get to a very exact number of story points, possibly because some team members are equating this with the number of hours required to complete the work. When using t-shirt sizing, estimates are selected from a range of extra-small, small, medium, large, extra-large, or double extra-large. While this technique can help in situations where people are becoming too analytical and getting bogged down in the details, it does require additional effort on the Scrum Master’s part, as he/she will then need to assist with translating the t-shirt sizes into the number of story points at a later stage when the planning session is over. It tends to be more common to use this technique when people are relatively new to agile, or when a team has been newly formed. Over time, as the team gels together, it would be more appropriate to move to a somewhat more sophisticated technique like planning poker.
Prev <— Continue Reading —> Next
Our Favourite Agile Books
The History of Agile For Scrum Masters
Prior to the 1990’s software development was very slow, often taking years to complete development and release the product to market. The industry was following a very formal methodology for products and software development…
What is Agile to the Scrum Master?
While traditional project management is still widely used, the benefits of an Agile approach to running a project are becoming more and more recognized. Where Agile has a distinct advantage over classic project management is the development of new products…
Why Use Agile as a Scrum Master?
When determining if a move to Agile is right, a PESTLE can be used to simplify what factors should be considered. While Agile is sometimes thought of as a software development project management method, it isn’t just for these types of technology-centric companies…
The Agile Manifesto For Scrum Masters
Agile is a quick, simple, lightweight and effective way of managing projects. In traditional project management models…
The Agile Principles For Scrum Masters
When the Agile Manifesto was drawn up in 2001, it embodied four values and twelve principles that signaled a new approach to…
The Agile Fundamentals For Scrum Masters
Thinking of becoming a Scrum Master? Or are you already one, but you’re still new to the job? No matter what level of experience…
The Declaration of Interdependence For Scrum Masters
The Declaration of Interdependence establishes that all members, stakeholders, and customers are interdependent and…
The Agile Frameworks For Scrum Masters
There are many different Agile frameworks – all of them share the same philosophy and are built around the Agile Manifesto and Principles. But they vastly differ in their approaches, values, and structure. …
The Scrum Framework For Scrum Masters
The Agile Scrum framework is designed to deliver products and projects of any size. This includes projects, programs, and portfolios. Scrum provides guidelines on delivery techniques, events, and roles. Many of the same ceremonies are held within both a standard Agile scrum project and an Agile Scrum…
The Scrum Roles For Scrum Masters
Scrum is a useful tool for the creation, maintenance, plan, and execution of diverse products and services. The tool consists of…
The Scrum Team Size For Scrum Masters
The basics of Scrum can be easy but implementing them and succeeding with Scrum can be infinitely harder. Scrum …
The Agile Project Vision For Scrum Masters
At the heart of any great product is a great vision. It describes the primary goal or goals of a product and creates a focus that…
Forming the Scrum Team For Scrum Masters
Scrum is a framework that encourages delivery of potentially shippable product increments every 2-6 weeks. The work is…
Developing Epics For Scrum Masters
The term ‘epic’ in agile refers to a large user story that has not yet been defined in detail. Typically, an epic will cover a single…
The Agile Product Backlog For Scrum Masters
A Product Backlog is an organized collection of the existing User Stories (aka Wants and Needs) for an explicit business endeavor. Think of a shopping catalog of User Stories, ordered by urgency, that can be perused and selected from to determine what will be worked on during the current…
Release Planning For Scrum Masters
Although flexibility and adaptability are part and parcel of an agile methodology, this does not mean that no planning is required when…
Creating User Stories For Scrum Masters
User Stories are an integral part of the agile development process. They are an important agile technique that is used to frame…
Estimating User Stories For Scrum Masters
One of the principles of self-managing teams in Agile Scrum is working collaboratively with the Product Owner to effectively deliver…
Creating Tasks For Scrum Masters
According to The Agile Manifesto: “The best architectures, requirements, and designs emerge from self-organizing teams.” As a…
Estimating Agile Tasks For Scrum Masters
In Scrum, a list of user stories is produced and put together to form a product backlog, and each of these user stories will need to…
Creating the Sprint Backlog For Scrum Masters
The Sprint Backlog is defined as a group of user stories that are grouped together during the Sprint Planning Meeting. This…
Creating the Deliverables For Scrum Masters
Agile Scrum provides the framework for delivery of the vision of an organization. Execution of the vision includes processes, ceremonies and project deliverables that are also known as artifacts…
The Daily Stand-Up For Scrum Masters
The daily scrum is an opportunity for developers or anyone committed to working in the sprint to talk to each other to make sure the…
Product Backlog Prioritisation For Scrum Masters
The product backlog is a key element of Agile software development. It facilitates a development environment that creates valuable features and products for stakeholders…
The Sprint Review Meeting For Scrum Masters
The Sprint Review meeting comes at the end of the sprint and the goal of this meeting is to have key people in the room to be able …
Demonstrating and Validating the Sprint For Scrum Masters
As organizations migrate to Agile principles, there may be questions about how the organization can prove that there is value…
The Sprint Retrospective For Scrum Masters
A very simple step by step guide to help you choose the appropriate product development methodology from…
Releasing the Product For Scrum Masters
One of the most important milestones any project will ever have is finally releasing their product and putting it out there. It’s the…
Regression Testing For Scrum Masters
In companies using agile development, it is common to introduce changes in a product incrementally. Along with the new changes, unexpected issues may arise, testing whether the existing functionality is broken or not becomes very important…
Product Owners
Find out more about the Agile and the Product Owner Role
Developers
Find out more about the Agile and the Developer Role
More Articles
