GOVERNANCE STRUCTURE

Fundamentals of Choosing the Right Leadership

Team
Leadership skillset
Experience
Education
Expertise
Knowledge
Interpersonal Skillset
Communication Skillset
Organizational Skillset
 TEAM ROLES &
RESPONSIBILITIES
Joseph Javellana Project Coordinator
In charge of evaluating the critical path and the
connections between the different WBS.
Responsible to evaluate all resources from the
tasks according to the deliverables.
Responsible to preview all tasks that need to get
completed.
Chidiebere Njoku Project Leader
In charge of selecting the right person to
perform the assigned task.
Responsible to solve conflicts and issues arising
out of discussions and brainstorming activities.
 TEAM ROLES &
RESPONSIBILITIES (CONT.)
Emirjona Molla Quality Assurance Coordinator
Responsible for the project quality
Communication
Consolidation
Responsible for connecting all reports according to our
project management documentation
Alvaro Salamanca Tasks Maintenance
Coordinator
In charge of maintaining the tasks list
In charge of monitoring the time due for each tasks over
the duration of the project.
Responsible of ensuring that all the deliverables are
completed and on time.
 TEAM ROLES &
RESPONSIBILITIES (CONT.)
Jason Proctor Editor
Responsible for editing
Responsible for revising all the deliverables according
to the project managers request.
Responsible for ensuring that proper APA standards are
observed.
Responsible for evaluating graphics, presentation,
documents and reports.
Dominique Escoe Secretary
Responsible for taking notes in our meetings.
Definition of responsibilities
Evaluation of constraints and externalities
The due date
The scope
The budget for all aspects defined in the meetings.
 METHODS OF COMMUNICATION
AND DECISION MAKING
How the decisions were made:
E-mails
Team Consensus
Phone Calls Brainstorming
Industry Best Practices
Google Drive
Research
Meetings Government and Industry Policies
Professional organizations (PMI, ISO)
On Ground
Walsh College Campus
Online
Skype
 RISK PLAN
Identify all the Risks.

Asses the level of impact they

may have on the project.
What we should do when they
occur.
Probability of occurrence.

Method of approach.

How soon we should take action if

they occur.
 IDENTIFICATION OF RISKS
Schedule Flaws

Under Communication

Unrealistic Expectations

Failures From the Suppliers

Staff Turnover

Technology and uncertainty

Resource shortfall

Ambiguous Decisions

Theft, vandalism and sabotage

RISKS THAT BECAME ISSUES
Unrealistic Expectations
Louis Styles threatened to stop the
project due to unrealistic quality
defects.
Schedule Flaws
Davids absence affected our
schedule which resulted in delays.
The main stakeholder from
marketing could not be in the Kick-
Off meeting which resulted in a
two-day delay on the project.
 MEETING EXPECTATIONS
Gantt-Chart

Critical Path

EVM

Overtime

Project Performance Index

Estimated Cost

Estimated Project Finish

Quality

Work Productivity

Project Status Report

Task Status Report

 CORRECTING COURSE
Training

Overtime

Meetings

Visiting

Consultation

Counseling

WBS Diagram

Project Charter

Rewards
 SUCCESSFUL TEAMWORK
Open-mindedness and respectfulness
to new ideas
Create a collaborative environment

Using effective communication tools

Equally sharing tasks and

responsibilities
Structured division of labor

Strategic Thinking and Planning

Behaving professionally

Capitalized on the individual fissure

project experience
UNSUCCESSFUL TEAMWORK
Scheduling issues due to different work
schedules of members.
Sick team members affected meetings
schedule.
Snow day led scheduling problems.

Balancing heavy workloads of team

members.

However, we completed the project on

time, scope, budget and quality. This is
due to the individual fissure experience.
RESULTS OF THE SIMULATED
PROJECT
Variance Explained Costs Budget to Actual

Approved Budget = $50,000

Planned Budget = $50,000

Actual Budget = $47,574

Budget Variance = $2,426

We delivered the project on budget.

Lessons learned : In the past, we

failed to allocate enough resources
to various tasks.
 RESULTS OF THE SIMULATED
PROJECT
Variance
Estimated Explained
schedule = 11 weeks (55 Schedule Estimate to Actual
days)
Actual Schedule = 9 weeks (48 days)

Schedule Variance = (7 days early)

We delivered the project earlier than

the planned schedule.
Lessons learned : Generously
allocating enough resources to task
allowed us to complete the task
faster.
RESULTS OF THE SIMULATED
PROJECT
Variance Explained Recognition plan to actual
The plan was to focus on moderate recognition
budget $830
The approved budget for recognition was $500, and
the actual was $275
Quality was impacted due to overtime and lack of
training but it was solved on time, budget, and scope
Variance
Planned $830
Actual 275
Lesson learned
Recognition is connected to efficiency and results. If I
had given more rewards, our team would have
become more motivated and more efficient. As a
result, we would have decreased defects and delays,
and improved motivation, efficiency and quality
RESULTS OF THE SIMULATED
PROJECT
Variance Explained Budget To Actual Defects

Theoretical Defects = 12

Project Defects = 11.5

Hardware Defects = 5

Software Defects = 6.5

We managed to exceed the quality control since the

results should be under 12 defects.
The threshold according to the Project Charter is 12.

Lessons Learned : To control quality defects we sent

a team member to do a 2 day training on Quality.
We learnt that we should have sent more members
to improve our quality especially in Weeks 6, 7 and
8.
 ADVICE TO OTHERS
Advice
Be overly generous when
budgeting for resources.
Do not be afraid to assign more
than one person to a task.
To improve quality, get at least 3
members to attend the training
workshop.
To keep workers happy and
motivated, make sure you reward
generously.