CSE Senior Design IICSE Senior Design II

Staged DeliveryStaged Delivery

Instructor: Mike O’DellInstructor: Mike O’Dell

1

CSE 4317 2

What is Staged Delivery?What is Staged Delivery?

RequirementsAnalysis

Concept & Planning

ArchitecturalDesign

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

PublicRelease

Design-to-Design-to-Schedule with risk Schedule with risk reduction.reduction.

1

CSE 4317 3

What is Staged Delivery?What is Staged Delivery?

A Lifecycle Model in which the: product is designed (details), developed

and delivered in discrete stages discrete stages requirements are clearly prioritizedprioritized, , and

consistent with implementation dependencies

schedule determinesschedule determines the features that are delivered at each stage

the deliverable at any stage is “completed” potentially “shippable”

1

CSE 4317 4

Why Consider Staged Delivery?Why Consider Staged Delivery?

Staged Delivery can, potentially: significantly reduce riskreduce risk associated with

an “all or nothing” release provide clear signs of progresssigns of progress toward

the ultimate product definition improve product qualityimprove product quality facilitate a build-to-budget build-to-budget project help maintain team morale team morale during the

end game

1

CSE 4317 5

Requirements for Staged Requirements for Staged DeliveryDelivery

Clear and agreed statement of product product requirementsrequirements

Buy-in at all levels on prioritizationprioritization of features/requirements AND staging of deliverables

Willingness of stakeholders and end-stakeholders and end-usersusers to accept less than “the whole enchilada”

1

CSE 4317 6

Requirements for Staged Requirements for Staged DeliveryDelivery

Ability to partition the deliverablespartition the deliverables into phased releases (stages)

Commitment to focus on qualityfocus on quality of each staged release

A clear and well-defined architectural architectural modelmodel, precisely mapped to your requirements.

1

CSE 4317 7

Advantages of Staged DeliveryAdvantages of Staged Delivery

Provides visible signs of progress for customers and stakeholders obviates, mitigates “90-90”mitigates “90-90” rule

Allows frequent and predictable releasespredictable releases internal or external Beta internal or external Beta releases/customer

testing? encourages early and frequent customer/end-frequent customer/end-

user feedbackuser feedback engages marketing and sales teammarketing and sales team in process

1

CSE 4317 8

Advantages of Staged DeliveryAdvantages of Staged Delivery

Provides early warningearly 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!

Increases release optionsrelease options e.g., release version 1, hold version 2,

release version 3, …

1

CSE 4317 9

Advantages of Staged DeliveryAdvantages of Staged Delivery

Reduces estimation errorestimation error smaller tasks to estimate -> less variance

Reduces integration and testintegration and test effort

But…

1

CSE 4317 10

Major Risk with Staged DeliveryMajor Risk with Staged Delivery

Feature Creep, late in the game!

1

CSE 4317 11

Keys to Success with Staged Keys to Success with Staged DeliveryDelivery

Be sure that the product architecture is architecture is flexibleflexible, supporting as many future directions as possible

Plan stages in order of importance/priorityimportance/priorityDefine the first stagefirst stage so that it can be

delivered as early as possibleas early as possibleDefine the stages in terms of “themesthemes”Get stakeholder buy-instakeholder buy-in on staging planTightly control/manage feature set

1

CSE 4317 12

Keys for Senior Design ProjectsKeys for Senior Design ProjectsDefine at least 3 or 4 stages at least 3 or 4 stages for your

deliverySuggest timing your first stage (core

functionality which support further development) to occur at least one week one week prior to “Early Prototype Preview” prior to “Early Prototype Preview” date

One more interim release (stage) interim release (stage) one week before Final Presentations.

Final stage completed 1-2 days before Final stage completed 1-2 days before Final Presentations.