1. CSE Senior Design II Timebox Development Mike O’Dell Based on an earlier presentation by Bill Farrior, UTA, modified by Mike O’Dell

2. 1 CSE 4317 2 What is a Timebox? DEADLINE FUNCTIONALITY

3. 1 CSE 4317 3 What is a Timebox?  A Rapid Application Development (RAD) technique that: schedule  focuses on schedule fixed time limit  imposes a fixed time limit of a project critical requirements  focuses on critical requirements scope creep  forbids (further) scope creep NOT  does NOT work for all types of projects very large projects projects in core business area(s) with other RAD techniques  is often deployed with other RAD techniques, such as Evolutionary Prototyping, CASE, SWAT and JAD

4. 1 CSE 4317 4 Why Consider Timebox?  Things don’t always go as planned  Scope changes  Estimates were inaccurate  People  Timebox Development provides a way to redefine the product to fit the schedule  Schedule is the priority  Avoids the “90% complete” problem  Controls product definition

5. 1 CSE 4317 5 Need for a 90-Day Lifecycle  First used at DuPont  Scott Shultz  Documented by James Martin  “...Better to have a system of limited functionality working quickly than to wait two years for a comprehensive system.”  The application must be built so that it can be added to quickly The two year wait...

6. 1 CSE 4317 6 Scope Creep Problem  Users/developers keep adding  design slow to converge  By placing a rigid limit on delivery, developers are less inclined to experiment  Excessive functionality in software and electronic products often goes beyond usefulness Enough, already!

7. 1 CSE 4317 7 The Timebox Approach  Implementation  Implementation/construction phase practice essential features first  Implement essential features first, then other features as (if) time permits  The product “grows like an onion” with the essential features at the core  Prototype and evolve  Prototype and evolve approach  Requires heavy end-user/sponsor involvement 60-120 days  Usually last 60-120 days

8. 1 CSE 4317 8 The Timebox System Definition/ Priorities End-user Review & Feedback Build & Evolve Prototype Evaluate/ Deliver System Prototype Request for Change Timebox Development Need for large- scale change or enhancement ProductRejected Review Board

9. 1 CSE 4317 9 Review Board system definition (priorities)  Signs off on system definition (priorities) prior to timebox  Monitors  Monitors progress  Evaluates completed system  YES / NO  YES / NO decision on completion.  Decision made quickly on each stage  Includes:  executive owner  user representative(s)  QA professional

10. 1 CSE 4317 10 Timebox Requirements  Clearly prioritized list of features essential  What’s essential and what’s not  Minimum core feature set  Realistic schedule  Realistic schedule estimate  Right kind of project extremely rapid turn-around  Ability for extremely rapid turn-around on prototypes (Evolutionary Prototyping?)  Sufficient end user involvement  Quick feedback  Quick feedback is essential (JAD?)

11. 1 CSE 4317 11 Variation: Parallel Timeboxing  Interfaces among subsystems determined, and held constant  Complex projects broken down into very small projects, which proceed in parallel TIME 

12. 1 CSE 4317 12 Dupont Experience productivity improvements on certain projects  Extraordinary productivity improvements with Timeboxing on certain projects  80 function points per PM with Timeboxing vs. 15-25 without  No projects rejected with Timeboxing  Risk lowered/eliminated in many projects

13. 1 CSE 4317 13  Advantages  Speed  Quick feedback on basic functionality  Smaller teams reduce communication overhead  Problem tasks become visible  Can be used to save a doomed project  Disadvantages  May be attempted as a last-ditch effort on unsuitable projects  Improperly applied (wrong project or wrong approach), may sacrifice quality instead of features Summary: Timeboxing

14. 1 CSE 4317 14 Keys to Success with Timeboxing 60-120 days  Only use for projects that can be implemented within 60-120 days core feature setprioritization  Ensure that all stakeholders agree on minimum core feature set and prioritization of features bought in motivated properly  Be sure that team has bought in to aggressive Timebox schedule- and motivated properly to support it.  Focus on quality  Focus on quality throughout the process  Cut features if necessary, don’t extend the Timebox deadline

15. 1 CSE 4317 15 Timebox and Scrum (simplified)  Scrum is a sequence of short Timeboxes (called Sprints). Each Sprint…  focuses on COMPLETING an agreed set of product features/functions  has an agreement with the product owner on the product requirements (called the Product Backlog)  Each Sprint has a planned list of to-do’s (called the Sprint Backlog)  Each Sprint has a specified, HARD DEADLINE for completing the specified items