CAPM Definitions Flashcards
an overview document to formally authorizes a project or a phase and includes stakeholders, the project objectives, deliverables, and milestones.
document issued by the project initiator or sponsor that formally authorizes the existence of a project and provides the PM with the authority to apply organizational resources to project activities
Project Charter
document that primarily focuses on the business rationale, including ROI, benefits, and risks.
Business Case
Document defining, preparing, and coordinating all plan components and consolidating them. outlines the basis of all project work and how it will be perfromed.
Project Management Plan
document that includes detailed deliverables, work requirements, risks, acceptance criteria, and constraints/assumptions/exclusions (Initiating Phase)
Project Scope Statement
a process where you compare the work that has gotten done to the project management plan to see if they line up
Control Scope
a process where stakeholders formally accept the project deliverables
Validate Scope
unauthorized work added to scope
Scope Creep
doing extra work not in the scope
Gold Plating
table created that will link the requirement back to its source and used to help manage changes to the project scope. it tracks the original stakeholder, why the requirement was added, description, and the status of it
Requirements Traceability Matrix
breakdown of work into smaller levels of work that subdivides project deliverables and project work into smaller more manageable components (from info on scope statement)
WBS - work breakdown structure
breaking down each of the project deliverables into smaller components - work packages should be able to estimate time, cost, effort
decomposition
detailed content of WBS that includes time estimate, cost, team member, account info, ect.
WBS dictionary
progressive elaboration - near term work packages are able to be defined in a much greater detail
Rolling Wave Planning
graphical representation of all work needed to perform the project. represents the flow of the project and the work packages relationships to each other -
a visual tool that helps schedule activities in a project plan by creating a network diagram that shows dependencies and critical paths
Precedence Diagramming Method
tangible limitations of work packages that are tied together. One work package must be completed prior to subsequent work package beginning.
They are a fundamental aspect of the work and cannot be changed. These dependencies are based on the physical or logical relationship between tasks and the order in which they must be completed. For example, the installation of a foundation must be completed before building construction can begin. Usually easy to identify because they are based on the nature of the work and the inherent dependencies between tasks.
Mandatory Dependences (Hard Logic or Hard Dependencies)
work packages that are tied together but do not have limitations - work in unison or tandem
Refers to the relationships in project management that are based on best practices, preferences, or expert judgment rather than hard requirements.
They are often flexible and can be adjusted based on the needs and priorities of the project. However, project managers must be careful while considering the potential consequences of changing them.
Discretionary Dependencies (Soft Logic or Preferential Logic)
work package relationship between project and non-project activities that are outside the control of the project team
External Dependencies
work activities within the control of the team
Internal Dependencies
amount of time a successor activity can be advanced with respect to a predecessor activity
Lead
directs the delay in the successor work package or activity
Lag
technique that uses a statistical relationship between historical data, project parameters, other variables to calculate an estimate for activity parameters
Parametric Estimating
relies on historical information to predict estimates (time, budget, difficulty) for current projects. Used when there’s limited info/time. Costs less in time/money but least accuracy in estimating.
Analogous Estimation (Top-Down)
very detailed estimation and takes a while to complete - breaks down the work to the lowest levels then aggregating back up to find and overall duration
Bottom-Up Estimating
(opt + pess + most likely) / 3
program evaluation and review technique - a scheduling tool that uses a weighted average formula to predict the length of activities and the project
Three Point Estimate or Triangle Distribution
(opt + pess + (most likely x 4) / 6
program evaluation and review technique - a scheduling tool that uses a weighted average formula to predict the length of activities and the project
PERT estimation formula or BETA distribution
a method to flatten the schedule when resources are over-allocated or allocated unevenly
Resource Optimization Technique
ensures workers are not overextended on activities - but it might extend the schedule
Resource Leveling
amount of time a task can be delayed without delaying the start of a successor task
Free Float
the amount of time a scheduled activity can be delayed without delaying the overall project completion date.
(name the formula)
Total Float
Formula - TF = Late Finish - Early Finish
cost estimate between -5% and 10%
Definitive
cost estimate between -10% and 25%
Budgeted
cost estimate between -25% and 75%
Rough Order of Magnitude
the process of estimating the total cost of a project by combining the individual cost estimates of its activities, work packages, or deliverables - delivers a high level overview with less accuracy
Cost Aggregation
project’s current run rate vs. what was planned over the life cycle of the project - done when there are limited funds to spend on the project and work may need to be rescheduled
Funding Limit Reconciliations
cost of all the activities - work packages, contingency reserves, control accounts
Cost Baseline
cost baseline + management reserves
Project Budget (Actual Cost)
matrix grid that shows the project resources assigned to each work package - shows which stakeholders are responsible, accountable, consulted, or informed, and are associated with project activities, decisions, and deliverables
Responsibility Assignment Matrix (RACI Chart)
bar chart that visually shows a project’s schedule and progress over time -
activities are listed on the vertical axis, dates shown on the horizontal axis, and activity durations are shown as horizontal bars placed according to start and finish dates
FUCKING CRITICAL PATH
Gantt Chart
SWOT Analysis identifies risks
Strengths, Weaknesses, Opportunities, Threats
channels = N(N-1) / 2
N = Number of people on the project
Communication Channel Formula between Stakeholders
prioritizing individual project risks by assessing their probability of occurrence and impact (determines which risks are highest priority)
Qualitative Risk Analysis
numerically alayzing the effect of individual project risks on the overall project objectives (assigns a value to the risk)
Quantitative Risk Analysis
a risk threat where the project team acts to eliminate the threat or protect the project from its impact
Avoid
a risk threat where the project team/sponsor agrees that the threat is outside the scope of the project or that the proposed response would exceed the PM’s authority
Escalate
a risk threat where the ownership of a threat is shifted to a third party to manage the risk and bear the impact if it occurs
Transfer
a risk threat where action is taken to reduce the probability of occurrence and/or impact of a threat.
Mitigate
a risk threat where the threat is acknowledged but no proactive action is planned. Can include developing a contingency plan that could be triggered if the event occurred or nothing could be done
Acceptance
an opportunity risk action where the project team acts to ensure that an opportunity occurs
Exploit
an opportunity risk, as with a threat, response is used when the project team or sponsor agrees that the opportunity is outside the scope of the project or that the proposed response would exceed the PM’s authority
Escalate
an opportunity risk response that involves allocating ownership of an opportunity to a third party who is best able to capture the benefit of the opportunity
Share
an opportunity risk action where the project team acts to increase the probability of occurrence or impact of an opportunity.
Enhance
an opportunity risk action where, as with a threat, an opportunity is acknowledged but no proactive action is taken
Accept
buyer pays one flat price that includes all labor and materials. used when the scope is well-defined and understood (all risk is with the seller)
Fixed-Price Contract (Lump Sum)
a type of contract where the fixed price cannot change
Firm Fixed Price (FFP)
a type of contract where the fixed price includes an additional fee for meeting target set forth in contract
Fixed Price Incentive Fee (FPIF)
a type of contract where the fixed cost is adjusted over the life of the contract because of the economy
Fixed Price Economic Price Adjustment (FP-EPA)
involves payments to the seller for actual costs incurred for completing the work plus a fee representing seller profit and often used when the project scope is not well defined or subject to frequent change
Cost-Reimbursable Contracts
contract when a buyer pays the work expense and then a fixed fee to the seller for profit
Cost Plus Fixed Fee (CPFF)
contract when a buyer pays the work expense and an additional fee if a target is met
Cost Plus Incentive Fee (CPIF)
contract when a buyer pays the work expense and pays an award fee based on the satisfaction of the work (subjective and written into the contract)
Cost Plus Award Fee (CPAF)
contract that establishes a fixed rate when a buyer pays for both the labor and material - the buyer takes all of the risk of cost overrun for both the labor and the materials (used only when the scope is high level and not detailed) can be used for staff augmentation, subject matter expertise, or other outside support
Time and Materials (T&M)
a tool you can use as part of stakeholder analysis, management, and engagement. It’s a way of categorizing stakeholders so you can evaluate the best way to involve them in the project
- stakeholders are described based on the following attributes:
Power: Ability to impose their will
Urgency: Need for immediate attention
Legitimacy: Appropriateness of their involvement
Salience Model
5 Stages of Team Development - Forming, Storming, Norming, Reforming, Adjourning
Tuckman’s Ladder
show the relationships between the variables within a process and how those relationships may contribute to the inadequate quality (ex: Ishikawa and fishbone diagrams)
Cause & Effect Charts
tool for showing the relative importance of problems.
It contains both bars and lines, where individual values are represented in descending order by bars, and the cumulative total of the sample is represented by the curved line. An 80% cut off line is also included to indicate where the 80/20 rule applies i.e. the vital few factors that warrant the most attention sit under the 80% cut off line.
Pareto Chart / 80-20 Rule
the belief that people need to be watched and micromanaged
McGregor’s Theory X
the belief that people are self-lead, motivated, and can accomplish tasks proactively
McGregor’s Theory Y
the factors that influence satisfaction at work
Herzberg Theory of Motivation
theory of workplace loyalty that is definitely not a thing in the USA
Theory Z
document used to estimate assumptions, constraints, ranges of estimates, and the confidence levels of the estimates
Basis of Estimates
Upwards influence is for stakeholders above you, such as senior management.
Downward are below you, such as team members.
Sideways are your peers, such as other project managers.
Outwards are external, such as vendors.
Influences
meeting where the backlog is progressively elaborated and (re)prioritized to identify the work that can be accomplished in an upcoming iteration
Backlog refinement or grooming
a meeting used to clarify the details of the backlog items, acceptance criteria, and work effort required to meet an upcoming iteration commitment
iteration planning or sprint planning meeting
Incorporating multiple viewpoints and insights from differing perspectives; requires a cooperative attitude and open dialogue. This approach can result in a win-win situation.
Collaborative/Problem Solve
Retreating from an actual or potential conflict situation; postponing the issue to be better prepared or to be resolved by others.
Withdrawal/Avoid
Highlighting areas of agreement rather than areas of difference; conceding one’s position to the needs of others to maintain harmony.
Smooth/Accomodate
Searching for solutions that bring some degree of satisfaction to all parties to temporarily or partially resolve the conflict. This is generally a lose-lose situation.
Compromise/Reconcile
Pushing one’s viewpoint at the expense of others; offering only win-lose solutions, usually enforced through a power position. This is often a win-lose situation.
Force/Direct
the plans, processes, policies, procedures, and knowledge bases specific to and used by the performing organization. They include any artifact, practice, or knowledge from any or all of the organizations involved in the project that can be used to perform or govern the project. It can also include the organization’s knowledge bases, such as lessons learned and historical information. It may include tools, checklists, methodologies, approaches, templates, frameworks, patterns, or PMO resources.
Organizational Process Assets
Six Areas of Constraints
Scope, Schedule/Time, Cost, Quality, Risk, Resources
known as a PERT chart or precedence diagram, displays the sequence of project activities and their interdependencies. This helps in understanding the flow and sequence of tasks in a project.
Network Diagram
Must have, should have, could have, won’t have
This method helps stakeholders prioritize tasks or requirements based on their importance and urgency.
MoSCoW Method
a visual guide representing the skeletal framework of an application, making it ideal to demonstrate user navigation
Wireframe
money spent during the project to avoid failures, includes:
- Prevention costs (training, documentation, equipment, time to do it right), and
- Appraisal costs (testing & inspections)
Cost of Conformance (Good Quality)
money spent during or after the project because of failures, includes:
- Internal Failure costs (rework, scrap), and
- External Failure cost (liabilities, warranty work, lost business)
Cost of Non-Conformance (Bad Quality)
KPIs - predict changes or trends
Leading Indicators
KPIs - reflect past performance
SV and CV are examples of these
Lagging Indicators
5-stage change model that describes each stage’s effects on feelings, thinking, performance, and physiology.
The core concept states that there is always the possibility of improvement from any change process. The model focuses on tracking rather than influencing performance.
The model outlines five distinct stages of change: Late Status Quo, Resistance, Chaos, Integration, and New Status Quo
Satir’s Change Model
The model highlights the difference between change and transition. Change happens to people. Transition, on the other hand, is internal: it’s what happens in people’s minds when facing and experiencing change.
You can use the model to understand how people feel as you guide them through change. It has three distinct stages:
- Ending, Losing, and Letting Go.
- The Neutral Zone.
- The New Beginning.
Bridges’ Transition Model
A top-down approach where the need for and approach to change originates at the top levels of the organization, and then is promoted down through the organization’s layers of management to the change recipients.
Kotter’s 8 Step Process for Leading Change
Dynamic systems development method (DSDM) is an agile project delivery framework, initially used as a software development method. First released in 1994, DSDM originally sought to provide some discipline to the rapid application development (RAD) method. In later versions, the DSDM Agile Project Framework was revised and became a generic approach to project management and solution delivery rather than being focused specifically on software development and code creation and could be used for non-IT projects. The DSDM Agile Project Framework covers a wide range of activities across the whole project lifecycle and includes strong foundations and governance, which set it apart from some other Agile methods. The DSDM Agile Project Framework is an iterative and incremental approach that embraces principles of Agile development, including continuous user/customer involvement.
DSDM fixes cost, quality and time at the outset and uses the MoSCoW prioritisation of scope into musts, shoulds, coulds and won’t haves to adjust the project deliverable to meet the stated time constraint. DSDM is one of a number of Agile methods for developing software and non-IT solutions, and it forms a part of the Agile Alliance.
Dynamic Systems Development Method
Transparency, Inspection, Adaptation
3 Pillars of Scrum
A software-development-centric agile method. While Scrum at the project management level focuses on prioritizing work and getting
feedback, it focuses on software development good practices.
The core values of this methodology are simplicity, communication, feedback, courage, and respect, and these values manifest themselves in the practices undertaken throughout the life cycle.
XP - Extreme Programming
In XP, production code is written by two developers working as a pair to write and provide real-time reviews of the software as it emerges. This saves time because the pairs catch issues early. Working in pairs also helps spread knowledge about the system through the team.
Pair Programming
A project team following this method will first develop an overall model for the product, build a feature list, and plan the work. The team then moves through design and build iterations to develop the features.
FDD - Feature-Driven Development
A visual depiction of a business system or process and how people and other systems (actors) interact with it.
Context Diagram
