Lance Gibbs' overview of moving from a plan driven approach to BPM delivery to a value-driven approach.

1. Moving to Value-Driven

2. The Major Paradigm Shift

4. Earned-Value Management of work

5. Focus on all the things we SHOULD do versus COULD do

6. Voice of Customer

9. “All or nothing” mindset

10. Long-tailed projects with milestones months away

11. Customer?...We know more than they do

12. We need an IT Application (Process-Driven?..really?)

13. Silos (SOA Team, BPM Team, Testing Team, Team for a Team)

14. Hand-off’s

15. The “how” something needs to be developed versus focusing on the need

17. Barrier to Entry? To do BPM with optimal effect Need to have an Iterative based delivery philosophy and competency And then…. Turning to a notion of process-centric delivery. The process is the first class citizen. All other supporting services and systems take their cue This is absolutely cultural and it takes a long time to work out... How do you start to move forward?

18. Actually its simple, or is it? Collaboration is Key Communication and collaboration Ownership – Democracy in delivery is over-rated Pragmatic approach to delivery, remove the “one and done” thinking “The challenge with communication is the illusion that it’s actually occurring” - anonymous