Create High-Performing Team Flashcards
Stakeholder Identification
- Usually done during project charter development.
- Document SH interest, involvement, interdependencies, influence, and potential impact.
- Use expert judgment, questionnaires, brainstorming, and meetings to identify
Stakeholder Register
A set of individuals who support the project manager in performing the work of the project to achieve its objectives
RACI chart
A common type of responsibility assignment matrix (RAM). Responsible, Accountable, Consulted, and Informed statuses define the involvement of stakeholders in project activities
Team Skill Appraisal
enables the team to holistically identify its strengths and weaknesses, assess opportunities for improvement, build trust, and establish effective communication.
Might identify forms of communication, aspirations, decision-making process, and interactions.
Pre-assessment tools when assessing candidates before assigning team roles
Allow you to assess candidates before assigning and confirming team roles
- Attitudinal surveys,
- specific assessments
- structured interviews
- abilities test
Resource Management Plan
The project document that identifies resources, and how to acquire, allocate, monitor, and control them.
Includes:
- Project Organization Chart
- Project team resource management (how to define, staff, manage, and release)
- Training strategies and requirements
- Team development methods
- Resource controls - to manage physical resources
- Recognition plan (e.g. bonus)
Work Breakdown Structure (WBS)
A project management tool that takes a step-by-step approach to complete large projects with several moving pieces. By breaking down the project into smaller components, a WBS can integrate scope, cost and deliverables into a single tool.
Agile
Project Management methodology characterized by self-organising teams assesses who assess their own work requirements and determine who will do the work.
KanBan
Information Radiator in Agile projects to provide seamless visibility into project status across the stakeholder community.
Team Charter
A document that enables the team to establish its values, agreements, and practices as it performs its work together
it includes:
- guidelines for communication
- decision-making guidelines
- conflict resolution measures
- meeting time, frequency, and channel
- other agreements
Ground Rules
Clear expectations regarding the code of conduct for team members
- sets performance and communication expectations
- decreases risk of confusion
- improves team performance
Project Agreement Objectives (traditional)
- Reporting and verification criteria
- Identify each deliverable and objective acceptance criteria for each.
Project Agreement Objectives (Agile)
- Deliverables vary as the product backlog is added to, reprioritized, and so forth
- Each story (function) needs to have clearly defined acceptance criteria approved by the customer
- the project may also specify a definition of DONE for the project, releases, iterations, and user stories.
Agreements
define initial intentions for a project. These can be:
- Contracts
- MOUs
- Service Legal Agreements (SLA)
- Letters of agreement or intent
verbal agreements
- email
Product Backlog
- Prioritization technique used in agile
- List of to do’s for later
Kano Model
- Prioritization technique used in agile
- approach base on what satisfied the customer
MoSCoW (MSCW)
- Prioritization technique used in agile
- Must have, should have, could have, won’t have
Paired comparison analysis
- Prioritization technique used in agile
- one-to-one comparison
100 points method
- Prioritization technique used in agile
- vote system to prioritize
Expert Judgement
Judgement based upon expertise in an application area, knowledge area, discipline, industry, etc. as appropriate for an activity being performed. Such expertise may be provided by any group or person with specialized education, knowledge, skill, experience or training.
Resource calendar
Identify working days, shifts, and when specific resources are made available to the project
Lessons learned Register
A project document used to record knowledge gained during a project so that it can be used in the current project and entered in the lessons learned repository.
Retrospective (Agile)
Agile version of lessons learnt.
- Identify specific improvements at the end of each iteration to identify issues, potential solutions, and improve processes.
Special Intervals (Agile)
In Agile, projects may require scheduled ‘down’ time within different iterations or releases
Example:
- black-outs
- Go live
Make sure to agree when and how these will take place according to the project’s needs.
T-Shaped Skills
Agile teams invest in becoming more cross-functional
- Find ways to diversify skills set.
Communications Plan
Includes:
- Team meeting times
- Tools to track work status
- Frequency of work status updates
- shared team hours
- preferred communication approaches
Variance Analysis
Evaluate the accuracy of team estimates (e.g. the planned time it took to deliver a sprint vs the actual time).
Project Vision includes (5)
- define a clear vision of the desired objectives at the start of the project.
- Understand and appreciate how the project vision aligns with the organisations’s strategic goals.
- Vision statement includes:
a) product or solution description
b) intended user’s or consumers of the solution
c) Key Desired objectives
d) Differentiators from competitive approaches
e) Key features and benefits
Project Charter
A document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities
Project Charter Contents (11)
1) measurable project objectives and related success criteria
2) High-level requirements
3) High-level project description, boundaries, and key deliverables
4) Overall project risk
5) Summary of milestones schedules
6) Pre-approved financial resources
7) Key stakeholders list
8) Project approval requirements
9) Project exit criteria
10) Assigned project manager and responsibilities/Authority level
11) Name and authority of project sponsor.
Project Overview Statement
- Communicates enterprise-wide the intent and vision of the project
- Written with brevity and clarity
- Captures the project’s objective, problem or opportunity and criteria for success.
- Authorization via the projects charter or approved project overview statement enables kickoff activities of project planning
Iteration/Sprint planning
- Collaborative agile ceremony for the team and the customer representative to do the following:
- Review the highest prioritized user stories, or key outcomes
- Ask questions
- Agree on forecasts for story completion in the current iteration
Task Boards
Visualize work and enable the team and stakeholders to track progress as work is performed
- promote visibility and maximize efficiency and accountability
Ex. Kanban boards, to-do lists, procedure checklists, and Scrum board.
Consensus methods (4)
a collaborative process to reach a decision that everyone can support
Methods:
- Fist of Five (closed fist for disagree, open for agree)
- Roman Voting (Thumbs up or down)
- Polling (independent point of view)
- Dot Voting (distribute dots equally, then each person allocates dots according to highest preference)
Product Box
Ways to describe a solution that is complicated in a simple form. Like the way a marketer would explain product features and benefits on a box
