Plan Driven vs Value Driven Development

As part of the Scrum Tapas video series, Professional Scrum Trainer Punit Doshi discusses the difference between having your entire schedule driven by plans that are create at the beginning of a project vs defining the plans on a Sprint by Sprint basis to help ensure that you are always focused on the delivery of value by learning and adapting as you go.

[baymax]

Best explanation so far. Love how you just simply broke it down and clarify everything

[EnricoPezzini]

Simply explanation, so good to see something I can share with my boss hoping he sees the same things I saw

[himanshunayak]

simple and easy to understand, thanks.

[FrankRiedijk_NL]

Hmmmm….. I tend to disagree with your arguments. The essential difference in your description of the left model and the right model is not “plan vs iterations”, it’s that the customer is apparantly aware of the flexibility of requirements in the right model, where the customer seems to expect everything fixed in the left model. In the left model you would have the customer invest all effort into requirements refinement “at once” or at least “before the creation-efforts”, where the customer would be available for decisions during the creation-efforts in the right model; during iterations/sprints.

There is no other reason why the left model could not also deliver intermediate business results as part of the plan.

I still run into situations where a customer wants to know the full price of a system-creation or replacement up front. When you argue that requirements are “to be discovered” they will not understand and demand a (nearly) fixed price (particularly when you replace a system the customer would argue that all requirements are known, or at least 90%).

So I think that rather than blaming a “project plan” or “project management” of being the right way forward, I think the responsible team or manager should consider the level of customer understanding and build an approach based on that. I would argue that in both cases that would be a “planned approach”.
Just my 10 cents.

[olowoporoku]

Isn't this another way of explaining waterfall vs Agile?. Incremental value delivery is the basis of Agile

[rohitkanade]

what is the example of value driven module