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 Checklist Agile • 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 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