Project Domain 2
By: Yassin Hassan
Agenda
• Performance Tracking Tools
• Agile in project management
• Retrospectives and Lessons Learned
• Empower Team Members & Stakeholders
Collaborate with
Manage conflict Lead a team
stakeholders
Empower team
Support team Build shared
members and
performance understanding
stakeholders
Engage and
support virtual
Negotiate
project
Ensure team
members/stakeh
olders are
People’s domain
teams agreements adequately
trained
Define team Mentor relevant
Build a team
ground rules stakeholders
Address and Promote team
remove performance
impediments, through the
obstacles, and application of
blockers for the emotional
team intelligence
Kanban boards
Earned Value
Performance
Tracking Tools
Bar charts (Gantt)
Velocity
Agile in project
management
Kanban
methodology
Gantt chart (Project schedule)
Retrospectives and Lessons Learned
Lessons learned Uses to help Retrospectives
have to be a project encourage team
continues performance and to review
practice its environment performance
Retrospectives is The result is a
more than plan on how to
capturing lessons utilize
learned improvements
What worked well
Conducting What could be improved
Retrospectives
idea How will it be improved
Notice common items needs improvements
Involve team on the plan
Update the Backlog (a prioritized list of
deliverables)
Organize
Organize around team strengths
around
Empower Team
Members & Support Support team task accountability
Stakeholders
Evaluate demonstration of task
Evaluate accountability
Determine Determine and bestow level(s) of decision-
and bestow making authority
SOWT analysis
Strengths Weaknesses
Opportunities Threats
Decision-making tools
1. Project team involves in project’s activates, risks, estimates and challenges
2. Forming the team on how to make decision and how handle conflict
3. Decision making and conflict handing must include in the Team Charter
4. Team to train and learn how to reach to consensus
Estimates performs by people doing the work
Estimates skills Team must have knowledge of Risks, Level of effort
and potential drawbacks
Traditional manager use the hours off effort to
identify the length of task
Teams assign story points relative to work
complexity, the amount of work, and risk or
uncertainty
Agile project team uses Story Point estimation
Team task accountability
WHAT WORK MUST HOW THE WORK WHO SHOULD DO
BE DONE CAN BE DONE THE WORK
Project manager identify how and who
performed the task
Evaluate
Work Breakdown Structure (WBS) uses
demonstration of to assign tasks
task accountability
WBS dictionary (work package) uses to
identify, track and manage deliverable
In Agile identity & track task is the
team accountability
WBS
Next lesson
01 02 03
Train team Build a team Address &
members and remove
stakeholders impediments,
obstacles, and
Blockers
