diane pozefsky. interactions there is no “right answer” typically people and product are fixed...

16
Diane Pozefsky THE 3 P’S:

Upload: brielle-tonkin

Post on 15-Jan-2016

219 views

Category:

Documents


0 download

TRANSCRIPT

Page 1: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Diane Pozefsky

THE 3 P’S:

Page 2: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Interactions

There is no “right answer” Typically people and product are fixed … can adapt process (which is where we will start)

Page 3: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Processes

Page 4: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Fundamental Steps

Requirements Design Implementation Test Deployment Maintenance

Page 5: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Processes

Differ by how often you do the stepsFocus and emphasis

Points on the spectrum Differences in overhead Three fundamental processes

WaterfallSpiralIterative

Page 6: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Waterfall Do it once Traditional model Used for large next version releases, especially when well understood product tightly coupled changes

Page 7: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Waterfall

1970s Built on 1950’s

stage-wise process

Recognized the need for feedback LimitedHeavy process

Page 8: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Waterfall Pros

Simple documentation managementClean design phase

ConsLeast flexibilityNo early feedback

Page 9: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Iterative (a.k.a. Agile) Many iterations Each iteration is on a fixed cycle

Typically biweekly

Used for projects with

lots of small independent, but well understood, changes

small development team

strong client involvement

Page 10: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Iterative

Reaction to waterfall Derived from “evolutionary” process

Requirements and specs evolve over time Two well-known models

Extreme programmingSCRUM

Page 11: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Iterative (a.k.a. Agile) Pros

Fast feedback on problems Very adaptable to any changes Lots of versions to work with Heavy user involvement

Cons Document maintenance Code maintenance Requires good automation

Page 12: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Spiral Few iterations Each iteration adds new requirements Used often for projects with less well

defined requirements

Page 13: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Spiral

Risk based Barry Boehm 1988 “A Spiral Model of

Software Development and Enhancement”

Page 14: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Spiral Pros

Adaptation to changes based on risksGood customer interactionEarly versionLimited iterations provide phase structure

ConsDocument maintenance

Page 15: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Historical Perspective

Waterfall: 1970, built on 1950’s stage- wise processes

Recognized need for feedback Iterative (agile): late 70s,modeled on

evolutionary model

Didn’t work well for large products Spiral: 1988, risk-based

Page 16: Diane Pozefsky. Interactions  There is no “right answer”  Typically people and product are fixed  … can adapt process  (which is where we will start)

Unified Process Variant of Spiral Identifies that

iterations differ Also known as

Rational Unified Process (Rational products)

Phases

Cor

e P

roce

sses