





















Study with the several resources on Docsity
Earn points by helping other students or get them with a premium plan
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community for help and clear up your study doubts
Discover the best universities in your country according to Docsity users
Free resources
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
A comprehensive glossary of agile project management terms and concepts relevant to the pmi-acp exam. It covers a wide range of topics, including agile principles, practices, roles, and artifacts. Structured as a study guide, offering definitions and explanations for key terms such as agile manifesto, scrum, kanban, user stories, and various agile techniques. It also includes questions and answers related to agile methodologies, making it a valuable resource for exam preparation and understanding agile principles. Useful for university students, high school students and lifelong learners.
Typology: Exams
1 / 29
This page cannot be seen from the preview
Don't miss anything!
ACP - SOLUTION:->Agile Certified Practitioner Active Listening - SOLUTION:->Focuses on understanding what is said and provides feedback to confirm understanding. Involves: Listening, Understanding, Retaining, Actively Responding. Affinity Estimation - SOLUTION:->Technique to rapidly place user stories into similarly-sized groups. Agile Manifesto - SOLUTION:->Four statements of the values of Agile philosophy Agile Modeling - SOLUTION:->A representation of the workflow of a process or system that the team can review before it is implemented in code. Stakeholders should be able to understand it Agile Space - SOLUTION:->Work area that encourages collaboration, communication, transparency and visibility Agile Tooling - SOLUTION:->Software or artifacts that increase the sense of team
and encourage participation among members (could be version control SF or video conferencing) Analysis - SOLUTION:->Developing an understanding of potential solutions by studying the problem and underlying need Artifact - SOLUTION:->The output of a process or work, typically a document, drawing, model, or code. Brainstorming - Answer✅ Method of gathering ideas from a group - elicit a large number of ideas in a short time. Burn-Down Chart - SOLUTION:->A chart used to communicate progress during and at the end of an iteration (# of stories completed/remaining) Burn Rate - SOLUTION:->The cost of Agile work - the rate that the team consumes resources; cost per iteration. Burn-Up Chart - SOLUTION:->Chart that shows completed functionality over time. Progress trends up as stories are completed (value accumulated). Does not
responsible for 100% of code (all members of team can cross maintain code) - discourages specialization Collocation - SOLUTION:->Having the entire team physically working in one room Communication - SOLUTION:->Sharing information - in Agile, needs to be transparent and free- flowing Command & Control - SOLUTION:->Non-Agile principle where decisions are made by individuals higher up on the organizational chart and handed down to the team Compliance - SOLUTION:->Meeting a regulation (project justification) Cone of silence - SOLUTION:->Creating an environment free of distractions and interruptions for the team Cone of Uncertainty - SOLUTION:->describes the difficulty of estimating early due to unknowns and how that should improve over time. Implies that the Collective Code Ownership - Answer✅ Environment where the entire team is collectively
ability to estimate should get more accurate if estimates are agiven shortly before the work is performed. 5 Levels of Conflict - SOLUTION:->Problem Recognized, Disagreement, Contest, Fight/Flight, World War Conflict Resolution - SOLUTION:->Coming to an acceptable agreement when areas of conflict arise Continuous Integration - SOLUTION:->Regularly checking in each team member's work, building and testing the entire system Coordination - SOLUTION:->Orchestrating their work together with the goal of higher productivity & teamwork progress, and completed features over time Customer - SOLUTION:->Actual end-user or representative who will define and prioritize business value Cumulative Flow Diagram - Answer✅ Single chart that shows feature backlog, work-in-
DRY - SOLUTION:->Don't Repeat Yourself. Reinforces the "maximize the work not done" concept. DSDM - SOLUTION:->Dynamic Systems Development Model (an Agile framework primarily used outside the US) the schedule. Difficult in agile. Emergent - SOLUTION:->Characteristic of backlog items - stories should grow and change over time as other stories are completed Emotional Intelligence - SOLUTION:->Ability to relate to others and lead Epic - SOLUTION:->A very large story that will span iterations (must be disaggregated into component user stories before they are useful on a tactical level EVM - Answer✅ Earned Value Management - Earned value is a measure of how work is progressing against the plan. (Works better in waterfall because scope must be well-defined.) Planned Value - Answer✅ the amount of value the project SHOULD have earned at a point in
Escaped Defects - SOLUTION:->Defects that are reported by the customer after delivery - track to identify opportunities to improve processes Extreme Persona - SOLUTION:->A team-manufactured persona that is strongly exaggerated in order to elicit requirements that standard persona might miss. 5 Roles in XP - SOLUTION:->Coach, Customer, Programmer, Tracker, Tester eXtreme Programming - SOLUTION:->A highly disciplined Agile methodology that runs one week iterations and uses paired development Feature - SOLUTION:->A group of stories that delivers value to the customer FDD - SOLUTION:->Defining an overall model and list of features to be included in the system prior to starting design work 13, 20, 40, 100 Fishbone Diagram - SOLUTION:->A root cause diagram Fibonacci Sequence - Answer✅ Sequence of numbers used in Agile estimating - 0, 1, 2, 3, 5, 8,
Ideal Time - SOLUTION:->The amount of time an assignment would take if there were no interruptions or disruptions Incremental Delivery - SOLUTION:->Functionality should be delivered in small stages.
stakeholders (help maintain visibility) Information Refrigerator - SOLUTION:->Information not readily visible or useful to the team Innovation Games - SOLUTION:->Exercises used to elicit requirements from product owners, users, and stakeholders Interaction - SOLUTION:->Face-to-face communication; in contrast to processes/tools IRR - SOLUTION:->Internal Rate of Return - express profit as an earned interest rate. Bigger is better when weighing comparative benefits INVEST - SOLUTION:->Acronym describing benefits of good user stories (Independent, Negotiable, Valuable, Estimate-able, Small, and Testable) Iteration - SOLUTION:->work cycle (multiple iterations go into a release) - Scrum uses 2 - 4 weeks, XP uses 1 week Information Radiator - Answer✅ Artifacts used to communicate project status to the team and
Last Responsible Moment - SOLUTION:->Term reminding us to make decisions as late as possible in order to preserve all options for as long as possible 7 Principles of Lean - SOLUTION:->Eliminate Waste, Amplify Learning, Decide as late as possible, Deliver as fast as possible, Empower the team, Buld integrity in, and See the Whole Metaphor - SOLUTION:->The practice of using real-world examples for systems and components to describe how a project will be completed to stakeholders MMF - SOLUTION:->Minimal Marketable Feature - the smallest feature that can deliver value to users Negotiable - SOLUTION:->Part of INVEST (user stories) - stories are not set in stone and must be challenged and changed as they go from cards to complete code
NPV - SOLUTION:->Net Present Value - a way of determining the time value of money to calculate a project's worth to the business Osmotic Communication - SOLUTION:->Absorbing communication by sharing an environment Pair Programming - SOLUTION:->XP practice where developers work together (one driving keyboard and one looking) Parking Lot - SOLUTION:->Place to store ideas that might distract from the primary goal during a meeting - particularly used in requirements gathering Persona - SOLUTION:->An imaginary representation of the end user of a system that includes relevant details about usage to Chicken) Plan-Do-Check-Act - SOLUTION:->Work cycle (Deming) - similar to traditional, Pig - Answer✅ Agile - someone who is fully committed and impacted by the outcome (contrast
stories, represents the users/customer. Product Backlog - SOLUTION:->All known features for a project, regardless of iteration or release Product Road Map - SOLUTION:->Artifact showing planned product functionality
waterfall Prototyping - SOLUTION:->Modeling used to refine requirements Qualitative - SOLUTION:->Descriptive factors not measured numerically Quality - SOLUTION:->Conformance to specifications or requirements Quantitative - SOLUTION:->Factors measured numerically Refactoring - SOLUTION:->Reorganizing working code to improve functionality and maintenance - should not affect functionality or performance Relative Sizing - SOLUTION:->Estimating the size of a story in comparison with another story (most difficult to least, without specific points) Release - SOLUTION:->A group of iteration outcomes designed to be delivered to end users
Risk - SOLUTION:->Uncertainty that could affect project Risk Burn Down - SOLUTION:->Chart showing risk to success associated with each feature vs time - should burn down or lessen as the project goes along Role - SOLUTION:->Description of how a person functions within an Agile project. Roles have different names in different methods Root Cause Analysis - SOLUTION:->Technique to look beneath the symptoms of a problem to understan the fundamental problem that caused it Root Cause Diagram - SOLUTION:->Ishikawa, Fishbone, or Cause/Effect - illustrate how different factors relate to the symptom 3 Pillars of Scrum - SOLUTION:->Visibility, Inspection, Adaptation Scrum of Scrums - SOLUTION:->Meeting with multiple scrum masters from different teams, used to coordinate very large projects
Scrum Master - SOLUTION:->Responsible for helping the team follow Scrum methodology SDLC - SOLUTION:->System or Software Development Life Cycle - non-Agile approach with long cycles and lots of upfront planning Self-organizing Team - SOLUTION:->Agile concept for teams that form organically and interact without a lot of management oversight Servant Leadership - SOLUTION:->Agile concept contrasted with command and control - leaders work with the team and should be willing to do anything they ask the team to do Silo - SOLUTION:->Isolated work; not Agile Smells - SOLUTION:->Symptoms of problems affecting Agile teams and projects - i.e., Smell Test Spike - SOLUTION:->Quick experiment used to help the team answer a specific question and determine path forward