GR8 PM ACP Exam Prep

Card Set Information

GR8 PM ACP Exam Prep
2014-06-13 02:59:23
ACP Agile

GR8 PM ACP Exam Prep 152 Flascards
Show Answers:

  1. Sufficient-to-Purpose
    An intermediate work product that needs to be only good enough to help the agile project team move forward.
  2. Cooperative Game Goals
    Delivering the software and creating an advantageous position for the next game
  3. Weick's Principle of Small Wins
    Delivering running, tested, useful code at regular intervals is a motivating reward for the project team
  4. Information Radiator
    A display of project-related information in a place where passerby can see it.
  5. Colocation
    Placing the project team in close proximity (i.e. in the same room) to facilitate communication
  6. Erg-second
    A "unit" of agile measure that captures the cost in both labor and time to get a project-related question answered.
  7. Mictotouch Intervention
    The project leader gets the team to make small changes that they do not mind and which causes the team to become more aligned in the same direction.
  8. Test-driven Development (TDD)
    The test, or executable example, is written before deciding how to design the code.
  9. Daily Stand-up Meeting
    Each day, the team meets face-to-face for a maximum of fifteen minutes to update each other on their status and on any obstacles that are slowing them down.
  10. Roadblock
    An obstacle or impediment that slows down team members during an iteration.
  11. Scrum Master
    A scrum team member who ensures the process is understood and followed, shields the team from outside interference, and removes roadblocks for the team.
  12. Venture-capital Financing Model
    The sponsor provides a round of financing for a certain amount work, and the contracted company must produce results in order to get more funding.
  13. Planning Game
    An XP technique where the sponsors write story cards for new features, the developers estimate the time it will take, and the customers prioritize the stories.
  14. Blitz Planning
    An index card-bases planning session in which the sponsor, business expert, expert user, and developers together build the project map and timeline, including tasks and dependencies.
  15. Product Backlog
    A prioritized list (of feature or tasks) of all the tings the scrum team needs to do.
  16. Sprint Backlog
    A prioritized, detailed task list for the current sprint that the team promises to deliver to the sponsors at the end of the sprint.
  17. Team Reflection Workshop
    A periodic work pause to reflect on the product, progress, and process.
  18. Burn Chart
    A time-based graph of features to be completed over time and features completed so far.
  19. Walking Skeleton
    A Crystal technique in which there is a tiny implementation of the system that performs a small end-to-end function linking the main architectural components.
  20. Exploratory 3600
    A Crystal technique where a pre-project safety check is performed.
  21. Epic
    A high-level, valuable business or product function that typically is broken down into smaller stories for inclusion in a sprint.
  22. Fibonacci Sequence
    A number series (1, 2, 3, 5, 8, 13, 21, 34, 55) when the next number is derived by adding the previous two; used by scrum teams during "planning poker" to provide value point estimates for stories.
  23. Scanning
    The agile practice of looking ahead to learn the unknown and to reduce uncertainty.
  24. Timeboxing
    Setting a fixed time limit to overall development efforts while letting other elements (e.g. scope) vary.
  25. Kanban
    A continuous improvement approach which has periodic releasable timeframes and which does not require strict iteration lengths for all stories.
  26. Adaptation
    Allowing requirement or design issues to arise and then building them into the product.
  27. Refactoring
    Constantly improving a product's internal design (e.g. rewriting code) without changing its behavior to make the product more reliable and adaptable.
  28. Compliance Documentation
    Documentation necessary to appease external bodies (e.g., regulatory agencies) but which has little value in communicating customer value to the agile development team.
  29. Project Chunking
    Taking large projects and breaking them down into smaller pieces that reduce risk and add customer value sooner.
  30. Retrospective
    A meeting where the team gathers after completing an increment of work to inspect and adapt their methods and teamwork.
  31. Self-transcendent
    The agile team's empowerment to make decisions to get work done and to strive continuously to "find the limit"
  32. Satisfy the Customer
    According to the Agile Manifesto, the highest priority that drives agile team.
  33. Cowboy Coding
    Considered the least disciplined of agile methodologies.
  34. Iteration
    A period, usually two to four weeks, in which the agile team codes and tests one or more small features resulting in potentially releasable software.
  35. Present Value
    The amount an investor has today to generate a known amount in the future.
  36. The Three Brainstorming Activities that May be Performed During Agile Retrospectives
    • Free-for-all
    • Round-robin
    • Silent individual generation of ideas
  37. Project Data Sheet (PDS)
    A single page summary of key project management information, product capabilities, and business and quality objectives, the PDS is the minimum documentation for an agile project's objectives.
  38. Trade-off (or Flexibility) Matrix
    A grid which shows the relative importance of project constraints (i.e. scope, schedule, cost, quality) in terms of Fixed, Firm, or Flexible; only one constraint may be Fixed.
  39. Feature
    A product component that provides some valuable functionality for the customer, typically accomplished in one or more agile stores.
  40. Scopeboxed Plan
    A plan that defines the features the team will build in advance, but where the release date is uncertain.
  41. Timeboxed Plan
    A plan the defines the release date in advance, but where the specific features that the release will include are negotiable.
  42. Batman
    On an XP team, the "Batman" deals with organizational emergencies and support requests so the other programmes can focus on programming.
  43. Customer-centric Stories
    Stories that are written from the on-site customer's point of view, and provide something that the customer cares about.
  44. Exploratory Spike
    A story used to solve a difficult technical problem or to learn enough to posit another solution that will solve it.
  45. Velocity
    The number of story points a team can complete in an iteration.
  46. Risk Census
    A list of the project's unique risks, particularly when using XP practices
  47. Transition Indicators
    In XP risk management, triggers that tell you when the risk has materialized.
  48. Shuffle Time
    The time it takes to move from one activity to another during agile retrospectives.
  49. Performance Measure Baseline (PMB)
    PMB is the total number of story points planned for a release.
  50. Planned Percent Complete (PPC)
    PCC is the number of the current sprint (n) divided by the total number of planned sprints (T), or n/T
  51. Payback Period
    The amount of time required to earn back an initial investment of cash
  52. Threshold (or Must-Have) Features
    Features that must be present in the product for it to be successful.
  53. Exciters and Delighters
    Features that provide great customer satisfaction, often adding a price premium to a product
  54. Forecasted Velocity
    An estimate (or forecast) of team velocity when it is either impossible or impractical for the team to run an iteration, and they do not yet have any historical observations.
  55. The Three Ways of Estimating Velocity
    • Use historical values
    • Run an iteration
    • Forecast velocity
  56. Risk Audit
    Examines the effectiveness of risk responses and is conducted as part of the retrospective meeting
  57. Iteration H
    A hardening iteration where the agile team prepares for the final rollout of a project
  58. Handoff Iteration
    An iteration used to prepare the formal documentation and other deliverables that production requires, including attending final approval meetings
  59. Repostory
    A master storage area for all the team's file and their history; typical of XP projects
  60. Sandbox
    The local development area for each team member, it contains a copy of all the files in the team repository from a recent snapshot in time.
  61. Synchronous Intergration
    The practice of confirming that the build and test succeed before moving on the the next task
  62. Collective Code Ownership
    Everyone on the team shares responsibility for the quality of the code, allowing anyone to make necessary changes anywhere.
  63. Daily Scrum
    A 15 minute daily meeting where all participants specifically describes what they did yesterday what they plan to do today, and what problems are preventing them from making progress
  64. Coach
    An XP team leader who helps the tam reach its potential and encourages discipline in XP practices
  65. Fractional Assignment
    Assignment of people to multiple projects simultaneously, a practice not recommend when using most agile methodologies
  66. Technical Debt
    The total amount of imperfect design and implementation decisions in the project
  67. Story
    A self-contained element of a project that typically corresponds to an individual feature and represents one to two days of work
  68. Greenfield Project
    A project where the team is creating a new codebase from scratch; the preferred method of implementing XP for the first time in an organization.
  69. Pair Programming
    An XP practice where two programmers are paired at a keyboard, with one person (the driver) coding and the other person (the navigator) thinking
  70. Mute Mapping
    A practice where an XP team gathers at a whiteboard to silently arrange annotated index cards; often performed at iteration retrospectives
  71. Showing Empathy
    A part of active listening, acknowing that people's feelings of loss of frustration are valid
  72. Force Field Analysis
    A retrospective activity where the team first defines a state they want to achieve and then breaks into groups to identify factors that may either restrain or drive the desired change
  73. "INVEST"
    • The acronym "INVEST" represents the qualities of a good user story:
    • Independent
    • Negotiable
    • Valuable
    • Estimatable
    • Sized
    • Appropriately
    • Testable
  74. Fixed, Firm, Flexible
    In a tradeoff matrix, agile project constraints are categorized as Fixed, Firm, or Flexible, with only one constraint (i.e., time, scope, or cost) being Fixed
  75. Abnormally Terminated Sprint
    A scrum iteration that is discontinued, either because the team cannot meet the sprint goal or because organizational priorities change
  76. "Done-done"
    An agile state of being when the code is complete, tested, and bug free and can be released to the customer
  77. Buffer Sprint
    A sprint in the last release of a project that allows the scrum team to address some final finishing features
  78. Servant Leader
    A project leader or facilitator who makes his highest priority that of serving the needs of the team
  79. Facilitating
    Supporting the team's self-organization and enhancing their ability to deliver real business value to the customer
  80. "CRACK"
    • The acronym "CRACK" describes an effective agile product owner:
    • Committed
    • Responsible
    • Authorized
    • Collaborative
    • Knowledgeable
  81. BART Analysis
    • When performing a BART analysis, agile coaches focus on the impact of four dimensions on team dynamics:
    • Boundary
    • Authority
    • Role
    • Task
  82. Invitation Opening
    A non-leading, open-ended question ("What did you notice during the stand-up meeting this morning?") that gives team members the opportunity to provide thoughtful response
  83. Minimum Markable Features (MMF)
    The smallest amount of functionality that makes sense to deliver to market
  84. Optimizing the Whole
    A Lean principle that emphasizes continuous improvement by addressing whole entities or processes rather than individual problems or symptoms
  85. Portfolio Management
    An organizational approach of selecting the most important products to create and enhance
  86. Working Software
    In Lean thinking, working software in the most valuable indicator of project status
  87. Scrum #
    A variation of scrum, which is an enhancement that results from embedding scrum with Lean thinking
  88. Iteration 0
    A planning iteration used for accomplishing technical setup, establishing agile methods and roles, and creating a product vision
  89. Organic Risk Management
    Risk management resulting inherently from using agile practices such as release planning, short iterations, and the daily stand-up meeting, where obstacles are addressed daily
  90. Overt Risk Management
    Specific risk management strategies employed to identify, track, and mitigate project risk, such as constructing and maintaining a risk board
  91. Backlog
    A list of capabilities, features, and stores that the product team has identified for use both in both release and iteration planning
  92. Predictive Release Planning
    A release planning method in which the entire plan is created in advance and which tends to work best in environments that are low in flux
  93. Discipline
    The level of adherence (on a high/low continuum) to the agile methodology's prescribed structure and processes
  94. Flux
    The level of change (on a high/low continuum) that is occurring with the project requirements or code
  95. Responsibility, Respect, Fairness, and Honesty
    The four hallmarks of the PMP Code of Ethics and Professional Responsibility; adhering to them builds trust
  96. Responsibility
    Taking ownership of one's decisions, actions, and related outcomes; one of the four hallmarks of the PMP Code or Ethics and Professional Responsibility
  97. "Caves and Commons" Area
    The team is located in a "commons" area to foster osmotic communication but members may retreat to a private "caves" area when they need quiet or personal space
  98. Certified Scrum Master (CSM)
    One of the most widely recognized agile certifications; the CSM is issued by the Scrum Alliance
  99. Sprint
    An iteration; the term sprint is specific to the scrum world
  100. Deferring Commitment
    Decisions are made at the right time; synonymous with "last responsible moment"
  101. Iterative Development
    The agile practice of delivering increments of the solution early and often
  102. Product Owner
    In scrum, the "voice of the customer" representing stakeholders and the business, who sets the priorities of the deliverables
  103. Agile Manifesto Values
    • Individuals and Interactions over Processes and Tools
    • Working Software over Comprehensive Documentation
    • Customer Collaboration over Contract Negotiation
    • Responding to Change over Following a Plan
  104. Sustainable Pace
    Allowing agile teams to work at a pace that can be sustained for the long term; this practice avoids team burnout and improves quality and team morale
  105. Ideal Scrum Team Size
    5 to 9 members (i.e., 7 + or - 2)
  106. Artifacts
    • Deliverables or work products resulting from the agile process. Examples include:
    • Vision statement
    • Flexibility matrix
    • Product backlog
    • User stories
    • Team agreements
  107. Elevator Statement
    A brief, structured product vision statement that gives the team the ability to explain the project concisely to someone "in an elevator"
  108. "Pigs and Chickens"
    "Pigs" are the scrum team, who are committed to success; all others with a vested interest but who do not participate are "chickens"
  109. Heavyweight Team
    An agile team focused solely on new development and not supporting existing operations; often used on pilot projects or when on boarding agile methods
  110. Hybrid Sprint
    A sprint (iteration) where a significant part is reserved for non-development work (e.g., defect repair, unplanned items, etc.)
  111. Defect Repair Sprint
    A sprint (iteration) devoted exclusively to fixing product defects (e.g., software bugs)
  112. 4 Types of Resistors to Agile Onboarding
    • Diehards (Passive; Like Status Quo)
    • Followers (Active; Like Status Quo)
    • Saboteurs (Passive; Don't Like Agile)
    • Skeptics (Active; Don't Like Agile)
  113. Extreme Programming (XP) Quality
    All checked-in code must pass unit tests at 100% at all times
  114. Software Development is What Type of Game?
    Goal-seeking and cooperative
  115. 3 Levels of Agile Planning
    • Release planning
    • Iteration planning
    • Daily planning
  116. Features that Should be Developed First
    High-value, high-risk features deliver the most value and eliminates risks
  117. Structure of an Agile Retrospective
    • The structure of an agile retrospective is:
    • Setting the stage
    • Gathering data
    • Generating insights
    • Deciding what to do
    • Closing
  118. The Most Efficient and Effective Method of Communication for Agile Teams
    Face-to-face (F2F) conversation
  119. Retained Revenue
    Revenue an organization will lose if the project or theme is not developed
  120. Incremental Revenue
    Additional revenue that may be obtained from existing customers
  121. Discounting
    The process of moving future amounts back into their present value
  122. Reciprocal Commitment
    The team commits delivering specified functionality and the business commits to not charging priorities during the sprint
  123. When May an Agile Team Intitate a "Code Freeze?"
    Only during an ongoing iteration, to prevent unapproved scope changes
  124. Fist of Five
    "Fist of five" is an agile consensus-building activity; during team votes showing more fingers (1 to 5) demonstrates increased agreement with the question posed, with five fingers meaning, "Strongly agree"
  125. Agile Advocates Working on How Many Projects at a Time?
    One, which improves focus and team productivity
  126. Visual Control
    In Lean, a visual tool (e.g., Kanban signal card) for controlling an activity or process
  127. Per Lean Principles, What are the Two Biggest Wastes in Software Development?
    • Delays
    • Building what is not needed
  128. Agile Coaching Occurs at These Two Levels
    • Individual
    • Team
  129. The Japanses Concept "Shu Ha Ri," Which is Used as a Model for Mastering Agile, Means
    • Follow the rule
    • Break the rule
    • Be the rule
  130. Linear Feature
    Linear features are so named because customer satisfaction is correlated linearly with the quantity of the feature
  131. When Should a User Stroy be Split?
    When the user story is too big to fit within a single iteration
  132. Release Planning
    The process of creating a very high-level plan that covers a periods longer than an iteration
  133. Date-driven Project
    One that must be released by a certain date but for which the feature set is negotiable
  134. Iteration Review Meeting
    Meeting where new functionality and capabilities that were added during the iteration are demonstrated to stakeholders
  135. Velocity-driven Iteration Planning
    The team estimates how many story points should be planned into the current iteration base on its actual velocity during recent iterations
  136. Ideal Day
    The amount of time per day that a team would spend on a project if working full speed without any interruptions, vacations, or other competition for their time
  137. Buffer
    A margin for error around an estimate, used where there is significant uncertianty
  138. Two Types of Buffers
    • Features buffers
    • Schedule buffers
  139. Continue-or-Cancel Clauses
    Contract stipulations where the customer may cancel if the agile seller fails to deliver and the agile seller may cancel if the customer does not provide input and priorities
  140. The Three Phases of Dynamic Systems Development Method (DSDM)
    • Pre-project
    • Project Lifecycle
    • Post-Project
  141. In Crystal, What are the Name Color Schemes?
    • Clear
    • Yellow
    • Orange
    • Red
    • Maroon
  142. In Crystal, What do the Color Schemes Represent?
    Going from lighter (Clear) to darker (Maroon) indicates increased "heaviness" in terms of the number of people involved, criticality, and project-level priorities
  143. Seven Principles of Lean
    • Elminating waste
    • Amplifying learning
    • Deciding as late as possible
    • Delivering as fast as possible
    • Empowering the team
    • Building integrity in
    • Seeing the whole
  144. Open Space Meeting
    A self-organized meeting where the participants set the topic and agenda, typically to solve a problem
  145. Inputs to Agile Release Planning
    • Prioritized, estimated product backlog
    • Velocity measurement (or estimate)
    • Product vision
  146. The Main Output of Agile Release Planning
    Release plan
  147. Name Two Exercises for Refining the Product Vision
    • Design the box that would carry the product
    • Write an elevator statment
  148. Team Working Agreements
    Standards that the agile team defines for how it will work
  149. Planning Poker
    A consensus-based game that employs the Delphi method; team members individually estimate user stories through use of numbered cards, followed by discussion, until consensus is achieved
  150. Acceptance Criteria
    Measurable terms defining how a user story can satisfy customer expectations
  151. Identify the 3 Essentail Roles for Any Scrum Project
    • Product Owner
    • Scrum Master
    • Team
  152. Analysis Paralysis
    The fear of moving forward until the project's agile models are perfect