4. Specifying Deliverables Clearly
Friday, Oct. 21, 2005 or
Friday, Mar. 17, 2006, 9 am - 4 pm
at University of BC, Robson Square
See detailed agenda.
Projects deliver results required to help clients reach objectives. Deliverables
are the results produced by projects and tasks. Deliverables include systems,
product designs, facilities, equipment, hardware, networks, new methods and
procedures along with the associated documentation, training and support.
The fourth session covers key role that deliverables play in the planning
process. Your Statement of Work defining the deliverables, determines what
makes each project unique. Each deliverable requires a finite set of tasks to
produce based on the method of delivery. Selecting a method of delivery for
each deliverable influences schedule, cost and risk. The method of delivery
determines skill sets and resource types to produce that deliverable.
Specification of deliverables starts during project initiation. These
specifications are refined during the Requirements and the Design phases
of a project. Each deliverable can be broken down by a bill of materials.
Specification methods can be written, pictures, sketches, tabular,
mathematical, graphical, schematics and diagrams.
Understanding the deliverables provides the basis for
estimating and change control. Deliverables determine the size of your project.
Increasing scope of deliverables will increase your budget and schedule.
Specifications define what is to be delivered and provide the foundation for
change control.
Creating specifications to define the deliverables from projects, phases and
deliverables communicates what the project has to accomplish and establishes
agreement between the client and the project team.
Participants will learn to:
- Specify deliverables to achieve client objectives
- Decompose deliverables into components to create a bill of materials.
- Select delivery method for each component.
- Create an assembly sequence to assemble the project deliverables.
- Generate breakthrough solutions in project design.
- Generate a project schedule based on deliverables.
- Understand the importance of strategy in ensuring a successful project.
Click to register for this course
4. Specifying Deliverables Clearly, Agenda, Friday, Oct. 21, 2005 or
Friday, Mar. 17, 2006 - 9am - 4pm
| Oct. 21, 2005 |
Topic |
Specifying Deliverables Clearly agenda |
| 9am |
Specify Deliverables clearly |
- Understand Project deliverables.
- Document client requirements
-
|
| 9:30am |
Chunk project to reduce complexity with matrix decomposition. |
- Chunk project in to phases with WBS (work breakdown structure).
- Chunk project into deliverable types.
- Sequence stages for execution.
- Identify tasks within phase for each summary tasks.
- Define work breakdown structure with Progressive Decomposition.
- Structure tasks in clusters with Outlining.
- Reduce complexity with matrix decomposition.
- Define project management methodology with Microsoft Project.
- Simplify complex subjects with Patterns.
|
| 10am |
Coffee |
| 10:15 am |
Focus on deliverables before strategy and tasks |
- Avoid building a one legged stool.
- Reduce complexity by an order of magnitude.
- Build knowledge of project tasks with each project.
- Plan backwards from the final outcome.
- Ensure all work produces a useful output.
- Define method of delivery for each deliverable.
- Reuse task checklists from methodology.
- Evolve consistent basis for estimating.
|
| 11:45 |
Specify deliverables to achieve client objectives |
- Understand project planning deliverables.
- Prepare statement of work defining deliverables.
- Decide delivery method (build, buy, assemble) for each component.
- Define components with Bill of Materials.
- Construct assembly sequence.
- Create summary tasks.
- Prepare master schedule.
- Re-use sub-tasks to reduce planning effort.
- Create detailed plan for summary task cell in Master Project with Matrix decomposition.
|
| 12noon |
Lunch break |
|
| 1 pm |
Specify requirements to meet client objectives |
-
- Select specification methods.
- Select design tools.
- Define client requirements with JAD sessions.
- Plan quality assurance based on the requirements.
|
| 1:45 pm |
Design innovative solutions to meet customer requirements |
- Allocate design resources.
- Solve problems openly.
- Generate continuous stream of innovative products with Microsoft Strategy.
- Make design decisions.
- Package solutions for implementation.
- Generate systems solutions with Breakthrough thinking.
- Experiment with new ideas.
- Integrate design decisions.
|
| 2:30pm |
Coffee | |
| 2:45 pm |
Develop project strategy and master plan |
- Design project strategy.
- Select superior strategies.
- Reduce project delivery schedule.
|
| 3:30 pm |
Define deliverables for your case study |
- Identify deliverable types from your project.
- List the deliverables under each type.
- Create a bill of materials for the most complex deliverable.
- Create an assembly sequence for your deliverables with network diagram.
- Identify method of delivery for each deliverable using the table you created.
- Identify benefits of assembly sequence method.
|
Click to register for this course
email Brian Mullen with your questions
Updated: Oct.18, 2005.
Check out Questions and Answers for this session