Module 4 - Planning For Implementation

Download as pptx, pdf, or txt
Download as pptx, pdf, or txt
You are on page 1of 14

THE UNIVERSITY OF ZAMBIA

Centre of Consultancy Training Unit


 

INTRODUCTION TO PROJECT MANAGEMENT


Module 4:
PLANNING FOR IMPLEMENTATION
The implementation phase
• After you have carefully planned your project, you will be ready to
start the project implementation phase, the third phase of the
project management life cycle.
• The implementation phase involves putting the project plan into
action.
• It’s here that the project manager will coordinate and direct
project resources to meet the objectives of the project plan.
• As the project unfolds, it’s the project manager’s job to direct and
manage each activity, every step of the way.
The implementation phase
• That’s what happens in the implementation phase of the
project life cycle: you follow the plan you’ve put together and
handle any problems that come up.
• The implementation phase is where you and your project team
actually do the project work to produce the deliverables.
• The word “deliverable” means anything your project delivers.
• The deliverables for your project include all of the products or
services that you and your team are performing for the client,
customer, or sponsor, including all the project management
documents that you put together
• The steps undertaken to build each deliverable will vary depending on
the type of project you are undertaking, and cannot therefore be
described here in any real detail.
• For instance engineering and telecommunications projects will focus on
using equipment, resources, and materials to construct each project
deliverable, whereas computer software projects may require the
development and implementation of software code routines to produce
each project deliverable.
• The activities required to build each deliverable will be clearly specified
within the project requirements document and project plan.
• Your job as project manager is to direct the work, but you need to
do more than deliver the results. You also need to keep track of how
well your team performs.
• (Scope, Budget, Time, Quality)
• (Risk Minimizing and Maximizing Benefits)
• The implementation phase keeps the project plan on track with
careful monitoring and control processes to ensure the final
deliverable meets the acceptance criteria set by the customer.
• This phase is typically where approved changes are implemented.
• Most often, changes are identified by looking at performance
and quality control data.
• Routine performance and quality control measurements
should be evaluated on a regular basis throughout the
implementation phase.
• Gathering reports on those measurements will help you
determine where the problem is and recommend changes to
fix it.
Change Control

• When you find a problem, you can’t just make a change, because
it may be too expensive or  take too long to do.
• You will need to look at how it affects the triple constraint (time,
cost, scope) and how it impacts project quality.
• You will then have to figure out if it is worth making the change. 
• If you evaluate the impact of the change and find that it won’t
have an impact on the project triple constraint, then you can
make the change without going through change control.
Change Control……
• Change control is a set of procedures that lets you make changes
in an organized way.
• Any time you need to make a change to your plan, you must start
with a change request. This is a document that either you or the
person making the request must complete.
• Any change to your project must be documented so you can figure
out what needs to be done, by when, and by whom.
• Once the change request is documented, it is submitted to a
change control board.
Change Control……
• A change control board is a group of people who consider changes
for approval. Not every change control system has a board but most
do.
• The change request could also be submitted to the project sponsor
or management for review and approval.
• Putting the recommended changes through change control will help
you evaluate the impact and update all the necessary documents.
• Not all changes are approved, but if the changes are approved, you
send them back to the team to put them in place.
• The implementation phase uses the most project time and
resources, and as a result, costs are usually the highest during
this phase.
• Project managers also experience the greatest conflicts over
schedules in this phase.
• You may find as you are monitoring your project that the
actual time it is taking to do the scheduled work is longer than
the amount of time planned.
Project Compression Tools
• When you absolutely have to meet the date and you are running behind,
you can sometimes find ways to do activities more quickly by adding more
resources to critical path tasks.
• That’s called crashing. Crashing the schedule means adding resources or
moving them around to bring the project back into line with the schedule.
• Crashing always costs more and doesn’t always work.
• There’s no way to crash a schedule without raising the overall cost of the
project. So, if the budget is fixed and you don’t have any extra money to
spend, you can’t use this technique
• Sometimes you’ve got two activities planned to occur in
sequence, but you can actually do them at the same time.
• This is called fast tracking the project.
• On a software project, you might do both your user acceptance
testing (UAT) and your functional testing at the same time, for
example.
• This is pretty risky. There’s a good chance you might need to
redo some of the work you have done concurrently.
• Crashing and fast tracking are schedule compression tools.
Managing a schedule change means keeping all of your
schedule documents up to date. That way, you will always be
comparing your results to the correct plan.
• After the deliverables have been physically constructed and
accepted by the customer, a phase review is carried out to
determine whether the project is complete and ready for
closure.

You might also like