Scope Issues in an Agile Project

This content is syndicated from Jim Highsmith by Jim Highsmith. To view the original post in full, click here.

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.

Leave a Reply

What is 3 + 6 ?
Please leave these two fields as-is:
Please do this simple sum so I know you are human:)

There are 101 ways to approach anything.
To find the best way, sometimes you need expert help

What People Say

“Kelly revolutionised the way our digital department operated. A true advocate of agile principles, he quickly improved internal communication within our teams and our internal clients by aligning our business and creating a much enhanced sense of transparency in the decisions the business was making. Kelly also introduced a higher sense of empowerment to the development teams...”

PETER SILVA-JANKOWSKI
IPC MEDIA

“Kelly’s a leading program director with the ability to take charge from day one and keep strong momentum at both a program and project level driving prioritisation, resourcing and budgeting agendas. Kelly operates with an easy-going style and possesses a strong facilitation skill set. From my 5 months experience working with Kelly, I would recommend Kelly to program manage large scale, complex, cross company change programs both from a business and IT perspective.”

LUKE SHARKEY /STRATEGY & IMPLEMENTATION LEADER
SUNCORP

“Kelly is an extremely talented and visionary leader. As such he manages to inspire all around him to achieve their best. He is passionate about agile and has a wealth of experience to bring to bear in this area. If you're 'lucky' he might even tell you all about his agile blog. Above all this, Kelly is great fun to work with. He is always relaxed and never gets stressed - and trust me, he had plenty of opportunity here! If you get the chance to work with Kelly, don't pass it up.”

GILES BENTLEY, DEVELOPMENT & OPERATIONS DIRECTOR
TIME INC

“Kelly is an Agile heavy-weight. He came in to assess my multi-million $ Agile development program which wasn’t delivering the right throughput. He interviewed most of the team and made some key recommendations that, when implemented, showed immediate results. I couldn’t ask for more than that except he’s a really nice guy as well.”

DAN PULHAM, DIGITAL DIRECTOR
TELSTRA

“Kelly and I worked together on a very large project trying to secure a new Insurer client. Kelly had fantastic commercial awareness as well as his technical expertise. Without him I would never had secured this client so I owe a lot to him. He is also a really great guy!”

GINA MILLARD
GLASS'S INFORMATION SERVICES

“Kelly came to the department and has really made a huge impact on how the department communicates, collaborates and generally gets things done. We were already developing in an agile way, but Kelly has brought us even more into alignment with agile and scrum best practices, being eager to share information and willing to work with us to change our processes rather than dictate how things must be done. He is highly knowledgable about agile development (as his active blog proves) but his blog won't show what a friendly and knowledgeable guy he is. I highly recommend Kelly to anyone looking for a CTO or a seminar on agile/scrum practices - you won't be disappointed!”

ANDY JEFFRIES/TECHNICAL LEAD
IPC MEDIA

“Kelly was a great colleague to work with - highly competent, trustworthy and generally a nice bloke.”

HANNAH JOYCE
GLASS'S INFORMATION SERVICES

“Kelly was engaged as a Program Director on a complex business and technology transformation program for Suncorp Commercial Insurance. Kelly drew on his key capabilities and depth of experience to bring together disparate parties in a harmonised way, ensuring the initiate and concept phases of the program were understood and well formulated. Excellent outcome in a very short time frame. ”

BRUCE WEIR/EGM
SUNCORP

“I worked with Kelly on many projects at IPC and I was always impressed with his approach to all of them, always ensuring the most commercially viable route was taken. He is great at managing relationships and it was always a pleasure working with him.”

BEATRIZ MONTOYA/CONSUMER MARKETING DIRECTOR
IPC MEDIA

“I worked with Kelly whilst at Thoughtworks and found him to be a most inspiring individual, his common-sense approach coupled with a deep understanding of Agile and business makes him an invaluable asset to any organisation. I can't recommend Kelly enough.”

PETER THATCHER, SENIOR ACCOUNT DIRECTOR
ThoughtWorks

“Kelly was a brilliant CTO and a great support to me in the time we worked together. I owe Kelly a great deal in terms of direction and how to get things done under sometimes difficult circumstances. Thanks Kelly.”

JULIE PEEL
GLASS'S INFORMATION SERVICES