1 / 11

Staged Delivery

Staged Delivery. Instructor: Manfred Huber Partially adapted from Mike O ’ Dell. What is Staged Delivery?. Concept & Planning. Design-to-Schedule with risk reduction. Requirements Analysis. Architectural Design. High Priority: Detailed design, implement and test.

robertlevi
Download Presentation

Staged Delivery

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Staged Delivery Instructor: Manfred Huber Partially adapted from Mike O’Dell

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

  3. What is Staged Delivery? • A Lifecycle Model in which the: • product is delivered in discrete stages • requirements are clearly prioritized • schedule determines the features that are delivered at each stage • the deliverable at any stage is “completed”potentially “shippable” CSE 4317

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

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

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

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

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

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

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

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

More Related