PMI Glossary Flashcards
(179 cards)
1
Q
Acceptance Test Driven Development
A
Method used to communicate with business, devs and testers before coding begins
2
Q
Active Listening
A
To focus on what is said and provide feedback to communicate understanding
3
Q
Adaptive Leadership
A
leadership that helps teams to thrive and over come challenges throughout a project
4
Q
Affinity estiamtion
A
Method to quickly place user stories into comparable sized group
5
Q
Agile
A
To develop a goal through periodic experimentation in order to fulfill the need of complex decision
6
Q
Agile Adaption
A
To adapt project continously through retrospective in order to max value creation during planning process
7
Q
Agile Experimentation
A
To use empirical process, observation & spike intro while executing a project to influence planning
8
Q
Agile Manifesto
A
1) Individual & interaction over process & tools; 2) Working software over comprehensive doc 3) Customer collaboration over contract negotiation, and responding to changes over following a plan
9
Q
Agile Manifesto: Customer Satisfaction
A
To satisfy customers thru early and continuous delivery of products, to test and receive feedback, to inform customers on progress, and to fulfill customer’s value by completing priority req
10
Q
Agile Manifesto: Frequent Delivery
A
To deliver software frequently to the customer, allowing for a quicker product release, faster provision of value to the customer and shorter delivery time frame
11
Q
Agile Manifesto: Collocated Team
A
To have individuals work together daily on a project to implement OSMOTIC communication, focus and receive instant feedback to achieve common goal
12
Q
Agile Manifesto: Motivated Individuals
A
To give individuals the empowerment, environment, support and trust needed to complete a task successfully
13
Q
Agile Manifesto: Face-to-Face Conversation
A
Most efficient and effective way to communicate in order to receive direct feedback & influence osmotic communication
14
Q
Agile Manifesto: Working Software
A
Working software enables the measurement of progress, enhance customer satisfactions and maintain and improve the quality of the software to help support project goals
15
Q
Agile Manifesto: Constant Pace
A
To help team establish a healthy work-life balance, remain productive and respond to change swiftly for progress during a project
16
Q
Agile Manifesto: Continuous Attention
A
To enhance agility and time spent on work req in order to retain a well-balanced work environment
17
Q
Agile Manifesto: Simplicity
A
Let team focus on what is necessary to achieve the req needed to create and deliver value to the project and customer
18
Q
Agile Manifesto: Self-organization
A
Team that knows how to complete tasks effectively, has dedication to the project and is expert on the process and project
19
Q
Agile Manifesto: Regular Reflection
A
Let team to learn how to become more effective, what changes need immediate implementation and behavior that needs adjustment
20
Q
Agile Mentoring
A
To pass on and teach based on experience, knowledge, and skill to other in team or that work for the org
21
Q
Agile Methodologies
A
A way to complete a goal effectively and efficiently / Example - XP , Scrum , Lean
22
Q
Agile Modelling
A
A workflow depiction of a process/system a team can review before it is turned into code; Stakeholder should understand the model / Example - User case diagram, Data models, Screen design
23
Q
Agile Planning
A
Most important aspect of Agile project - Planning happen at multiple levels such as strategic, release, iteration and daily. Planning must happen up-front and can change throughout project
24
Q
Agile Space
A
A space that let team to establish Collaboration, Communication, Transparency and Visibility
25
Agile Theme
Used to help team focus on the functions of iteration
26
Approved Iterations
After the deadline of iterations is reached, the team and stakeholders conduct a meeting for approval. Stakeholders approve the iteration if the backlog used supports the product increment
27
Architectural Spikes
Spikes that relate to any area of system, tech, or application domain that is unknown
28
Artifact
A process or work output / Example - Document, Code
29
Adaptive Software Development (ASD)
Exhibits continuous adaption to the project and its processes with characteristics that include - Mission focused, Feature based, Iterative, Time-boxed, Risk driven & Change Tolerant
30
Automated Testing Tools
Tools let for efficient and strong testing / Example - Peer Reviews, Periodical Code-review, Refactoring, Unit Test, Automatic & Manual Testing
31
Being Agile
To work in responsive way to deliver products or services a customer needs and when they want the products or services
32
Brainstorming
Effective and efficient way of gathering ideas within short period of time form a group
33
Burn-Down Chart
To display progress during and at the end of iteration; "Burning down" means that backlog will lessen throughout the iteration
34
Burn Rate
Rate of resources consumed by the team; also cost per iteration
35
Burn-Up Chart
To display complete functionality. Progress will trend upward, as stories are completed. Only show complete functions, it isn't accurate at predicting or showing WIP
36
CARVER
Acronym - to measure the goals and mission of the project -> Criticality, Accessibility, Return, Vulnerability, Effect & Recognizeability
37
Ceremony
Agile meetings - Daily stand-up, Iteration planning, Iteration Review and Iteration Retro
38
Charter
Doc created during initiation that formally starts the project; Includes Justification, summary level budget, major milestone, critical success factors, constraints, assumptions and authorization
39
Chicken
One involved but not committed to agile project
40
Coach
role that keep team focused on learning and the process
41
Collaberation
Method of cooperation among individuals to achieve common goal
42
Collective Code Ownership
Entire team together is responsible for 100% of code
43
Collocation
Entire team physically present, working in one room
44
Common cause
Issue solved through TREND ANALYSIS cuz issue is systematic
45
Communication
To share smooth and transparent info of needs
46
Command & Control
Decision created by higher-up in org and handed over to the team
47
Cone of Silence
Environment of the team that is free of distractions and interruptions
48
Continuous Integration
To consistently examine a team's work; To build and test entire system
49
Coordination
To organize work with goal of higher productivity and teamwork
50
Cost Performance Index (CPI)
To measure the cost spent on a project and its efficiency; Earned Value / Actual Cost = CPI
51
Cross-functional Team
Team who completes various functions to achieve a common goal; Able to do more than one role in a project
52
Crystal Family
Adaptable approach that focus on interaction btw ppl and processes that consists of families that vary based on team size, system criticality & project priorities; Contributed to Osmotic Communication
53
Cumulative Flow Diagram
Displays Feature Backlog, WIP & Completed features
54
Customer-valued Prioritization
Deliver max customer value early in order to win loyalty and support
55
Cycle Team
Time needed to complete a feature/user story
56
Daily Stand-up
Brief meeting where team share previous day's achievement, plan to make achievement, obstacle and how to overcome obstacle
57
Decide as late as possible
To postpone decision to determine possibilities and make decision when most amount of knowledge is available
58
DEEP
Product backlog qualities - Detailed, Estimate-able, Emergent and Prioritized
59
Disaggregation
To separate epics or large stories into smaller stories
60
Dissatisfaction
Demotivators - Work conditions, salary and management
61
Distributive Negotiion
To reach a deal through tactics so both parties receive highest amount of value possible
62
Done
When work is complete and meets the criteria - Complies, Runs without errors and passes predefined acceptance and regression tests
63
Dot Voting
Voting system where ppl receive a certain # of dots to vote on the options provided
64
Dynamic Systems Development Model (DSDM)
Model that provides a comprehensive for planning, managing, executing and scaling agile and iterative software development project based on 6 principles that involve 1) business needs/values, 2) active user involvement 3) empowered team 4) freq delivery 5) integrated testing 6) Stakeholder Collaboration
65
Earned Value Management (EVM)
EVM works well at iteration. Method to measure and communicate progress and trends at the current stage of project
66
Emergent
Stories that grow and change overtime as other stories reach completion in backlog
67
Epic
A large story that span iterations, then disaggregated into smaller stories
68
Escaped Defects
Defects reported after the delivery by customer
69
Expectancy Theory
An individual choose to behave in particular way over other behaviors because of expected results of chose behavior
70
Exploratory Testing
To inquire how software works with the use of test subjects using software and asking questions about software
71
Extreme Persona
Team-manufactured person that exaggerates to induce req a standard person may amiss
72
eXtreme Programming (XP)
Agile methodology in 1 week iterations and paired development
73
Feature-driven Development (FDD)
comprehensive model and list of feature included in the system before the design work begins
74
Fibonacci Sequence
Sequence of # used in Agile estimating (0, 1,2,3,5,8,13,20,40, 100)
75
Finish Task One by One
Task must be finished in all iterations to meet the "Definition of done" req as a way to track progress and let freq delivery
76
Fishbone Diagram
Root Cause diagram
77
5 Whys
Root Cause analysis that asks WHY 5 times
78
Fixed Time Box
Assigned tasks prioritized for completion based on estimated # of days; Top priority are usually completed first
79
Force Field Analysis
To analyze forces that encourage/resist change
80
Grooming
To clean up product backlog by removal of items, disaggregation of times or estimation of times
81
Herzberg's Hygiene Theory
A theory that state factors in workplace create satisfaction and dissatisfacton in relation to the job
82
High Performing Team
Team reaches MAX performance by creation of clear, detailed goals, open communication, accountability, empowerment, use of participatory decision model and the team consist of 12 or less ppl
83
Ideal Time
Amount of time needed to complete assignment without distractions/interruptions
84
Incremental Delivery
Functionality conveyed in small phases
85
Incremental Project Releases
To build upon prior release of goal, outcome, or product, not all req are met but after all release, the req will be met
86
Info Radiator
Artifacts used to help maintain transparency of project status to team and stakeholders
87
Info Refrigerator
Info that not transparent or useful to team and stakeholders
88
Intergrative Negotiation
To reach agreement collaboratively that creates more value for both parties by a win-win solution
89
Internal Rate of Return (IRR)
Discount rate that make Net Present Value (NPV) of all cash flows from a project = 0; Used to determine potential profitability of project/investment
90
Intraspectives
To inspect within, during a meeting with Agile team to review practices, usually when a project/issue occurs
91
Intrinsic Schedule Flaw
Poor estimation that happen at the beginning of iteration
92
INVEST
User story Pro - Independent, Negotiable, Valuable, Estimate, Small & Testable
93
Iteration
Work cycle, Scrum uses 2 - 4 wks, XP on 1 week
94
Iteration Backlog
Work to complete in a particular iteration
95
Iteration H
Iteration used to prep the software launch and to test software
96
Iteration 0
Iteration to complete tasks before dev work occurs, for tech and architectural spikes and to gather req into backlog
97
Just-In-Time
To min inventory cost by materials delivered before they are required
98
Kaizen
To continue improvement through small releases
99
Kanban
A signal used to advance transparency of WIP, new task can begin once a previous one is complete
100
Kanban Board
Chart that shows workflow stages to locate WIP
101
Kano Analysis
Analysis of product development & customer satisfaction based on needs fulfilled/no fulfilled vs. satisfaction/dissatisfaction
102
Last Responsible Moment
To make decision as late as possible in order to preserve all possible options
103
Little's Law
Limit WIP efficiently with development of appropriate cycle time
104
Low Performing Team
Lack of trust / No accountability / Fear of conflict / Less commitment / Less attention to details and results
105
Lean Software Development (LSD)
Focus of "Value Stream" to deliver value to customers. Goal to eliminate waste by focus on valuable feature of a system and to deliver value in small batches; Principles: 1) Waste elimination 2) Amplify learning 3) To decide late as possible 4) Deliver as fast as possible 5) Empowerment of team 6) To build in integrity 7) To see the whole
106
Maslow's Hierarchy of Needs
Suggest interdependent needs (motivators) of ppl on 5 levels in order: Physiological, Safety & Security, Social, Esteem and Self-Actualization
107
Min Viable Product (MVP)
A product with only essential features delivered to early adopters to receive feedback
108
Min Marketing Feature (MMF)
Smallest feature of product that provide value to end user
109
Monopoly Money
To give fake $ to business feature in order to compare the relative priority of those features
110
MoSCoW Analysis
Help stakeholders understand importance of each req delivered: Must have, Should have, Could have and Would like to have
111
Net Present Value (NPV)
Value that compares the amount invested today to present value of future cash receipts from the investment
112
Osmotic Communication
To communicate by sharing an environment
113
Pair Programming
Dev work together in XP practice
114
Pareto Principle
80/20 rule; For Agile project, 80% of development should be spent on the top 20% of the features the customers need
115
Parking Lot
Place for ideas that distract from main goal during a meeting
116
Participatory Decision Models
To have stakeholders' involvement in decision making with tech (like simple vote)
117
Persona
Depiction of customer of system with applicable details about usage
118
Pig
Committed individual impacted by the outcome
119
Plan-Do-Check-Act (PDCA)
Continuous improvement - work cycle in smaller quick iterations
120
Planning Game
In XP, to prioritize work & estimate effort req by creation of release plan
121
Planning Poker
Tool used to estimate team effort on user stories
122
Positive Value
To max value through INCREMENTAL work in order to gain competitive advantage
123
Pre-mortem
Team asked to define reasons of a project's failure and to ID causes of failure missed in previous analyses
124
Present Value
Way to calculate time value of money
125
Process Tailoring
To perfect agile process for a specific project and evt
126
Productivity
Effectiveness of production, measured with output per unit of input
127
Productivity Variation
Difference btw planned & actual performance
128
Product Backlog
Known features for a project
129
Product Road Map
Artifact displays planned project functionality
130
Product Vision
A doc that describes what product is, who will use the product, why the product will be used and how the product supports the company strategy
131
Product Vision Statement
Defines purpose & value of the product
132
Programmer
XP role; write the code
133
Progressive Elaboration
Approach for planning that occurs in CYCLES instead of upfront, which happens frequently
134
Refactoring
To adjust working code to improve functionality and convervation
135
Relative Prioritization
List of all user stories and feature order by high to low priority
136
Relative Sizing
To estimate size of story in comparison with another story
137
Release
Iteration outcomes delivered to cutomers
138
Req Review
To review req so they fulfill needs and priorities
139
Return of Investment (ROI)
Return of org makes on investment expressed by %
140
Risk-Adjusted Backlog
Product backlog adjusted to help balance the risk & value factors of product
141
Risk-based Spike
Helps the team remove major risk, and if the spike fails every approach possible, the project is define as "fast failure"
142
Risk Burn Down
Chart that displays risk and success with feature vs time
143
Risk Impact
To analyze the consequence of the risk if they occur based on their probability
144
Risk Probability
Likelihood that risk will occur
145
Risk Severity
How much the risk's consequence will influence the success/failure of a project
146
Role
A person's description that includes their function in Agile project
147
Rolling Wave Planning
To divide planning phase into stages
148
Root Cause Analysis
To investigate beyond symptoms of problem and to understand the root cause of the problem
149
Root Cause Diagram
Diagram to correlates different factors and symptom
150
Satisfaction
Worker's feeling when their needs are fulfilled (Motivators)
151
Schedule Performance Index (SPI)
Ratio of earned value to planned value; EV/PV = SPI
152
Scope Creep
Uncontrolled changes/growth in scope which goes beyond initial agreement
153
Software Development Life Cycle (SDLC)
Cycle tends to be long and requires a lot of advanced planning
154
Self-directing Team
Team has the capability to make their own decision, empowerment, mutual accountability and collective ownership of a project, which lead to more productive and efficient
155
Self-organizing Team
Natural formed team that interact with min management supervision
156
Servant Leadership
Leaders collaborate with the team and do anything the team does when needed
157
Shu-Ha-Ri Model
Understand learning & mastery = Shu (Obey rules), Ha (consciously move away from rule), Ri (consciously find individual path)
158
Specification Breakdown
This happen when req for the specification are incomplete or conflicting
159
Spike
Experiment that helps team answer, a specific question and determine future action
160
Sprint
Iteration that lasts from 1 week to month in order to measure velocity in scrum
161
Sprint Plan
doc explains sprint goal, task and req and how the tasks will reach completion
162
Story Map
Prioritization tool that backlogged stories made smaller and organized by user functionality
163
Swarming
Team collaborate to focus on single user story
164
Tabaka's Model
To describe team with values that include self-organization, empowered to make decision, belief in vision and success, committed team, trust, participatory decision-making, consensus-driven and construction disagreement
165
Task
Smaller job to fulfill a user story, divided among team
166
Team Velocity
of story points completed during iteration, used to determine planned capacity
167
Test-Driven Development (TDD)
A written acceptance test for a module with the code built to pass the test in order to ensure correct performance
168
Tester
In XP - Explain acceptance test to customer then consistently measure the product agst the test and record result for the team
169
Time-boxed
To set fixed delivery date for project/release
170
Tracker
In XP - a role to measure team's progress, and communicates the measurement to the team
171
Traditional Management
Top-down approach that consist of long cycle, heavy planning and minimal customer involvement
172
Trend Analysis
Analysis provides trends that will occur in the future to help control and implement continuous improvement
173
Two-way Communication
To let communication btw parties so their concerns and perspective are given for effective feedback
174
Unit Testing
Test used for continuous feedback to achieve quality improvement and assurance
175
Value Stream Mapping
Tool used to analyze a chain of process with desired outcome of eliminate waste
176
Variance
Measurement of how far apart data is from each other
177
Velocity
Total # of feature that team deliver in iteration
178
Wide-band Delphi Estimating
Estimation Tech for user stories - PO present user stories and discuss challenges; Each story's estimates plotted, and then team comes to agreement on the range of points
179
WIP Limits
To limit WIP so team maintain focus on complete work, maintain quality and deliver value
