PMI - ACP Flashcards
1
Q
Adaptive Leadership
A
A leadership style that helps teams thrive and overcome challenges throughout the project
2
Q
Agile
A
To develop a goal through periodic experimentation in order to fulfill the need of a complex decision
3
Q
Agile Adaptation
A
To adapt the project plan continuously through retrospectives in order to maximize value creation during the planning process
4
Q
Acceptance Test Driven Development
A
A method used to communicate with business customers, developers and testers before the coding begins.
Writing acceptance tests before coding
5
Q
Agile Coaching
A
To help achieve goals that is either personal or organizational
6
Q
Agile Experimentation
A
To use the empirical process, observation, and spike introduction while executing a project to influence planning
7
Q
Agile Manifesto
A
Individuals and interactions over process and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
8
Q
Agile Manifesto Principles
A
12 principles
9
Q
Customer Satisfaction
A
To satisfy customers through early and continuous delivery of products, to test and receive feedback, to inform customers on progress, and to fulfill the customers value by completing priority requirements
10
Q
Welcome Changes
A
To allow quick responses to changes in the external environment, and late in development to maximize the customers competitive edge
11
Q
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 times
12
Q
Collocated TEam
A
To have individuals work together daily on a project to implement osmotic communication, focus and receive instant feedback to achieve a common goal
13
Q
Motivated individuals
A
To give individuals the empowerment, environment, support and trust needed to complete a task successfully
14
Q
Face to Face Conversation
A
The most effective and efficient way to communicate in order to receive direct feedback and influence osmotic communication
15
Q
Working Software
A
Working software enables the measurement of progress, enhance customer satisfaction, and maintain and improve the quality of the software to help support project goals
16
Q
Constant Pace
A
To help the team members establish a healthy work-life balance, remain productive, and respond to changes swiftly for progress during the project
17
Q
Continuous Attention
A
To enhance the agility and time spent on work requirements in order to retain a well balanced work environment
18
Q
Simplicity
A
Allows team members to focus on what is necessary to achieve the requirements needed to create and delivery value to the project and customer
19
Q
Self Organization
A
A team that knows how to complete tasks effectively, had dedication to the project, and is expert on the process and project
20
Q
Regular Reflection
A
This allows a team to learn how to become more effective, what changes need immediate implementation and behaviour that needs adjustments
21
Q
Agile Methodologies
A
A way to complete a goal effectively and efficiently. Examples of Agile Methodologies include XP, Scrum and Lean
22
Q
Agile Modeling
A
A workflow depiction of a process or system a team can review before it is turned into code. Stakeholders should understand the model
23
Q
Agile Planning
A
The most important aspect of the Agile project. Planning happens at multiple levels such as strategic, release, iteration and daily. Planning must happen up-front and can change throughout the project
24
Q
Agile Practices
A
To make use of the Agile principles through activities
25
Agile Projects
A project that occurs based on the Agile Manifesto and Agile Principles
26
Agile Smells
Symptoms of problems that affect Agile Teams and Projects
27
Agile Themes
Themes used to help the team focus on the functions of iterations
28
Agile Tooling
To increase team morale with software and artifacts
29
Analysis
To develop possible solutions by studying the problem and its underlying need and to understand the information provided
30
Approved Iterations
After the deadline of iteration is reached, the team and stakeholders conduct a meeting for approval. Stakeholders approve the iteration if the backlog used supports the product increments
31
Architectural Spikes
Spikes that relate to any area of a system, technology, or application domain that is unknown
32
Automated Testing Tools
```
These tools allow for efficient and strong testing.
Peer Reviews
Periodical Code Reviews
Refactoring
Unit Tests
Automated and Manual Testing
```
33
Being Agile
To work in a responsive way to deliver the products or services a customer needs and when the want the product or services
Starts with internalizing the agile mindset, then using that understanding to select and implement correct practices
34
Burn Down Chart - Backlog
A chart used to display progress during and at the end of an iteration. 'burning down' means the backlog will lessen throughout the iteration
35
Burn Rate
The rate of resources consumed by the team, also cost per iteration
36
Burn-Up Chart - Completed Functionality
A chart that displays completed functionality. Progress will trend upwards, as stories are completed. Only shows complete functions, it is not accurate at predicting or showing work in progress.
37
CARVER - Goals and Missions of the Project
An acronym to measure the goals and missions of the project with each letter meaning
```
Criticality
Accessibility
Return
Vulnerability
Effect
Recognizability
```
38
Ceremony
A meeting conducted during an Agile project that consists of daily stand up. iteration planning, iteration review and iteration retrospective
39
Change
To change requirements that increase value to the customer
40
Chicken
An individual involved but not committed to an Agile project
41
Coach
A team role that keeps the team focused on learning and the process
42
Collaboration
A method of cooperation among individuals to achieve a common goal
43
Collective Code Ownership
The entire team together is responsible for 100% of the code
44
Common Cause
An issue solved through trend analysis because the issue is systematic
45
Command and Control
Decisions created by higher up individuals in the organization and handed over to the team
46
Cone of Silence
An environment for the team that is free of distractions and interruptions
47
Conflict Resolution
An agreement made after a conflict
48
Continuous Improvement
To ensure that self-assessment and process improvement occurs frequently to improve the product
49
Continuous Integration
To consistently examine a team members work. To build, and test the entire system
50
Coordination
To organize work with the goal of higher productivity and teamwork
51
Test Driven Development (TDD)
A written acceptance test for a module with the code built to pass the tests in order to ensure correct performance.
52
Extreme Programming (XP)
A methodology in Agile with one week iterations and paired development
53
Adaptive Software Development
Exhibits continuous adaptation to the project and its processes with characteristics that include: Mission focused, feature based, iterative, time-boxed, risk driven, and change tolerant
Enable teams to quickly and effectively adapt to changing requirements or market needs by evolving their products with lightweight planning and continuous learning.
54
Feature Driven Development (FDD)
A comprehensive model and list of features included in the system before the design work begins
55
Dynamic Systems Development Model (DSDM)
A model that provides a comprehensive foundation for planning, managing, executing and scaling agile and iterative software development projects based on nine principles that involve:
```
Business needs/value
Active user involvement
Empowered teams
Frequent delivery
Integrated testing
Stakeholder collaboration
```
56
Crystal Family - Alistair Cockburn
Focuses on individuals and interaction, rather than processes and tools
An adaptable approach that focuses on interaction between people and processes that consists of families that vary based on team size, system criticality and project priorities.
Each methodology is customized
Low criticality, small teams = Crystal Clear
Teams of 10 - 20 = Crystal Yellow
Teams of 20 - 50 = Crystal Orange
Teams of 50 + = Crystal Red
57
Cross Functional Team
Team consists of members who can complete various functions to achieve a common goal. Team members are able to do more that one role in the project.
58
Cumulative Flow Diagram
A chart that displays feature backlog, work in progress and completed features
59
Customer Valued Prioritization
To deliver the maximum customer value early in order to win customer loyalty and support
60
Cycle Time - Feature
The time needed to complete a feature (user story)
61
Decide as late as possible
To postpone decisions to determine possibilities and make the decision when the most amount of knowledge is available
62
DEEP - Product Backlog
```
The qualities of a product backlog which include:
detailed,
estimate-able,
emergent
prioritized
```
63
Disaggregation
To separate epics or large stories into smaller stories
64
Distributive Negotiation
To reach a deal through tactics so both parties receive the highest amount of value possible
65
Done
When work is complete and meets the following criteria:
Compiles, runs without errors, and passes predefined acceptance and regression tests
66
Dot Voting
A system of voting where people receive a certain number of dots to vote on the options provided
67
Emergent
Stories that grow and change over time as other stories reach completion in the backlog
68
Emotional Intelligence
An individuals skill to lead and relate to other team members
69
Epic Story
A large story that spans iterations that is disaggregated into smaller stories
70
Escaped Defects
Defects reported by the customer after the delivery
71
Expectancy Theory
An individual chooses to behave in a particular way over other behaviours because of the expected results of the chosen behaviour
72
Exploratory Testing
To inquire how the software works with the use of test subjects using the software and asking questions about the software
73
Extreme Persona
A team manufactured persona that exaggerates to induce requirements a standard persona may miss
74
Feature
A group of stories that deliver value to the customer
75
Finish Tasks One by One
Tasks must be finished in all iterations to meet the 'definition of done' requirements as a way to track progress and allow frequent delivery
76
Fishbone Diagram
A root cause diagram
77
Five Whys - Toyota
The root cause analysis technique that asks WHY five times. The problem is looked into deeper each time WHY is asked.
78
Fixed Time Box
Assigned tasks prioritized for completion based on an estimated number of days. Top priorities usually completed first.
79
Focus
To stay on task and is facilitated by scrum master of coach
80
Force Field Analysis
To analyze forces that encourage or resist change
81
Functionality
An action the customer must see and experience from a system, which will add value to the customer
82
Grooming
To clean up the product backlog by removal of items, disaggregation of items or estimation of items
83
Ground Rules
Unwritten rules decided and followed by team members
84
Herzberg's Hygiene theory
A theory that states factors in the workplace create satisfaction and dissatisfaction in relation to the job
85
High Bandwidth Communication
Face-to-face communication that also includes non verbal communciation
86
High Performance Team
This team reaches maximum performance by creation of crystal clear,
detailed goals,
open communication,
accountability,
empowerment, use of the participatory decision model,
and the team consists of twelve or less dedicated members
87
Ideal Time
The amount of time needed to complete an assignment without distractions or interruptions
88
Incremental Delivery
Functionality conveyed in small phases
89
Incremental Project Releases
To build upon the prior release of a goal, outcome, or product.
Not all requirements are met, but after all releases, the requirements will be met
90
Information Radiator
Artifacts used to help maintain transparency of a project status to team members and stakeholders
91
Information Refrigerator
Information that is not transparent or useful to the team and stakeholders
92
Innovation Games
Practice used to induce requirements from product, owners, users and stakeholders
93
Integrative Negotiation - Win Win
To reach an agreement collaboratively that creates more value for both parties
94
Intraspectives
To inspect within, during a meeting with the agile team to review practices, usually when a problem occurs
95
Intrinsic Schedule Flaw
Poor estimation that occurs at the beginning of an iteration
96
INVEST - Good User Stories
```
The benefits of good user stories
Independent
Negotiable
Valuable
Estimate-able
Small
Testable
```
97
Iteration
Work cycle, Scrum uses 2 - 4 weeks, XP uses 1 week
98
Iteration backlog
Work to complete in a particular iteration
99
Iteration H - Launch or Test
Iteration used to prepare the launch of software and to Test software
100
Iteration 0
Iteration to complete tasks before development work occurs, for technical and architectural spikes and to gather requirements into the backlog
101
Iteration Retrospective
A meeting used in Scrum the team discusses ways to improve after work is completed
102
Just in Time
Used to minimize inventory cost by materials delivered before they are required
103
Kaizan - continuous improvement
Based on Japanese Management philosophy - to continue improvement through small releases
104
Kanban
A signal used to advance transparency of work in progress, a new task can begin once a previous one is complete
105
Kano Analysis - product development and customer satisfaction
An analysis of product development and customer satisfaction based on fulfilled vs. not fulfilled needs as it relates to satisfaction and dissatisfaction
prioritizing features on a product roadmap based on the degree to which they are likely to satisfy customers.
Delighters/Exciters - deliver unexpected, novel or new high value benefits
Satisfiers - The more the better, these features bring value to the customer
Dissatisfiers -Cause a user to dislike the product if they are not there
Indifferent - No impact on the customer
106
Last responsible moment
To make decisions as late as possible in order to preserve all possible options
107
Lean Methodology
To eliminate Waste, an agile methodology derived from manufacturing
```
Eliminate Waste
Empower the team
Deliver fast
Optimize the whole
Build quality in
Defer decisions
Amplify learning
```
108
Little's Law - Limit WIP.
The law that limits work in progress efficiently with development of an appropriate cycle time
the more things that you work on at any given time (on average) the longer it is going to take for each of those things to finish (on average)
109
Low performing team
This team has a lack of trust, no accountability, fear of conflict, less commitment and less attention to details and results
110
Lean Software Development
This methodology focuses on the 'value stream" to deliver value to customers. The goal is to eliminate waste by focusing on valuable features of a system to deliver the value in small batches. Principles of lean include:
```
Elimination of waste
Amplify Learning
Decide as late as possible
Deliver as fast as possible
Empowerment of the team
Build in integrity
See the whole
```
111
Maslow hierarchy of needs
This theory suggests the interdependent needs (motivators) of people based on five levels in order:
```
Physiological
Safety and Security
Social
Esteem
Self Actualization
```
112
Metaphor
Explain how a project will be completed successfully to stakeholders by use of real world examples of systems and components
113
Minimal Viable Product
A product with only the essential features delivered to early adopters to receive feedback
114
Minimal Marketing feature - MMF
The smallest feature of a product that provides value to the end user
115
Fibonacci Sequence
A sequence of number used in Agile estimating, 0,1,2,3,5,8,13,20,40, 100
116
Planning Poker
A tool used to estimate team effort on user stories
117
Monopoly money
To give fake money to business features in order to compare the relative priority of those features
118
Wide Band Delphi Estimating
An estimation technique for user stories. The PO presents user stories and discusses challenges.
Each story's estimates plotted, and then the team comes to an agreement on the range of points
Anonymous forms with experts and group discussion of estimates
119
Affinity Estimation
A method used to quickly place user stories into a comparable sized group
120
100 Point Method
A method that allows customers to score different features - Total = 100 points
121
MoSCoW Analysis
An analysis to help stakeholders understand the importance of each requirement delivered.
Must Have
Should Have
Could Have
Would like to have
122
Osmotic Communication
Communicate by sharing an environment
123
Pair Programming
When developers work together in XP practice
124
Pareto Principle
Known as 80/20 rule. For Agile projects this means that 80% of all development should be spent on the top 20% of features that the customer needs
125
Parking Lot
A storage place for ideas that distract from the main goal during a meeting
126
Participatory Decision Models
To have stakeholders involvement in decision making with techniques such as a simple vote
127
Persona
A depiction of the customer of the system with applicable details about usage
128
Pig
A committed individual impacted by outcome
129
Plan - Do - Check - Act
Work cycle in smaller, quicker iterations than traditional
130
Planning game
To prioritize work and estimate efforts required by creation of a release plan in XP
131
Positive Value
To maximize value through incremental work in order to gain competitive edge
132
Pre-Mortem
Team members asked to define reasons of a project's failure and to identify causes of failure missed in previous analysis
133
Process Tailoring
To perfect agile processes for a particular project and environment
134
Productivity
The effectiveness of production, usually measured with output per unit of input
135
Productivity Variation
The difference between the planned and actual performance
136
Product Backlog
The known features for a project
137
Product Road Map
An artifact that displays planned project functionality
138
Product Vision
A document that describes what the product is, who will use the product, why the product will be used and how the product supports the strategy of a company
139
Product Vision Statement
A statement that defines the purpose and value of the product
140
Progressive Elaboration
An approach for planning that occurs in cycles instead of upfront, which happens frequently.
141
Project
An enterprise planned and designed to create a product, service or result
142
Prototyping
A model used to perfect requiremetns
143
Qualitative
Descriptive data used for analysis
144
Quality
The specifications and requirements of a product or service measured against the standard product or service in the industry
145
Quantitative
Numerical data used for analysis
146
Refactoring
To adjust working code to improve functionality and conservation
147
Relative Prioritization
A list of all user stories and features ordered by highest priority to the lowest priority
148
Relative Sizing
To estimate the size of a story in comparison with another story
149
Release
Iteration outcomes delivered to the customers
150
Release Plan
A document that describes the timeline of a product release
151
Requirements at a high level
Requirements are in the form of user stories, and collected at a high level to estimate a budget
152
Requirements Prioritization Model
A model to rate each feature with the calculation of weighted formula defined by the team
153
Requirements Review
To review the requirements so they fulfill the needs and priorities of stakeholders
154
Risk
The uncertainty of an unwanted outcome related to the project
155
Risk Adjusted Backlog
A product backlog adjusted to help balance the risk and value factors of a product
156
Risk Based Spike
The spike helps the team remove major risks, and if the spike fails every approach possible, the project is defined as a "Fast Failure"
157
RIsk Burn Down Chart
A chart that displays risk and success with feature vs. time
158
Risk Impact
To analyze the consequences of the risk if they occur based on their probability
159
Risk Probability
The likelihood that a risk will occur
160
Risk Severity
How much the risk's consequences will influence the success or failure of a project.
Risk Probability (%) x Risk Impact ($) = Risk Severity
161
Rolling Wave Planning
To divide the planning phase into stages
162
Root Cause Analysis
To investigate beyond the symptoms of the problem and to understand the root cause of the problem
163
Root Cause Diagram
A diagram that correlates different factors and the symptom
164
Cost Performance Index (CPI)
To measure the cost spent on a project and its efficiency
Earned Value/Actual Cost = CPI
165
Schedule Performance Index - SPI
The ratio of earned value to planned value
EV/PV = SPI
A value of 1 shows that the project operates in line with the planned schedule.
If the SPI exceeds 1, the project is ahead of the plan while a value below 1 indicates that it is behind schedule
166
Earned Value Management
EVM works well at iteration. It is a method to measure and communicate progress and trends at the current stage of the project
167
Present Value
A way of calculating the time value of money
168
NPV - Net Present Value
A value that compares the amount invested today to the present value of future cash receipts from the investment
NPV - Sum of the discounted net cash flows
169
ROI
Return on Investment - The return an organization makes on an investment expressed by a percentage %
ROI = Return - Cost - Investment / Investment
170
IRR - Internal Rate of Return
Internal Rate of Return is a discount rate that makes the net present value of all cash flows from a project equal to zero. Used to determine potential profitability of a project or investment
IRR is uniform for investments of varying types and, as such, can be used to rank multiple prospective investments or projects on a relatively even basis.
The internal rate of return (IRR) is the annual rate of growth that an investment is expected to generate.
171
Scope Creep
The uncontrolled changes or growth in a project's scope which goes beyond the initial agreement
172
Scrum Master
The leader that helps the team to follow Scrum methodology
173
Software Development Life Cycle
This cycle tends to be long and requires a lot of advanced planning
174
Self-Directing Team
This team has the capability to make their own decisions
Empowerment
Mutual accountability
Collective ownership
Which leads them to be more productive and efficient
175
Self-Organizing Team
Naturally formed teams that interact with minimal management supervision
176
Servant Leadership
Leaders collaborate with the team and do anything for the team to get what they need
177
Shu-Ha-Ri Model - Learning and Mastery
Originated in Japan as a way to understand learning and mastery
Shu - Obeying the rules
Ha- Consciously moving away from the rules
Ri - Consciously finding an individual path
178
Social Media Based Communication
Communication used conveniently to receive instant feedback, ideas and requirements from a particular community
179
Special Cause
A cause that occurs once because of special reasons
180
Specification Breakdown
This occurs when requirements for the specification are incomplete or conflicting
181
Spike
An experiment that helps a team answer, a particular question and determine future actions
182
Sprint
A consistent iteration that lasts from one week to one month in order to measure velocity in Scrum
183
Sprint Plan
A document that explains sprint goals, tasks and requirements and how the tasks will reach completion
184
Sprint Retrospective
A team member meeting that occurs after each sprint to evaluate the product and process to improve efficiency and effectiveness
185
Sprint Review
A meeting that occurs after each sprint to show the product or process to stakeholders for approval and to receive feedback
186
Stakeholder
An individual with an interest in the outcome
187
Stakeholder Management
To ensure stakeholders remain informed and that the achievement of their needs are met
188
Story Card
An index card that displays the user story
189
Story Map
A prioritized tool that backlogged stories made smaller and organized by user functionality
190
Story Point
A unit of measurement to estimate the difficulty of a user story
191
Sustainability
A maintainable pace of work that is intense yet steady
192
Swarming
When the team collaborates to focus on a single user story
193
Tabaka's Model - Team Values
A model originated in Japan to describe a team with values that include:
```
Self Organization
Empowered to make decisions
Belief in vision and success
A committed team
Trust
Participatory decision making
Consensus-driven
Construction disagreement
```
194
Tasks
The smaller jobs to fulfill a user story, usually divided among team members
195
Team
A group of individuals charged with the responsibility of delivery and value of a project
196
Teamwork
Team members function in a way that is collaborative to complete tasks and reach a common goal, mostly achieved with strong communication
197
Team Empowerment
A team that is empowered has collaboration, responsibility and self-sufficiency
198
Team Formation
Formation happens when a team creates ground rules and processes to build bonds and shared goals
199
Team Participation
When the team discusses the requirements that will fulfill the customers needs
200
Team Velocity
The number of story points completed during iteration, and used to determine the planned capacity
201
Technical Debt
Technical decisions a team chooses to not implement currently, but must do so or face the difficulty in the future
202
Tester
Explains acceptance test to the customers then consistently measures the product against the test and records results for the team (XP Role)
203
Theme
A group of stories, iteration or releases idea determined by the customer and the team agrees with the idea
204
Time-boxing
To set a fixed delivery date for a project or release
205
Tracker
A role in XP that measures the team's progress, and communicates measurements to the team
206
Traditional Management
A top-down approach that consists of long cycles, heavy planning and minimal customer involvement
207
Transparency
To show everyone's involvement and progress to the entire team
208
Trend Analysis
This analysis provides trends that will occur in the future to help control and implement continuous improvement
209
Two Way Communication
To allow communication between parties so their concerns and perspectives are given for effective feedback
210
Unit Testing
These tests are used for continuous feedback to achieve quality improvement and assurance
211
Usability Testing
An exploratory test which uses a test subject to understand the usability of the software
212
Users Involvement
The active involvement of users in the development cycle of a project so team members can receive feedback about the user's requirements
213
User Story
At least one business requirement that increases the value for the user
214
Validation
The way to make sure that the product is acceptable to the customer
215
Value
The worth of a product, project or service
216
Value Based Prioritization
To allow the PO or customer determine which function to implement first based on the value it delivers
217
Value Driven Delivery
To realize the values need to deliver a project
218
Value Stream Mapping
A tool used to analyze a chain of processes with the desired outcome of eliminating waste
219
Variance
The measurement of how far apart data is from each other
220
Velocity
Sum of story points completed in an iteration
The total number of features that a team delivers in an iteration
221
Verification
To ensure the product meets requirements and specifications
222
Visibility
The team's work and progress must be transparent to all stakeholders
223
Waterfall
Resistant to change that requires heavy planning and sequential, traditional approach
224
WIP Limits
To limit work in progress. Stories that have started, which are displayed in workflows to show progress and what still needs to be completed
225
Workflow
A series of phases or stages the team has agreed to execute as a project
226
Agile Declaration of independence
```
Six Rules:
Increase ROI
Deliver reliable results
Expect uncertainty
Unleash creativity and innovation
Boost performance
Improve effectiveness and reliability
```
227
Empirical Process - Based on experience and observation
```
Interactive
Incremental
Change Often
Adapt
Pass through reviews
```
228
Knowledge Work Projects are Different
Work is invisible
Work is changing
Continuous innovation, learning and teaching
Workers are assets, not costs
229
Agile Mindset
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
230
TCPI - To complete Performance Index - Efficiency
The future cost performance of a project
To Achieve Original Budget
BAC - EV / BAC - AC
To Achieve the Estimate at Completion
BAC - EV / EAC - AC
231
Work in Progress
WIP Consumes investment capital and delivers no ROI
WIP hides bottlenecks that slow overall workflow and masks efficiency issues
WIP presents risk in the form of potential rework
232
Scrum Pillars
Transparency
Inspection
Adaptation
233
Parkinsons Law
Work tends to expand to fill the time available
234
Tuckman Model of Team Formation and Development
```
Forming = Directing
Storming = Coaching
Performing = Delegating
Norming = Supporting
```
235
Average Velocity
Sum of story points completed from n interations/n
236
Throughput
Throughput is a measure of the number of work items completed during an iteration or another period of time
237
Defect Rate
Defect rate = Number of defects/number of items
238
Lead Time
Lead Time = Time of completion - time of adding an item to the board
From entering the board at the ready stage to exiting the completion stage
239
Work in Queue
Number of features for which work has not yet started
240
Earned Value
The portion of the approved budget or story points that are allocated to a completed item
241
Planned Value
The budget or story point value of items that were planned to be completed at a point in time
242
Actual Cost
The amount of cost consumed at a point in time
243
Cost Variance
The difference between the earned value and the actual cost at a point in time
Cost Variance = Earned Value - Actual Cost
244
Estimate At Completion
Budget at Completion BAC / CPI
$100,000 / ,67 = $149,253
245
Agile Unified Process
Model - Understand the business and Identify solutions
Implementation - Transform the model into executable code
Test - Perform and objective evaluation
Deployment - Plan for the delivery
Configuration Management - Manage access to project artifacts
Project Management
Environment - Support the project
246
ESVP - Participation evaluation and personas
Explorer - Hear new ideas and engage
Shopper - Looking for new insights that add value to themselves
Visitor - Looking for a distraction from work
Prisoner - Would rather be somewhere else but were forced to attend
