Hot answers tagged

15 votes

Managing scope creep in Agile

TL;DR Scope creep is a project risk, and must be controlled. However, in agile frameworks, scope is a variable constraint rather than a fixed one. To be an effective agilist, one needs to understand ...
user avatar
  • 47.4k
14 votes

Should I remove a User Story from a Sprint in progress if I know we can't complete it?

The Sprint backlog is a forecast, not a commitment In the 2011 revision of the Scrum Guide Jeff Sutherland and Ken Schwaber made an important change. They changed the word "commitment" to "forecast" ...
user avatar
13 votes
Accepted

Should I remove a User Story from a Sprint in progress if I know we can't complete it?

From the Scrum Guide: During the Sprint: No changes are made that would endanger the Sprint Goal; Quality goals do not decrease; and, Scope may be clarified and re-negotiated between the Product ...
user avatar
  • 1,210
11 votes
Accepted

What is the difference between requirement and scope?

I respectfully disagree with @DavidEspina. I don't think his answer is fundamentally wrong, but it doesn't match my answer. During project initiation (or in some contract work, prior to project ...
user avatar
  • 8,689
11 votes

Estimating when my project will be done

Just because you have 150 story points in your backlog now does not mean that work captures the work necessary from your stakeholders' perspectives. Every iteration, you should be evaluating what has ...
user avatar
  • 17.3k
9 votes

What is the difference between requirement and scope?

Product Specifications vs. Project Scope One assumes that you're not looking for dictionary definitions. We have Merriam-Webster and Wikipedia for that. For practical differences, I would suggest the ...
user avatar
  • 47.4k
9 votes

Does a Product Owner submit to Change Control before re-grooming Product Backlog?

Change Control Isn't an Agile Scoping Tool If he/she wishes to change the scope by adding in/taking out/re-prioritizing the Backlog the PO must submit a Formal Change Request/IOCA before taking an ...
user avatar
  • 47.4k
9 votes

Change requests processing best practice

Firm Fixed Price does not mean that the customer gets their desired solution for a fixed price. It means the customer agrees to negotiate about the scope and changes later and must pay extra for ...
user avatar
  • 5,687
8 votes

Estimating when my project will be done

Project Scheduling isn't a science, but an art. So it's not enough to provide you with a simple equation - which I'm sure you could also do using a calculator - you also have to "understand" your ...
user avatar
6 votes

How to track impact on planning due to scope changes?

You don't need any of that; close your spreadsheets. You need a change management process which include a governing body. Scope changes via new requirements is the type of change that would go ...
user avatar
  • 36.6k
6 votes
Accepted

Should impact on schedule because of scope change be reported as delay?

If you had a scope change, a legitimate one that was approved via your change process, then you should also have a corresponding and proportional schedule and cost change. This means that the delay ...
user avatar
  • 36.6k
6 votes

Change requests processing best practice

This is not a matter of change request best practices, but a matter of contract negotiation and relationship with the customer. There is a reason why fixed-price contracts for developing software are ...
user avatar
  • 13.6k
5 votes

How shall developers clarify PBI during its implementation?

As a Scrum Master I encourage team members to talk with the stakeholders. But I suggest they either do it in the presence of the Product Owner or brief the Product Owner as soon as possible after the ...
user avatar
5 votes
Accepted

How shall developers clarify PBI during its implementation?

Excellent question: To answer the question directly, yes, the developers can and should talk with the customer when possible. As you've pointed out though, the logistics of this can be difficult. ...
user avatar
5 votes
Accepted

Reduce Scope or Kill the Project?

So, there are a few things important to note. #1 - Assumptions - You assume one functionality takes 3-4 days to implement. Has this been confirmed with your team? Some tasks might be shorter (or ...
user avatar
5 votes

Managing scope creep in Agile

I usually answer by telling that the requirements need to be clearly defined before the project starts, and if there is any change during the project then it has to go through a change control process ...
user avatar
5 votes
Accepted

Are Delighters equivalent to Gold Plating?

These are two judgement labels applied to the exact same behavior, based on the outcome. If you get it right, the customer is delighted. If you get it wrong, you gold plated and the customer is ...
user avatar
  • 36.6k
5 votes

Estimating when my project will be done

In Scrum, a project is done when the client tells you that the product you delivered is good enough or when they don't want the product anymore. That can be when all the tasks currently on the backlog ...
user avatar
5 votes

Issue in managing changes

This is not an issue of managing changes in scope, this is an issue of trust and respect. When two business parties trust and respect each other, they will usually find ways to collaborate and agree ...
user avatar
  • 13.6k
4 votes
Accepted

What to do when someone says "that is not an acceptable solution"?

I see two (or well, three, if getting a new job counts ;-) ) possible ways to deal with such situations in general: When you receive a refusal like above: ask for clarification or more explanation, ...
user avatar
4 votes

Vendor selection being squeezed in as project's scope - how to best respond?

You are right to be concerned about this. Vendor selection can be a significant drain on time and resources, so you need to either ensure that this is excluded from the scope, or that sufficient time ...
user avatar
  • 6,763
4 votes
Accepted

Vendor selection being squeezed in as project's scope - how to best respond?

I am reading into this that the scope of the project and the firm fixed price are already negotiated and sealed. I can see why your customer thinks that vendor selection is part of the price because ...
user avatar
  • 36.6k
4 votes

How should a project manager handle a request for contracted software to produce twice as many reports as specified in the project's requirements?

One of the four values of agile is "Customer Collaboration over Contract Negotiation." The first thing to ask is "what is best for the customer?". Once you've done that, then you ask "is it covered ...
user avatar
4 votes
Accepted

How to minimize scope creep?

I've been dealing a lot with a scope creep over the last 2 years. I created a list of things that is a must to keep in mind in order to minimize the negative impact on the project. At first - you ...
user avatar
4 votes

Managing scope creep in Agile

tldr; Agile shifts the focus to the discovering and creating a solution for the customer's needs. Agile values "Responding to change over following a plan" because one must "Welcome changing ...
user avatar
  • 1,614
4 votes
Accepted

How can I force an epic to have a limited/finite scope?

TL;DR Whenever possible, think of epics as placeholders for more detailed product backlog items, not as evergreen stories. It's better to add new stories to the Product Backlog as they are discovered ...
user avatar
  • 47.4k
4 votes
Accepted

What techniques do you use to establish scope in agile

If I understand your Question correctly, you're asking how best to approach agile development in a situation where there is a hard cap on time? The obvious answer is to constrain the scope. And a ...
user avatar
  • 14.7k
4 votes
Accepted

What is the difference between scope creep and scope gap?

It’s All About Expectations “Unapproved” doesn’t really capture the essence of scope creep. In purely pragmatic terms, scope creep is a slow or gradual increase in scope beyond the original plan. A ...
user avatar
  • 47.4k
3 votes

What is the difference between requirement and scope?

To put it simply: Requirements is what the customer needs, scope is what will be done to fulfill them.
user avatar
  • 41
3 votes

How can I manage a rapidly changing copy deck with a fixed deadline?

A simple burn down chart might do the trick. We'll side step estimating and the value of it right now, that's a longer term thing that will help in the long run. Instead we'll go with fixed time as ...
user avatar

Only top scored, non community-wiki answers of a minimum length are eligible