Project Management Central

Please login or join to subscribe to this thread

Topics: Benefits Realization, IT Project Management, Strategy
Scope Creep Vs Value based delivery
Network:981



So far I was very proud that I'd meticulously defended my projects against scope creep. But I was missing the point, the real reason organizations should undertake projects is to achieve value.

So what should be the priority– Defending Scope Creep Vs Value based delivery?
Sort By:
Page: 1 2 next>
Network:1636



Hi Arvind,
In waterfall model we define and lock the scope. This is with the assumption that overall scope (cost Vs) value is determined and we stick to it. But if we go via Agile methodology, then we evaluate the requirements as we get them and determine the value and take them up. Its 2 different approaches.
In first Waterfall approach, budget is fixed and hence we have to deliver the scope. Any upcoming changes or scope creep should go via change request board and evaluated for its cost benefit analysis.
Network:981



Thank you Sachin and I agree that we always bid with fixed scope if we propose waterfall however if even scope is fixed and finalized, customers has always new things which is addition to scope. Can we say 'no' to customer?
and other thought, in both model - Waterfall & Agile, there is certain budget defined as per organization goal and to achieve certain business benefits. Can we go beyond budget?
Network:259



Hi Arvind,

Whatever methodology we are using there is always a room open to include the functionality into the scope. The point is to follow the change management process.

Agile supports the dynamic mechanism of change and re-prioritization very well. Even for waterfall you need to avoid gold platting, however any change if it is critical for the client it has to be reevaluated for the impacts and only be entertained once approved. Once the change impact is approved it means you are within budget..
Network:981



Agree Naveen!!
Network:529



Hi Arvind,

I believe that value based delivery is one of the main points that several projects miss in term of defending scope creep and at the end the project delivers less value than expected. I believe that part of this is due to not setting expectations correctly for the stakeholders by answering the question, "What do yo we expect to improve in our business if this project is successful" sometimes you deliver the project scope and final deliverables but due to not looking at the big picture from outside on how the project benefits the company, the project is successful but it is deemed as a business failure.
...
1 reply by Arvind Kumar
Jun 18, 2018 1:19 PM
Arvind Kumar
...
Thank you !!
Network:1669



Value and Scope creep are not related. The driven is value.
Network:14401



It's all about delivering value. Scope may be extended provided the stakeholders/customers see value in whatever decision they make that impacts time/cost/scope.
Network:1977



I understand the basis of the question, but without any value there is no project, thus no scope. Value delivery would be slotted and grouped by MVP and priority. Within each of those contexts is a set of work to be accomplished. So at this point, it is the feature that is the scope which will decompose as needed to achieve the intent.

In a traditional waterfall setting where the 'overall' scope is pre-defined there are still objectives to be met. The objectives are delivered through what is assumed to be a finite scope. Luckily, since we all know that is only in theory, we have a CM process to insert in where needed. The fun begins when deciding what falls under the umbrella of what is needed to deliver on the objective and what is 'extra' and can be slotted in the parking lot for later efforts/enhancements. Then there is the whole time/budget discussion which plays a role in those prioritization activities.
...
1 reply by Arvind Kumar
Jun 18, 2018 1:25 PM
Arvind Kumar
...
Thank you Andrew for great clarification.
Network:1107



Arvind -

It's not an either/or situation - scope creep is unmanaged change. Regardless of the lifecycle used to deliver projects (adaptive or deterministic), the focus should always be on delivering business value and ensuring that changes are being appropriately managed whether that is via project change control or via discipline in how we manage our product backlogs.

Kiron
...
1 reply by Arvind Kumar
Jun 18, 2018 1:21 PM
Arvind Kumar
...
Thank you Kiron for valuable comments! I will incorporate in my next article on this topic.
Network:981



Jun 15, 2018 4:21 AM
Replying to Seif Eldin Soliman
...
Hi Arvind,

I believe that value based delivery is one of the main points that several projects miss in term of defending scope creep and at the end the project delivers less value than expected. I believe that part of this is due to not setting expectations correctly for the stakeholders by answering the question, "What do yo we expect to improve in our business if this project is successful" sometimes you deliver the project scope and final deliverables but due to not looking at the big picture from outside on how the project benefits the company, the project is successful but it is deemed as a business failure.
Thank you !!
Page: 1 2 next>  

Please login or join to reply

Content ID:
ADVERTISEMENTS

The rumors of my death have been greatly exaggerated.

- Mark Twain

ADVERTISEMENT

Sponsors

Vendor Events

See all Vendor Events