Software Engineering Process I

Copyright © 2012-2014 by Mark J. Sebern

Software Engineering

Process ISE-2800-04

Sprints


Sprint Timeboxing• Establishes a WIP limit• Forces prioritization• Demonstrates progress• Avoids unnecessary perfectionism• Motivates closure• Improves predictability

How would you assess these claimed benefits?

Any drawbacks you can think of?


Sprint Timeboxing• Establishes a WIP limit• Forces prioritization• Demonstrates progress• Avoids unnecessary perfectionism• “90% best solution”• 1st 90%: 90% of time; remaining 10%: other 90%

of time




Sprint Timeboxing• Establishes a WIP limit• Forces prioritization• Demonstrates progress• Avoids unnecessary perfectionism• Motivates closure• Improves predictability




Short Sprint Duration

• Ease of planning• Fast feedback• Improved return on investment• Bounded error• Rejuvenated excitement• Frequent checkpoints

What is your opinion of these claims?

Any disadvantages?





Any disadvantages?

More frequent deliverables





Any disadvantages?


Consistent Duration?• Cadence

Benefits?

• Simplified planning?

• Any exceptions?


Consistent Duration?• Cadence

Benefits?

• Simplified planning?

• Any exceptions?• Test alternative durations.

• Work around end-of-year holidays

• Product release before end of sprint

• NOT: need more time to finish


Sprint Goal• Single sentence

• Describes business purpose and value

• How different from a collection of PBIs?

• What changes are allowed?

Mutual commitment? Focus?

Why not allow goal changes?


Definition of Done• Potentially shippable?

• Defined by checklist?

• Fixed or evolving?

• Versus "acceptance criteria" or "conditions of satisfaction"?

• When need notion of “done-done”?

Textbook, Table 4.1

What happens if sprint time runs out?


Clear as Mud?

• Checkpoint:• What do you understand about

sprints from this basic introduction?

• What is unclear or missing?

Software Engineering Process I

Documents

Transcript of Software Engineering Process I