Waterfall• Complete Requirements Docs• Complete Plan Needed (Gantt) • Little Customer Involvement• Start to Finish• Task Driven• Tasks, Millstones are

commitments• Milestone = DoD for phase• Handoff driven• Changes become issues• Phase Gate Delivery (Value at

End)• Project Charter details Economic

Biz Value being delivered to Organization

• Formal CCB (Change Control Board)

• Roadmaps are set w/o DEV team consultation

1

ChecklistAgile• JIT Doc means complete

documentation • Master Schedule (SoS) showing

interlocks and Integration points with Marketing / Release Roadmap)

• Constant Customer Involvement• Product Backlog is prioritized from

both Economic and Customer Needs

• PO defines solutions, w/ biz problem

• No Changes during Sprints• Story Estimation, PO (what) and

the team (how) + team forecast, No Hard Commit

• User Stories w/ AC• Actionable DoD• No Handoff • Outcome Driven w/ Business Value

in Economically Quantifiable & Measurable

• Iteration, delivering working software

• Change is expected but not chaotic

• Roadmaps set with DEV team consultation

• Poki Yoki, make is easy to do the right thing and HARD to do the wrong thing

FrankenScrum• Little Documentation• Agile used as a license not to

plan (No master schedule)• Release driven Customer

Involvement• Product Backlog is a place holder• PO defines solutions, w/o stating

biz problem• Changes during Sprints• Est. as Commitment (Est by

Management)• User Stories without AC• No Actionable DoD• Handoff Driven• Outcome Driven BUT Biz Value is

not measured in economic terms• Iteration, delivering working

software but change causes chaos

• Roadmaps are set w/o DEV team consultation

• Not practicing Poki Yoki

• Sometimes Teams measures value as the number of features• This leads to feature overbuild …the more features we build the better …(not true)• As an organization …

• how do you measure the value of features during release / customer acceptance?• Great, good enough, or the users just don’t use the feature• Users may not like, want, need, or cause people to drop off the page or

leave the app• Feature overbuild increases time, money and likelihood of quality issues

• In order to measure we need to Quantify • Measure PBI from an 80 / 20 POV

• 80% of the value resides in 20% of the features • Aligning customer feedback with PBI Priority and Economic POV

• Measure utilizations rates, conversion rate, what pages are users dropping off (see next slide)

• What are people actually doing with our product?

2

How to Quantify Features?

3