Categories of Project Influence (drag left items to match with right items) | ||
Examples | Category | |
Compromise
|
Force |
Direct
|
Collaborate
|
Collaborate |
Problem solve
|
Force
|
Withdraw |
Avoid
|
Accommodate
|
Accommodate |
Smooth
|
Withdraw
|
Compromise |
Reconcile
|
Technique | Description | |
Collaborate
|
Force |
A resolution technique that results in a win-lose situation
|
Force
|
Collaborate |
A resolution technique that often leads to consensus and commitment
|
Avoid
|
Avoid |
A resolution technique that involves withdrawing from the conflict
|
Compromise
|
Compromise |
A resolution technique that partially resolves conflict by finding a solution that brings some satisfaction to all parties
|
Term | Description | |
Organizational process assets
|
Enterprise environmental factors |
Conditions, not under the immediate control of the team, that influence, constrain, or direct the project, program, or portfolio
|
Enterprise environmental factors
|
Organizational process assets |
Plans, processes, policies, procedures, and knowledge bases that are specific to and used by the performing organization
|
Charter Component | Question Addressed | |
Release criteria
|
Release criteria |
What does “done” mean for the project?
|
Project purpose
|
Project purpose |
Who benefits and how?
|
Flow of work
|
Project vision |
Why are we doing this project?
|
Project vision
|
Flow of work |
How are we going to work together?
|
Types of Project Endings (drag left items to match with right items) | ||
Type | Description | |
Extinction
|
Addition |
When a project evolves into ongoing operations
|
Integration
|
Integration |
When resources are distributed to other areas in the organization or assigned to other projects
|
Starvation
|
Extinction |
When the project comes to an end because it was completed and accepted by the stakeholders
|
Addition
|
Starvation |
When resources are cut off from the project prior to completing all requirements
|
Agile Approach | Description | |
Kanban
|
eXtreme programming |
A software development method based on frequent cycles. This approach attempts to distill a best practice into its simplest and purest form and then applies that practice continuously.
|
eXtreme programming
|
Scrum |
A single-team process framework used to manage product development. This approach uses timeboxed sprints of one month or less and revolves around three core roles.
|
Agile unified process
|
Agile unified process |
Used for software projects and features accelerated cycles and less heavyweight processes. This approach focuses on performing more iterative cycles across seven key disciplines and incorporates feedback before formal delivery.
|
Scrum
|
Feature-driven development |
Used to meet the needs of a large software development project. This approach revolves around six core roles and is organized around five activities that are performed iteratively.
|
Feature-driven development
|
Kanban |
Allows for continuous flow of work and value to the customer. This approach is less prescriptive and pulls single items through the process continuously.
|
Power types (drag left items to match with right items) | ||
Type | Description | |
Expert
|
Legitimate |
When power comes about as a result of the influencer’s position
|
Legitimate
|
Punishment |
When the employee is threatened with consequences if expectations are not met
|
Punishment
|
Expert |
When a person being influenced believes the manager, or the person doing the influencing, is knowledgeable about the subject
|
Referent
|
Referent |
When power is inferred to the influencer by their subordinates
|
Crystal Methods (drag left items to match with right items) | ||
Crystal Method Name | Number of Stakeholders Involved | |
Crystal Yellow
|
Crystal Orange |
20 to 40 people
|
Crystal Clear
|
Crystal Clear |
1 to 4 people
|
Crystal Orange
|
Crystal Red |
5 to 100 people
|
Crystal Red
|
Crystal Yellow |
6 to 20 people
|
Levels of Stakeholder Engagement (drag left items to match with right items) | ||
Name | Description | |
Leading
|
Leading |
Stakeholders are actively engaged in the project and helping to ensure its success.
|
Resistant
|
Neutral |
Stakeholders are neutral, neither supporting nor resisting the project, and may be minimally engaged.
|
Neutral
|
Supportive |
Stakeholders have positive expectations of the project and are supportive and engaged.
|
Unaware
|
Resistant |
Stakeholders are not supportive of the project and may actively resist engaging.
|
Supportive
|
Unaware |
Stakeholders are not engaged in the project.
|
Organizational Structure Type | Authority | |
Project-oriented
|
Functional |
Little to none
|
Strong matrix
|
Strong matrix |
Moderate to high
|
Functional
|
Project-oriented |
High to almost total
|
Weak matrix
|
Weak matrix |
Low
|
Leadership Styles (drag left items to match with right items) | ||
Type | Description | |
Servant Leader
|
Interactional |
Uses a combination of transactional, transformational, and charismatic
|
Charismatic
|
Transactional |
Focuses on management by exception; rewards based on goals, feedback, and accomplishments
|
Interactional
|
Charismatic |
Enthusiastic, high-energy, and able to inspire others
|
Laissez-faire
|
Laissez-faire |
Allows the team to make their own decisions and establish their own goals
|
Transactional
|
Servant Leader |
Puts others first and demonstrates commitment to serve
|
Match the following agile measurements with their definitions.
Agile measurements and definitions (drag left items to match with right items) | ||
Agile measurements | Definitions | |
Lead time
|
Definition of done |
A checklist of elements needed to ensure the deliverable is ready for the customer to use
|
Response time
|
Response time |
The time a task waits before work starts
|
Cycle time
|
Capacity measures |
A type of in-the-moment measure
|
Definition of ready
|
Empirical measure |
Typically expressed as deliverables, functionality, or features
|
Capacity measures
|
Definition of ready |
Describes the specifics of the tasks planned for the iteration before the team begins work
|
Empirical measure
|
Cycle time |
The time it takes to complete work on a task from the time work starts
|
Definition of done
|
Lead time |
The time it takes for a task to go from request to completion
|
Agile measurements should focus on customer value
Motivational Theories (drag left items to match with right items) | ||
Theory | Theorist | |
Maslow’s Hierarchy of Needs
|
Achievement Theory |
David McClelland
|
Expectancy Theory
|
Theory of X and Y |
Douglas McGregor
|
Theory of X and Y
|
Hygiene Theory |
Frederick Herzberg
|
Achievement Theory
|
Maslow’s Hierarchy of Needs |
Abraham Maslow
|
Hygiene Theory
|
Expectancy Theory |
Victor Vroom
|
Five-Factor Model Domains and Spectrums (drag left items to match with right items) | ||
Domains | Aspects of Domain | |
Agreeableness
|
Extraversion |
Outgoing vs. reserved
|
Extraversion
|
Openness to experience |
Inventive vs. easy-going
|
Openness to experience
|
Agreeableness |
Compassionate vs. detached
|
Conscientiousness
|
Neuroticism |
Sensitive vs. confident
|
Neuroticism
|
Conscientiousness |
Efficient vs. careless
|
Term | Description | |
Velocity
|
Cycle time |
The time required to process a work item
|
Cycle time
|
Schedule performance index |
A measurement of the schedule efficiency expressed as a ratio of earned to planned value
|
Burnup chart
|
Lead time |
The total time it takes to deliver an item, measured from the time the work is committed to the time it is completed
|
Schedule performance index
|
Velocity |
The sum of story point sizes for the features completed in an iteration
|
Lead time
|
Burnup chart |
A visual depiction of the work completed
|
Project Life Cycles (drag left items to match with right items) | ||
Type | Description | |
Agile
|
Iterative |
Correctness of solution
|
Incremental
|
Agile |
Customer value via frequent deliveries and feedback
|
Iterative
|
Incremental |
Speed
|
Predictive
|
Predictive |
Manage cost
|
Term | Definition | |
Burndown chart
|
Burndown chart |
A visual representation of the work remaining versus the time left in a timebox
|
Burnup charts
|
Burnup charts |
A visual representation of the work completed toward the release of a product
|
Velocity
|
Velocity |
The sum of story point sizes for features actually completed during the iteration
|
Story points
|
Story points |
A unit-less measure used in relative user story estimation techniques
|
Knowledge Area Name | Description | |
Project Procurement Management
|
Project Resource Management |
Contains the activities to identify, acquire, and manage the resources needed for the successful completion of the project
|
Project Integration Management
|
Project Integration Management |
Contains the activities to identify, define, combine, unify, and coordinate the various processes and project management activities within the various process groups
|
Project Schedule Management
|
Project Procurement Management |
Contains the activities necessary to purchase or acquire products, services, or results needed from outside the project team
|
Project Resource Management
|
Project Stakeholder Management |
Contains the activities required to identify the people, groups, or organizations that could impact or be impacted by the project, analyze them, and develop strategies for engaging them
|
Project Stakeholder Management
|
Project Schedule Management |
Contains the activities required to manage the timely completion of the project
|
Types of Conflict Resolution Techniques (drag left items to match with right items) | ||
Type | Description | |
Direct
|
Problem Solve |
To incorporate multiple viewpoints and lead to consensus and commitment. This is considered a win-win situation.
|
Avoid
|
Direct |
To push one’s viewpoint at the expense of others. This is considered a win-lose situation.
|
Reconcile
|
Avoid |
To retreat from the conflict situation. This is considered a lose-lose situation.
|
Problem Solve
|
Reconcile |
To search for a temporary solution that satisfies all parties. This is considered a lose-lose situation.
|
Accommodate
|
Accommodate |
To emphasize agreement and concede one’s position to maintain harmony or relationships. This is considered a win-lose situation.
|
Agile Approaches (drag left items to match with right items) | ||
Approach | Description | |
eXtreme Programming (XP)
|
Crystal methods |
A family of methodologies designed to scale to the project needs
|
Scrum
|
Feature-driven development |
Focuses on delivering usable, working software continually in a timely manner
|
Crystal methods
|
Kanban |
A pull-based concept where work progresses to the next step only when resources are available
|
Kanban
|
Scrum |
A single-team process framework typically used to manage product development
|
Feature-driven development
|
eXtreme Programming (XP) |
Focuses on delivering software that’s ready when the customer needs it
|
Life Cycle Name | Description | |
Agile life cycle
|
Incremental life cycle |
An approach that provides deliverables to the customers to use immediately
|
Predictive life cycle
|
Predictive life cycle |
A traditional approach where the majority of planning occurs up front, followed by execution of the work
|
Incremental life cycle
|
Iterative life cycle |
An approach that allows feedback on unfinished work to improve and modify the work
|
Iterative life cycle
|
Agile life cycle |
An approach that is both iterative and incremental to refine work items and deliver frequently
|
Term | Description | |
Voting
|
Autocratic |
One individual makes the decision
|
Autocratic
|
Multicriteria decision analysis |
Uses a systematic approach to making decisions
|
Multicriteria decision analysis
|
Voting |
Uses unanimity, majority, or plurality to make decisions
|
Leadership Style | Attributes | |
Transactional
|
Laissez-faire |
A hands-off approach
|
Charismatic
|
Servant leader |
Puts other people first
|
Servant leader
|
Transactional |
Management by exception
|
Transformational
|
Transformational |
Seeks to inspire and encourage innovation
|
Laissez-faire
|
Charismatic |
High-energy and enthusiastic
|
PMO Type | Description | |
Controlling
|
Supportive |
Serves in a consultative role. Provides templates, best practices, training, and lessons learned from other projects
|
Directive
|
Controlling |
Serves in a supportive and compliance role. Provides project management and governance frameworks that are followed by PMs
|
Supportive
|
Directive |
Serves in a management role. Assigns project managers to projects and directly manages projects
|
Term | Description | |
Iterative
|
Iterative |
Planning occurs early in the project’s life. The plan is modified through each iteration, and work completed informs future work.
|
Predictive
|
Predictive |
Most of the planning occurs upfront. The team strives to identify as much detail about requirements as possible early on.
|
Incremental
|
Incremental |
Teams plan one or more subsets of the overall project. Completion of these deliveries informs the future wor
|
Quality Theorist | Theory | |
Joseph Juran
|
Joseph Juran |
Pareto Principle
|
W. Edwards Deming
|
Walter Shewhart |
Total Quality Management (TQM)
|
Philip Crosby
|
Philip Crosby |
Zero Defects
|
Walter Shewhart
|
W. Edwards Deming |
Plan-Do-Check-Act
|
Life Cycle | Continuum | |
Agile
|
Predictive |
Low frequency of delivery and low degree of change
|
Predictive
|
Incremental |
High frequency of delivery and low degree of change
|
Iterative
|
Iterative |
Low frequency of delivery and high degree of change
|
Incremental
|
Agile |
High frequency of delivery and high degree of change
|
PMO Type | Description | |
Supportive
|
Supportive |
Provides consultation to project teams by providing resources, training, and access to information
|
Directive
|
Directive |
Takes control of projects by directly managing them via project managers that report to the PMO
|
Controlling
|
Controlling |
Provides support and requires compliance against published project management and governance frameworks
|