Work Plan

1
Work Plan

• Spring 2004

2
Executive Summary

• In managing chaos, nothing is set in stone.
  Plans in particular need to be tentative, fluid,
  subject to continual revisions. The Work Plan
  must be revised with each deliverable if not more
  often.
• Team and Project Standards, Policies, Routines,
  even Leadership, should always be undergoing
  continuous improvement.
• Team name, motto, and logo can be subjected to
  revisions, especially now that the you are
  establishing your branding position. Leadership
  can be shared using Pair Programming technique.
• Including the updates and explanations in the
  deliverables gets you buy-in and good PR.

3
Work Plan

• Interactions With The Client
• Meetings Phase Deliverables Add-ons
• must appear in the Work Plan

4
PHASE Deliverables

• The PHASE Deliverables for this course are three
• Phase I Planning
• Phase II Analysis
• Phase III Design (includes Code)

5
REGULAR Deliverables

• The REGULAR Deliverables for this course are
  nine, see the Class Schedule
• Deliverable I The Team
• Deliverable II Business Analysis
• Deliverable III Analysis Plan
• Deliverable IV Requirements
• Deliverable V Models
• Deliverable VI User Interface
• Deliverable VII System Architecture
• Deliverable VIII Project Assessment
• Deliverable IX System Proposal

6
PHASE vs. REGULAR

• The Regular Deliverables make up the Phase
  Deliverables
• Phase I Planning
• Deliverable I The Team
• Deliverable II Business Analysis
• Phase II Analysis
• Deliverable III Analysis Plan
• Deliverable IV Requirements
• Deliverable V Models
• Phase III Design (and Code)
• Deliverable VI User Interface
• Deliverable VII System Architecture
• Deliverable VIII Project Assessment
• Deliverable IX System Proposal (includes The
  Code)

7
PHASE vs. REGULAR

• The PHASE Deliverables go to the client and/or
  the champion for payment
• The REGULAR Deliverables go to the instructor for
  feedback

8
Money
Project Team
Regular Deliverables
Phase Deliverables
Wisdom
Instructor
Client/Champion
9
PHASE vs. REGULAR

• After the instructor gives you feedback on the
  Regular Deliverables, you will use them to write
  the Phase Deliverables
• In your workplan, make sure you schedule adequate
  Phase Deliverable deadlines and Meetings with the
  client and/or champion

10
Add-ons

• You will bill the client with each Phase
  Deliverable.
• You will survey the champion with each Phase
  Deliverable.

11
Putting All Together

• Be willing to adjust
• The Work Plan is not carved in stone
• Use standards and routines as stepping stones,
  not as barriers
• Pair Programming vs. Divide and Conquer
• Less bugs Better code True Collaboration
• Not just for programming
• Creates knowledge, not just spreads it around
• Shared Leadership
• The deliverable leaders must collaborate, rework
  the product together, and sign-off as Phase
  Co-Leaders
• Leadership can be done in teams!