110 likes | 495 Views
2. Overview:. Inescapable Fixed Time, Fixed Scope ProjectsAgile Methods To Apply To The ProblemSuccesses and FailuresWhat We Think Is HappeningRecommendations For The Future. 3. Inescapable Fixed-Time, Fixed Scope Projects. Our Customers: Brick
E N D
1. Unfixing the Fixed Scope Project Using Agile Methodologies to Create Flexibility in Project Scope Jeff Patton
Tomax Corporation
Salt Lake City, UT
Jpatton@tomax.com
2. 2
3. 3 Inescapable Fixed-Time, Fixed Scope Projects Our Customers: Brick & Mortar Chain Retailers
Factors That Affect and Lead to Fixing Delivery Date
Busy & Slow Seasons – High Risk Installing During Busy Seasons
Large Numbers of Physical Locations
High Rollout Costs
High Training Costs
Desire to Pre-Schedule Training and Rollout Resources
Factors That Lead To Fixing Scope
Cost Justification for the Project = Required ROI
Features Selected For Their ROI
Features Fixed Into Original Contract Bid
Although Our Product is “Shrink-Wrapped”, Most Customers Require Some Custom Development – “Gaps”
4. 4 The Iron Triangle
5. 5 Inventing a Solution Acquire a Better Understanding of Scope
Employ Interaction Design Guidelines
Usage-Centered Design
Collaborative U-CD Sessions for Requirements Gathering and Scope Definition
Acquire Better Understanding of Ongoing Progress
Scrum Style Iteration Followed by Customer Demonstration
XP-Style Velocity Calculation and “Yesterday’s Weather” Estimation.
6. 6 Applying The Solution Interaction Design Helped With Prioritization
XP Estimation Helped Attach Suitable Value To Features
Iterative Development Helped Us Understand Progress
7. 7 No Escape The Project Was Behind
All the “required” scope would not be completed on time.
8. 8 Successful Failure Release Phase I With Missing Scope
Missing features were low priority
High priority features identified late were included
It wasn’t easy to determine if we had or hadn’t failed
No one seemed to mind the missing features
9. 9 *“I do not think that means what you think it means” Collaborative Design & Scoping Sessions Established Customer Trust
The customers didn’t mind scope changes because they trusted us and felt involved
Decoupling Features During Development Allowed Features To Be Dropped
We were able to cut scope late in the release cycle because we’d successfully decouple feature design
10. 10 Today’s Strategy Keep Design General And Scope Soft
Recognize Customers Aren’t Adversaries – Establish Trust
Write A Collaboration Plan
Collaborative Design & Scoping
Regular Progress Demonstrations
Phase Delivery
Plan To Drop Features – Decouple Design
11. 11 Thanks. Questions?