Certified Associate in Project Management (CAPM) Agile Frameworks and Methodologies Flashcards

24 sample cards from the Agile Frameworks and Methodologies deck

Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.

1. What does the INVEST acronym describe for a good user story?

   Independent, Negotiable, Valuable, Estimable, Small, and Testable.

2. What is backlog refinement (grooming)?

   The ongoing activity of adding detail, estimates, and order to Product Backlog items: breaking down large items, clarifying and adding acceptance criteria, re-estimating, and re-prioritizing so items are ready for future Sprints.

3. Name common backlog prioritization techniques.

   MoSCoW (Must, Should, Could, Won't have), Kano model, value vs. effort/cost-benefit ranking, WSJF (Weighted Shortest Job First), and the 100-point (cumulative voting) method.

4. What does MoSCoW stand for in prioritization?

   Must have, Should have, Could have, and Won't have (this time). It classifies requirements by necessity to focus delivery on the highest-priority items.

5. Name common agile estimation techniques.

   Planning Poker, story points (relative sizing), T-shirt sizing (S/M/L/XL), affinity estimation/grouping, the Fibonacci-like scale (1,2,3,5,8,13,...), and wideband Delphi.

6. What are story points, and how do they differ from time-based estimates?

   Story points are a unitless, relative measure of the overall effort/size/complexity/uncertainty of a backlog item, compared to other items. Unlike hours, they are not tied to calendar time and account for difficulty and risk, not just duration.

7. What is velocity, and how is it used in planning?

   Velocity is the amount of work (typically story points) a team completes per iteration, averaged over recent Sprints. It is used to forecast how much the team can take on and how many iterations remain to finish the backlog.

8. Distinguish release planning from iteration (Sprint) planning.

   Release planning is longer-range: it maps which features/backlog items will be delivered across multiple iterations toward a release goal/date. Iteration planning is short-range: the team selects and plans the specific work for a single upcoming iteration.

9. What is an information radiator?

   A large, highly visible display of project information (e.g., task board, burndown/burnup chart, Kanban board, impediment list) placed where the team and stakeholders can see it, providing transparency without anyone having to ask.

10. What is the difference between a burndown chart and a burnup chart?

    A burndown chart shows remaining work (sloping down to zero over time). A burnup chart shows completed work rising toward a total scope line, making scope changes visible because the scope line can move.

11. Define the key flow metrics: cycle time, lead time, throughput, and WIP.

    Cycle time: time from when work starts to when it's done. Lead time: time from request/commitment to delivery. Throughput: number of items completed per unit of time. WIP: number of items in progress at a given time.

12. What is Little's Law and its formula?

    Little's Law relates flow metrics: Average Cycle Time = Average WIP / Average Throughput. It shows that reducing WIP (with throughput constant) reduces cycle time.

13. What is a cumulative flow diagram (CFD) used for?

    A CFD plots the number of work items in each workflow state over time as stacked bands. It visualizes WIP, approximate cycle time, throughput, and bottlenecks (a widening band signals a bottleneck/queue buildup).

14. What is continuous improvement (kaizen) in agile, and where is it primarily practiced?

    Kaizen is the philosophy of ongoing, incremental improvement. In agile it is primarily practiced through the Sprint Retrospective, where the team regularly inspects its process and commits to small, actionable improvements.

15. What is the purpose and typical format of a retrospective?

    To inspect and adapt the team's process. A common format: set the stage, gather data (what went well, what didn't), generate insights (why), decide what to do (actionable improvements), and close. The aim is concrete improvement actions for the next iteration.

16. What is the Definition of Ready (DoR)?

    A shared checklist of criteria a backlog item must meet before it can be pulled into a Sprint (e.g., clearly described, acceptance criteria defined, estimated, no blocking dependencies, small enough). It ensures items are well understood before work begins.

17. What is the Definition of Done (DoD)?

    A formal, shared checklist of quality criteria an Increment must satisfy to be considered complete and potentially releasable (e.g., coded, tested, integrated, documented, reviewed). In Scrum it is the commitment for the Increment and creates transparency.

18. Contrast the Definition of Ready with the Definition of Done.

    DoR is the entry criteria applied to a backlog item before work starts (it's ready to be worked). DoD is the exit criteria applied to completed work before it's considered done (it's truly finished and shippable).

19. What is technical debt?

    The implied future cost (extra rework) incurred by choosing an easy/quick solution now instead of a better approach that would take longer. Like financial debt, it accrues 'interest' as it makes future changes slower and riskier.

20. How do agile teams manage and reduce technical debt?

    By making it visible (a debt backlog/register), refactoring continuously, maintaining a strong Definition of Done, automated testing and continuous integration, and allocating capacity each iteration to pay it down before it compounds.

21. What is refactoring and why is it important for managing technical debt?

    Refactoring is improving the internal structure of code without changing its external behavior. It keeps the codebase clean and maintainable, steadily paying down technical debt so the system stays easy to change.

22. In agile estimation, why is Planning Poker effective?

    Team members estimate simultaneously using cards (often Fibonacci values), avoiding anchoring bias. Divergent estimates trigger discussion that surfaces hidden assumptions and shared understanding, producing a more accurate consensus estimate.

23. What is the role of the customer/product feedback in distinguishing agile from predictive approaches?

    Agile builds in frequent customer collaboration and feedback at the end of each iteration to inspect and adapt the product. Predictive gathers requirements up front and typically obtains customer feedback mainly at the end, limiting the chance to course-correct.

24. What is a self-organizing (self-managing) team, a key agile concept?

    A team that decides internally how to accomplish its work rather than being directed by others outside the team. They choose who does what and how, which increases ownership, motivation, and responsiveness.

What this deck covers

Agile Frameworks and Methodologies flashcards FAQ