[Recap] Week 6 Managing Design and Development - The halfway mark

Week 6 notes

Spacecraft Galileo - 14 year project – Cost: $1.6 Billion 

It was a high risk strategy by NASA. “All their eggs in one basket”

(Image credit spacecraftkits.com)

NASA Philosophy '92 - '01 ‘Faster, Better, Cheaper’ 18 Billion 146 payloads 10 Failures

Philosophy smaller scopes. “Hedging Bets”

Scope 4^th variable, other three variables (Faster (Time) Better (Quality) Cheaper (Cost))

Never going to solve the problem of balancing all 4 variables but we have to deal with them all.

Fred Brooks’ Law, adding manpower to a late software project makes it later"

People and months are interchangeable, Brooks

 

(Image credit  Dilbert.com)

Alpha à Beta/Prototypes à Shipped/General Availability (GA)/ Final Release

Don’t give people an idea that it’s finished until it is actually finished

Scope = Requirements

“If you actively manage scope, you can provide managers and customers with control of cost, quality, and time." (Kent Beck, 2000)

Tools to manage scope include MoSCoW (Stapleton 1997)

(Image Credit: Managing Design and Development Week 6 slides)

Quality: Hard to measure. Are you measuring quality of the process or quality of the product?

It’s hard to describe what quality is?

Kent Beck: 'Quality is a terrible control variable'.

Cost: Every business has sunk costs. Every company has necessary costs to produce value.

Cost are equipment resources people and money.

Scope: 'Identifying the problem is the problem'

IDEO method cards a way of gathering Requirements.

It’s important to understand where the requirements are coming from. Is it the customer/ business? Hidden hand of the analysts may skew the requirements and this affects the value delivered by the project.

(Image Credit: Managing Design and Development Week 6 slides)

User Story – Goal Driven requirements – Part of the Scrum method.

Story Title:

As a…. (Identity of user)

I want to….(Minor Objective)

So that…(Ultimate Goal)

This is evidence for the project team, to show that you are addressing the need.

(Image Credit: Managing Design and Development Week 6 slides)

When you’re unsure on the requirements; (Above Diagram)

Constraint diagram with the ID’s.

Unique ID’s are essential for requirements design.

Implementation

You going to the user base, being a host to them, hospitality. (Social Norms, introduction)

Introduction of new product

Where the theory meets the practice

The learn IDEO cards

Maintenance and Use

(Image Credit: Managing Design and Development Week 6 slides)

Design complexity osculates (Traditional)

Failure doesn’t plateau in software it spikes.(Actual) Diagrams above.