PROJECT MANAGEMENT
UNIT- 4
Dr. A.K. SUBRAMANI
D.E.E.E., B.Tech (IT)., M.B.A., Ph.D., UGC-NET.
Assistant Professor (Sl. Grade),
HR & OB Department, School of Management Studies,
Greater Noida, Uttar Pradesh.
Mob: 9884485825.
Email: ak.subramani@sharda.ac.in/
draksubramani@gmail.com
Dr. A. K. Subramani @ SBS, Sharda University 18 May 2018
Course Details
S. Particulars
No
Project Execution
4.1 Project Team Development - Acquiring,
Managing and Developing Project Team, Multi-
project Scheduling
4.2 Managing Project Risk-Techniques and Risk
Response
4.3 Review Meetings; Distributing Progress Reports
4.4Documenting Lessons Learnt
Dr. A. K. Subramani @ SBS, Sharda University 18 May 2018
Project Team Development
1. Forming
The first stage of team development is forming, which is a lot like
orientation day at college or a new job. You could even compare it to going
out on a first date.
The team has just been introduced and everyone is overly polite and
pleasant. At the start, most are excited to start something new and to get to
know the other team members.
It includes: Member’s skills, background and interests, Project goals,
Timeline, Ground rules, Individual roles.
As the group starts to familiarize themselves, roles and responsibilities will
begin to form. It is important for team members to develop relationships
and understand what part each person plays, because this stage focuses
more on the people than on the work.
Project Team Development
2. Storming
In the storming stage, the reality and weight of completing the task at hand
have now hit everyone. The initial feelings of excitement and the need to be
polite have likely worn off.
Personalities may clash. Members might disagree over how to complete a
task or voice their concerns if they feel that someone isn’t pulling their
weight. They may even question the authority or guidance of group leaders.
But, it is important to remember that most teams experience conflict. If you
are the leader, remind members that disagreements are normal.
Some teams skip over the storming stage or try to avoid conflict at
whatever cost. Avoidance usually makes the problem grow until it blows
up. So, recognize conflicts and resolve them early on.
Project Team Development
3. Norming
During the norming stage, people start to notice and appreciate
their team members’ strengths. Groups start to settle into a groove.
Everyone is contributing and working as a cohesive unit.
Of course, you may still think that your tech guy’s choice in music
is horrible. But, you also admire his knowledge of web design and
coding skills, and value his opinions on anything tech-related.
Storming sometimes overlaps with norming. As new tasks arise,
groups may still experience a few conflicts. If you’ve already dealt
with disagreement before, it will probably be easier to address this
time.
Project Team Development
4. Performing Stage
In the performing stage, members are confident, motivated
and familiar enough with the project and their team that they
can operate without supervision. Everyone is on the same
page and driving full-speed ahead towards the final goal.
The fourth stage is the one that all groups strive to reach. Yet,
some do not make it. They usually fail to overcome conflict
and can’t work together.
Project Team Development
5. Adjourning
In 1977, Tuckman added a fifth stage called adjourning.
(Sadly, not a perfect rhyme.) Once a project ends, the
team disbands. This phase is sometimes known as
mourning because members have grown close and feel a
loss now that the experience is over
Multi-Project Scheduling
Step 1: Identify the Risk. Project team uncover, recognize and describe
risks that might affect the project or its outcomes. There are a number of
techniques you can use to find project risks. During this step team need to
start preparing Project Risk Register.
Step 2: Analyze the risk. Once risks are identified projct team determine
the likelihood and consequence of each risk. They develop an
understanding of the nature of the risk and its potential to affect project
goals and objectives. This information is also input to Project Risk
Register.
Step 3: Evaluate or Rank the Risk. Project team evaluate or rank the risk
by determining the risk magnitude, which is the combination of likelihood
and consequence. They make decisions about whether the risk is acceptable
or whether it is serious enough to warrant treatment.
Risk Management Process
Loss Reduction: Loss reduction is a technique that not only accepts risk,
but accepts the fact that loss might occur as a result of the risk. This
technique will seek to minimize the loss in the event of some type of threat.
For example, a company might need to store flammable material in a
warehouse. Company management realizes that this is a necessary risk and
decides to install state-of-the-art water sprinklers in the warehouse. If a fire
occurs, the amount of loss will be minimized.
Separation: Separation is a risk control technique that involves dispersing
key assets. This ensures that if something catastrophic occurs at one
location, the impact to the business is limited to the assets only at that
location. On the other hand, if all assets were at that location, then the
business would face a much more serious challenge. An example of this is
when a company utilizes a geographically diversified workforce.
Duplication: Duplication is a risk control technique that essentially
Risk control techniques
Common Belief
Every project is different and learning from one
project is not applicable to other projects
There is not enough time for learning. We have to
complete the project.
Nothing ever happens after lessons learned are
captured.