Scope Issues in an Agile Project

I was talking with a colleague the other day about troubles with scope management in an Agile project. She was lamenting problems that were arising with a particular client who was concerned about the progress of the delivery team. Since Agile teams use time boxed iterations and let scope adjust, this shouldn’t be a problem—should it?

There are a number of issues surrounding scope management in an Agile project, many of them are the same as trying to manage scope in a traditional project:

• Perception versus reality

• Poor definition of how to measure scope

• Running an Agile project in a non-Agile organization

• Wish-based planning

Agile projects, unfortunately, don’t eliminate the perception versus reality problem. Miscommunication and misunderstanding can impact an Agile project even as teams try to expose reality—or at least their reality. Short iterations and working software can reduce the perception/reality gap, but as long as projects are delivered by people and evaluated by other people, a gap will often remain. Good project managers realize they have to manage both—reality and perception.

Another question that isn’t asked or answered very often is—so what is scope? Is it the number of requirements, stories, or features? Is it the total work hours or story points estimated for the project? Is it the documented requirements? At what point is scope determined since in an Agile project features can change over the life of the project? These are all bottom up measures of scope (and therefore progress). Maybe a better approach, particularly in an Agile project in which the detail stories and features are changing, is to ask a top-down question, “Can we deploy this product at the end of this iteration?” Obviously the answer to this question involves some determination about feature completion, but the question really asks about value, about enough value to deploy, not about whether a set of detail requirements have been met.

Scope issues often crop up when Agile teams confront traditional organizational success measurements. The teams view themselves as being successful on the project and managers are wondering what’s going on since they don’t understand this “iterative” approach. This is somewhat different from the perception versus reality issue; it’s more the clash of two different perceptions (or two realities).

Finally, too many organizations subscribe to what I’ve called “wish-based planning.” They do a lousy job of capacity planning, that is, balancing the demands for work to be done with the actual capacity of the organization. These managers don’t understand the difference between stretching limits and being completely unreasonable and stretched project plans become irrational wish-based plans. Agile teams will still experience scope problems in this type of dysfunctional situation.

So, Agile won’t fix all your scope problems. Agile can help teams and management look at scope from a different perspective, but the long-held perceptions of scope will be difficult to change in many organizations.

Share on facebook
Facebook
Share on twitter
Twitter
Share on linkedin
LinkedIn

Leave a Reply

Your email address will not be published. Required fields are marked *

Recent Posts

Culture, Skills, and Capabilities // How to become a more data-driven organisation

In our whitepaper “How to become a more data-driven organisation”, we wrote about the five steps that an organisation would need to take, which are: Outcomes: Defining goals and metrics to ensure clear and measurable outcomes Analytics: Implementing and sharing the analytics to improve data-driven decision making Innovation: Testing assumptions through hypothesis testing and learning Data Platform: Gaining new insights

Read More »

Data Platform // How to become a more data-driven organisation

This is the fourth article in our series on “How to become a more data-driven organisation”, and we are going to be focusing on Data Platforms. It is at this point that most people start to dive deep into the technical aspects of Data Lakes vs Data Warehouses, but we want to bring us back up a level and ask

Read More »

Innovation // How to become a more data-driven organisation

In our white paper “How to become a more data-driven organisation”, we wrote about the five steps that an organisation would need to take, which are: Outcomes: Defining goals and metrics to ensure clear and measurable outcomes Analytics: Implementing and sharing the analytics to improve data-driven decision making Innovation: Testing assumptions through hypothesis testing and learning Data Platform: Gaining new

Read More »

Search the Blog

Agile Management Made Easy!

All About Agile

By Kelly Waters

“’Agile’ is one of the biggest buzzwords of the last decade. Agile methods often come across as rather more complicated than they really are. This book is an attempt to unravel that complexity. To simplify the concepts. This book breaks the concepts into small bite-sized pieces that are easy to understand and easy to implement and delivers the message in a friendly and conversational style. Allaboutagile.com is one of the most popular blogs about agile on the web. ”

Kelly Waters

Agile 101 is available to purchase. GAME ON!

Agile 101

Emma Hopkinson-Spark

“Whilst there are lots of ways you can vary the game depending on the teams you have and the learning outcomes you want, the basic flow of the game play is common to all.”
Emma Hopkinson-Spark

Why did we make the game?

How to play the game?

London

101 Ways Limited
145 City Rd
London
EC1V 1AZ
United Kingdom

Amsterdam

101 Ways BV
Weesperstraat 61-105
1018 VN Amsterdam
Netherlands

Contact Us

If you would like to get in touch with one of the team at 101 Ways, then please fill out the form below or email us at contact-us@101ways.com.