2. Other Processes
▪ Development Process is the central process
around which others revolve.
▪ Methods for other processes often influenced
by the dev process.
▪ We have looked at various models for dev
process.
a “real” process likely derived from a model
2
5. The Typical PMs Role
▪ Overall responsibility for the successful
planning, execution, monitoring, control and
closure of a project.
▪ Primary point of contact with project
sponsors.
▪ Key tasks:
Plans
Meets
Communicates
▪ Project Management = Leadership
5
6. Qualities of a PM
1. Inspires a SharedVision.
2. Good Communicator.
3. Integrity.
4. Competence.
5. Ability to DelegateTasks.
6. Cool Under Pressure.
7. Team-Building Skills.
8. Problem Solving Skills.
6
7. Planning
▪ Done before project begins.
▪ Key tasks:
Cost and schedule estimation.
Staffing.
Monitoring and risk management plans.
Quality assurance plans.
7
10. Background
▪ Main goal of inspection process is to detect
defects in work products.
▪ Earlier used for code, now used for all types
of work products.
▪ Is recognized as an industry best practice.
▪ Data suggests that it improves both Q&P.
10
11. Functionality Needed
▪ Capture current state of programs.
▪ Capture latest version of a program.
▪ Undo a change and revert back to a specified
version.
▪ Prevent unauthorized changes.
▪ Gather all sources, documents, and other
information for the current system.
11
13. Background
▪ Requirements change at any time during the
development.
▪ Changes impact the work products and the
various configuration items.
▪ Uncontrolled changes can have a huge
adverse impact on project in cost/scheduled.
▪ Changes have to be allowed, but in a
controlled manner.
13
15. What is a Project?
• Includes an element of something new
• Has a beginning and an end.
• Often interdisciplinary and as such involves
people with differing backgrounds.
16. What is the Project Management?
• The application of knowledge, skills, tools
and techniques to project activities in order
to meet or exceed stakeholder needs and
expectations from a project.
17. Why to use project management
tools and techniques?
• Focus and clarify our thinking so that we
proceed in a systematic, effective, and
efficient manner.
• Identify everything that needs to be
considered and done to reach a goal
(includes what is to be communicated and
to whom).
• Identify who will do what and time frames.
18. Why to use project management
tools and techniques?
• Reduce the confusion, frustration,
backtracking, and errors that can be
associated with developing or introducing
something new.
19. Where are we going?
• Overall project may have three distinct
components:
1. Feasibility study.
2. Pilot.
3. Operational.
20. Feasibility
• Should we introduce virtual reference?
Why or why not?
• What’s involved in introducing virtual
reference?
• What do we need to know, what do we need
to do, what decisions do we have to make in
order to answer the two previous questions?
21. Pilot Project
• Develop a plan for a pilot.
• Activate the pilot.
• Develop an assessment plan for the pilot.
• Activate the assessment plan.
• Decide whether we’re going into full
operation and, if so, what adjustments
should be made.
22. Move to operational
• Develop a plan to move from pilot to
operational.
• Activate the plan.
• Develop a plan for on-going assessment.
• Activate the assessment plan.
24. Overview
• Project Control Elements.
• Project Control Processes.
• Post Control Report.
• Controlling Change.
25. Purposes of Control
• There are two fundamental objectives of control:
– 1. The regulation of results through the alteration of
activities.
– 2. The organizational assets.
• The project manager needs to be equally attentive to both
regulation and conservation.
• The project manager must guard the physical assets of
the organization, its human resources, and its financial
resources.
26. Project Control
• Control is the last element in the
implementation cycle of planning-monitoring-
controlling.
• Control is focused on three elements of a
project:
– Performance
– Cost
– Time
Performance
Cost Time
27. Three Types of Control Processes
• Decisions must be made concerning:
– At what points in the project will control be
exerted?
– What is to be controlled?
– How it will be measured?
– How much deviation will be tolerated?
– How to spot and correct potential deviations
before they occur?
28. Benchmarking
• A recent addition to the arsenal of of project
control tools is benchmarking.
• Benchmarking makes comparisons to “best in
class” practices across organizations.
• Some successful organizations have been
benchmarked on their best practices and key
success factors for projects being conducted in
functional organizations.