1. CSE Senior Design II Staged Delivery Instructor: Mike O’Dell

2. 1 CSE 4317 2 What is Staged Delivery? Requirements Analysis Concept & Planning Architectural Design Medium High Priority: Detailed design, implement and test Medium Priority: Detailed design, implement and test High Priority: Detailed design, implement and test Medium Low Priority: Detailed design, implement and test Low Priority: Detailed design, implement and test Run out of time and/or money Public Release Design-to-Schedule with risk reduction.

3. 1 CSE 4317 3 What is Staged Delivery?  A Lifecycle Model in which the: discrete stages  product is designed (details), developed and delivered in discrete stages prioritized,  requirements are clearly prioritized, and consistent with implementation dependencies  schedule determines  schedule determines the features that are delivered at each stage  the deliverable at any stage is “completed” potentially “shippable”

4. 1 CSE 4317 4 Why Consider Staged Delivery?  Staged Delivery can, potentially: reduce risk  significantly reduce risk associated with an “all or nothing” release signs of progress  provide clear signs of progress toward the ultimate product definition  improve product quality build-to-budget  facilitate a build-to-budget project team morale  help maintain team morale during the end game

5. 1 CSE 4317 5 Requirements for Staged Delivery product requirements  Clear and agreed statement of product requirements prioritization  Buy-in at all levels on prioritization of features/requirements  AND staging of deliverables stakeholders and end-users  Willingness of stakeholders and end-users to accept less than “the whole enchilada”

6. 1 CSE 4317 6 Requirements for Staged Delivery partition the deliverables  Ability to partition the deliverables into phased releases (stages) focus on quality  Commitment to focus on quality of each staged release architectural model  A clear and well-defined architectural model, precisely mapped to your requirements.

7. 1 CSE 4317 7 Advantages of Staged Delivery  Provides visible signs of progress for customers and stakeholders mitigates “90-90”  obviates, mitigates “90-90” rule predictable releases  Allows frequent and predictable releases  internal or external Beta  internal or external Beta releases/customer testing? frequent customer/end- user feedback  encourages early and frequent customer/end- user feedback marketing and sales team  engages marketing and sales team in process

8. 1 CSE 4317 8 Advantages of Staged Delivery early warning  Provides early warning of problems in development  Ability/Inability to deliver core features and functionality will be clear well before deadline.  Cuts down on project management overhead  less reporting… more frequent delivering! release options  Increases release options  e.g., release version 1, hold version 2, release version 3, …

9. 1 CSE 4317 9 Advantages of Staged Delivery estimation error  Reduces estimation error  smaller tasks to estimate -> less variance integration and test  Reduces integration and test effort But…

10. 1 CSE 4317 10 Major Risk with Staged Delivery Feature Creep, late in the game!

11. 1 CSE 4317 11 Keys to Success with Staged Delivery architecture is flexible  Be sure that the product architecture is flexible, supporting as many future directions as possible importance/priority  Plan stages in order of importance/priority first stage as early as possible  Define the first stage so that it can be delivered as early as possible themes  Define the stages in terms of “themes” stakeholder buy-in  Get stakeholder buy-in on staging plan  Tightly control/manage feature set

12. 1 CSE 4317 12 Keys for Senior Design Projects at least 3 or 4 stages  Define at least 3 or 4 stages for your delivery one week prior to “Early Prototype Preview”  Suggest timing your first stage (core functionality which support further development) to occur at least one week prior to “Early Prototype Preview” date interim release (stage)  One more interim release (stage) one week before Final Presentations.  Final stage completed 1-2 days before  Final stage completed 1-2 days before Final Presentations.