iterdev2a 1 Iterative Development Royce, “Successful Software Management Style: Steering and Balance”, IEEE Software sep/oct 05

iterdev2a 2 Essential ideas in the Articles

iterdev2a 3 Rationale of Iterative Development “Traditional project management approaches in software-intensive projects don’t encourage the steering and adjustment needed to reconcile significant levels of uncertainty in the ■ problem space (what the user really wants or needs), ■ solution space (what architecture and technology mix is most appropriate), and ■ planning space (including cost and time constraints, team composition and productivity, stakeholder communication, and incremental result sequences).”

iterdev2a 4 Measurement Just as the movie industry gets action on film, we too must get increments of software into executable form to make things tangible enough to assess progress and quality.

iterdev2a 5 Results This iterative management style is results rather than activity-based. In the world of software, real results are executable programs. Everything else (requirements documents, usecase models, design models, test cases, plans, processes, documentation, and inspections) is secondary—simply part of the means to the end.

iterdev2a 6 precision A common failure pattern is developing a five-digits-of-precision specification when the stakeholders have only a one-digit-of-precision understanding of the problem, solution, or plan.

iterdev2a 7 Evaluation of these ideas

iterdev2a 8 What do we apply to 541 project?

iterdev2a 9 Our Goal: Project Plan u The size and important features of the product to be produced u The division of tasks into iterations u Size and effort estimations of work tasks

iterdev2a 10 Identify Subtasks u Identify all the different subtasks necessary to achieve product –Include units if possible, e.g. number of ppt slides u For each subtask, identify milestone(s) and completion criteria u Establish dependencies

iterdev2a 11 Checkpoints, Milestones, or Inch- pebbles u “A checkpoint is an objectively identifiable point in a project” u e.g. not “coding is 90% complete” u possible – “design is ready for review, design has been reviewed by all team members.” u “a checkpoint for every five hours or so of work”

iterdev2a 12 Project Plan u establish subtasks (wbs) u establish checkpoints (wbs) u establish dependencies (gannt or pert) u establish dates (gannt chart) u assign subtasks

iterdev2a 13 Project Plan for Iteration 1 u Must have time in minutes for each leaf task u No leaf task can be more than 7 days before successor u Each leaf task must have completion criterion u Post on web by Wednesday, 1/25

iterdev2a 14 Thursday, Jan 19 u Read rest of articles u Read about Earned Value – SOS 3.7