I85PREP
⌘ K
CASM study materials
CASM study resources

CASM practice questions

One question at a time. Build your CASM understanding.

First 50 of 200 questions. Each one lists the choices, the correct answer, and an explanation. The checker at the top of this page saves progress in this browser when it is available.

Continue in the practice tool above to load more questions, 50 at a time.

Question 1Agile and Lean Service Management Fundamentals

In Agile service management, what is the primary purpose of a service value stream map?

  1. To record the contractual penalties for missing service targets
  2. To visualize the sequence of activities that deliver value to the customer and expose delays Correct answer.
  3. To document the organizational chart of the service provider
  4. To list every configuration item in the configuration management database

Explanation

A value stream map traces the flow of work from demand to value delivery, making wait states and handoffs visible. Teams use it to find waste and shorten lead time, not to document hierarchy or contracts.

Question 2Agile and Lean Service Management Fundamentals

Which statement best describes the role of a service owner in an Agile service management organization?

  1. They own the budget for all services in the portfolio
  2. They are accountable for the end-to-end value and performance of a specific service Correct answer.
  3. They manage the daily task assignments of the development team
  4. They approve every code commit before release

Explanation

The service owner is accountable for a single service across its lifecycle, including its value and performance for customers. This accountability spans teams, so it differs from team-level task management or portfolio budgeting.

Question 3Agile and Lean Service Management Fundamentals

A team wants to limit the amount of work in progress across its service desk. Which Lean practice directly addresses this goal?

  1. Setting a work-in-progress limit for each stage of the flow Correct answer.
  2. Conducting a root cause analysis for every ticket
  3. Increasing the batch size of resolved incidents
  4. Adding a second approval step for change requests

Explanation

Work-in-progress limits cap how many items can be active at once, which reduces multitasking and shortens cycle time. This is a core Lean and Kanban practice for improving flow.

Question 4Agile and Lean Service Management Fundamentals

Which metric is a Lean measure of how long a service request takes from the customer's initial request to completion?

  1. Defect density
  2. Utilization rate
  3. Lead time Correct answer.
  4. Velocity

Explanation

Lead time measures elapsed time from the customer's request until delivery, including all waiting. It reflects the customer's experience of speed rather than internal effort.

Question 5Agile and Lean Service Management Fundamentals

In the Agile manifesto values, how is working service or software valued relative to comprehensive documentation?

  1. Documentation is required before any working service is released
  2. Documentation is valued more highly than working service
  3. Working service is valued more highly than comprehensive documentation Correct answer.
  4. Both are valued equally with no preference

Explanation

The manifesto states a preference for working software over comprehensive documentation while still valuing documentation. The point is to prioritize demonstrable value without banning documentation.

Question 6Agile and Lean Service Management Fundamentals

What does the Lean concept of 'pull' mean in a service management context?

  1. Customers are asked to resubmit requests weekly
  2. Managers assign priorities to each queue every morning
  3. Work is pushed to teams as soon as it is requested
  4. Work is started only when downstream capacity is available to handle it Correct answer.

Explanation

Pull systems release work based on downstream capacity rather than pushing it into queues. This prevents overload and keeps flow balanced with actual capacity.

Question 7Agile and Lean Service Management Fundamentals

Which practice is central to a blameless post-incident review in Agile service management?

  1. Identifying which individual caused the failure
  2. Suppressing details that could embarrass the team
  3. Assigning disciplinary action to the on-call engineer
  4. Focusing on systemic causes and improving the system Correct answer.

Explanation

Blameless reviews assume people act reasonably given the information they had and look for systemic contributing factors. The goal is learning and systemic improvement, not punishment.

Question 8Agile and Lean Service Management Fundamentals

A service team notices that incidents wait an average of three days for a specialist review before work begins. Which Lean waste is most directly illustrated?

  1. Inventory of finished goods
  2. Motion
  3. Overproduction
  4. Waiting Correct answer.

Explanation

Idle time while work sits in a queue awaiting the next step is the waste of waiting. It is one of the classic Lean wastes and a frequent target in service value streams.

Question 9Agile and Lean Service Management Fundamentals

A team uses a Kanban board with columns for triage, work in progress, and verification. Tickets keep piling up in verification. What is the most appropriate Lean response?

  1. Increase the number of tickets started in triage
  2. Ask customers to stop submitting requests
  3. Add a work-in-progress limit to the verification column and address the constraint Correct answer.
  4. Remove the verification column to eliminate the queue

Explanation

A growing queue signals a constraint at that stage, so limiting upstream intake and relieving the bottleneck restores flow. WIP limits make the constraint visible and prevent further buildup.

Question 10Agile and Lean Service Management Fundamentals

Which situation best demonstrates a cross-functional service team as described in Agile service management?

  1. A team that escalates every decision to a steering committee
  2. A team that consists only of developers and excludes operations staff
  3. A team that hands off all operational work to a separate support department
  4. A team that includes the skills needed to design, build, run, and support a service end to end Correct answer.

Explanation

Cross-functional teams contain the mix of skills required to deliver a service without repeated handoffs. This reduces delays and gives the team end-to-end accountability.

Question 11Agile and Lean Service Management Fundamentals

A service manager wants to reduce batch size for change deployments. Which outcome should they expect?

  1. Longer feedback cycles and larger risk per release
  2. Elimination of the need for testing
  3. Fewer deployments with higher failure impact
  4. Faster feedback and lower risk per release Correct answer.

Explanation

Smaller batches shorten the time to get feedback and reduce the blast radius when something fails. This is a core Lean and continuous delivery principle.

Question 12Agile and Lean Service Management Fundamentals

Which pair of metrics best helps a team understand flow efficiency?

  1. Active time versus total lead time Correct answer.
  2. Number of employees and office space
  3. Budget spent and invoice count
  4. Utilization and overtime hours

Explanation

Flow efficiency compares the time work is actively being worked on with the total elapsed lead time. A low ratio reveals large amounts of waiting in the process.

Question 13Agile and Lean Service Management Fundamentals

In Agile service management, what is the main purpose of defining a minimum viable service?

  1. To release the smallest version that delivers real value and enables fast learning Correct answer.
  2. To deliver every planned feature in the first release
  3. To postpone customer feedback until the final version
  4. To reduce the quality of the service to save cost

Explanation

A minimum viable service delivers enough value to be usable while allowing the team to learn from real feedback. It balances value delivery with early validation of assumptions.

Question 14Agile and Lean Service Management Fundamentals

A team claims to be Agile but releases once a year after a long freeze. Which principle from the Agile manifesto does this most directly conflict with?

  1. Deliver working service frequently, with a preference for shorter timescales Correct answer.
  2. Business people and developers must work together daily
  3. The best architectures emerge from self-organizing teams
  4. Simplicity is essential

Explanation

The manifesto explicitly favors frequent delivery of working software on short timescales. A yearly release with a long freeze contradicts that principle directly.

Question 15Agile and Lean Service Management Fundamentals

Which approach best reflects Lean thinking when a service process has an approval step that adds no customer value?

  1. Eliminate or streamline the step after confirming why it exists Correct answer.
  2. Add a second approval step to improve control
  3. Automate the step without questioning its purpose
  4. Keep the step because it has always existed

Explanation

Lean thinking challenges non-value-adding steps and removes them where safe, after understanding their original purpose. Automating waste without questioning it simply makes the waste faster.

Question 16Agile and Lean Service Management Fundamentals

A team tracks its cumulative flow diagram and sees the band for 'in progress' widening steadily. What does this most likely indicate?

  1. The team has too few requests
  2. Work in progress is accumulating and flow is degrading Correct answer.
  3. Defects are being eliminated
  4. Cycle time is decreasing

Explanation

A widening in-progress band on a cumulative flow diagram shows more items entering that stage than leaving it. That accumulation signals rising WIP and longer cycle times.

Question 17Agile and Lean Service Management Fundamentals

Which statement correctly distinguishes a service level objective from a service level agreement?

  1. An agreement is set by the engineering team, while an objective is set by the customer
  2. An objective is an internal target, while an agreement is a commitment made to the customer Correct answer.
  3. An objective is a legal contract, while an agreement is an informal goal
  4. Both terms mean exactly the same thing in all contexts

Explanation

Service level objectives are internal targets used to manage performance, while agreements are the commitments formally made to customers. Objectives usually sit at or above the agreed thresholds to provide a safety margin.

Question 18Agile and Lean Service Management Fundamentals

A team wants to adopt a 'stop the line' practice for service quality. What does this mean in practice?

  1. Quality checks are deferred until after the release
  2. Only senior managers may pause a release
  3. The line is stopped at the end of each sprint regardless of quality
  4. Anyone can halt work when a serious quality problem is detected so it can be fixed Correct answer.

Explanation

Stop-the-line authority empowers any team member to halt work when a defect or risk appears, preventing problems from flowing downstream. It reflects Lean's emphasis on building quality in rather than inspecting it later.

Question 19Agile and Lean Service Management Fundamentals

Which combination best describes how Agile and Lean principles complement each other in service management?

  1. Agile emphasizes documentation, while Lean emphasizes hierarchy
  2. Agile emphasizes iterative delivery and feedback, while Lean emphasizes flow and waste reduction Correct answer.
  3. Agile emphasizes command and control, while Lean emphasizes fixed roles
  4. Agile emphasizes annual planning, while Lean emphasizes individual bonuses

Explanation

Agile contributes short feedback loops and adaptive delivery, while Lean contributes flow, pull, and waste elimination. Together they support continuous improvement of services.

Question 20Agile and Lean Service Management Fundamentals

A service desk measures customer satisfaction after each resolved ticket and reviews trends weekly. Which Agile practice does this most closely reflect?

  1. Annual performance appraisal
  2. Iterative inspection and adaptation based on feedback Correct answer.
  3. Waterfall stage-gate approval
  4. Change advisory board scheduling

Explanation

Collecting feedback frequently and adjusting based on it is the essence of iterative inspection and adaptation. Weekly trend reviews create short loops for improvement.

Question 21Agile and Lean Service Management Fundamentals

In a complex service environment, why do Agile practitioners favor empirical process control over detailed predictive planning?

  1. Because empirical control removes the need for measurement
  2. Because predictive planning is illegal in service management
  3. Because planning is never useful in any context
  4. Because outcomes are uncertain and must be adjusted based on observed results Correct answer.

Explanation

Empirical control relies on transparency, inspection, and adaptation when cause and effect are not fully known. In complex work, observed results inform adjustments that a fixed plan cannot anticipate.

Question 22Agile and Lean Service Management Fundamentals

A team reduces its work-in-progress limit and finds cycle time drops but throughput briefly falls. How should a Lean-informed manager interpret this?

  1. A short throughput dip can accompany flow improvement, so the team should observe the trend before judging Correct answer.
  2. Throughput and cycle time are unrelated, so the dip is meaningless
  3. The change has failed and the limit should be removed immediately
  4. The team should raise the limit far above the previous level

Explanation

Tightening WIP limits can cause a transient throughput dip while queues drain and the system stabilizes. Flow metrics should be observed over several cycles before concluding the change failed.

Question 23Agile and Lean Service Management Fundamentals

A service team wants to shorten lead time without adding staff. Which analysis is most likely to reveal the greatest opportunity?

  1. Counting the number of meetings held each month
  2. Reviewing the organizational chart for reporting lines
  3. Measuring the ratio of value-adding time to waiting time across the value stream Correct answer.
  4. Comparing office locations of team members

Explanation

Most lead time in service processes is waiting rather than active work, so quantifying that ratio exposes where to attack delay. Reducing wait states can shorten lead time without additional capacity.

Question 24Agile and Lean Service Management Fundamentals

A team automates a manual approval step that customers never valued. What is the most accurate Lean assessment of this action?

  1. It may make a non-value-adding step faster, but eliminating the step would yield greater benefit Correct answer.
  2. It converts the step into a value-adding activity
  3. It violates Lean principles because automation is discouraged
  4. It is a clear improvement because automation always adds value

Explanation

Automating waste speeds up a step that still consumes resources and adds no customer value. Lean favors removing the step entirely where possible, making automation a second-best option.

Question 25The Agile Service Management Journey and Organizational Readiness

In the CASM journey, which activity most directly establishes the baseline against which later Agile Service Management improvements are measured?

  1. Appointing a product owner for the service desk tool
  2. Assessing current service management practices and maturity Correct answer.
  3. Drafting the annual IT budget
  4. Selecting a new ITSM platform vendor

Explanation

The journey begins with understanding where the organization stands, so a structured assessment of current practices, culture, and maturity creates the baseline. Without that baseline, later improvements cannot be evidenced or prioritized. Tool selection and budgeting are downstream decisions that depend on assessment results.

Question 26The Agile Service Management Journey and Organizational Readiness

A leadership team wants to adopt Agile Service Management but has not yet agreed on what value the change should deliver. Which readiness action should come first?

  1. Define a shared vision and expected outcomes for the change Correct answer.
  2. Run a pilot team to prove the concept quickly
  3. Recruit additional service desk analysts
  4. Purchase collaboration software licenses

Explanation

Readiness depends on a clear, shared sense of purpose: what problem the change solves and what outcomes matter. A pilot without agreed outcomes cannot be evaluated meaningfully. Tools and staffing decisions should follow from the vision rather than precede it.

Question 27The Agile Service Management Journey and Organizational Readiness

Which pairing best reflects the shift from traditional process ownership to Agile Service Management ways of working?

  1. From process compliance to customer value and flow Correct answer.
  2. From cross-functional teams to specialist silos
  3. From value-stream teams to departmental handoffs
  4. From outcome-focused teams to procedure compliance

Explanation

Agile Service Management reframes service management around customer value and the flow of work through value streams. Compliance with procedures remains relevant but is not the organizing principle. The other pairings describe the traditional model rather than the shift.

Question 28The Agile Service Management Journey and Organizational Readiness

An organization maps how a customer request moves from submission to fulfillment, noting wait times and handoffs. Which Agile Service Management practice is being applied?

  1. Root cause analysis
  2. Capacity forecasting
  3. Value stream mapping Correct answer.
  4. Configuration auditing

Explanation

Value stream mapping visualizes the end-to-end flow of work, including delays and handoffs between teams. Its purpose is to expose where value is added and where waste occurs. The other techniques address causes, capacity, or configuration accuracy rather than flow.

Question 29The Agile Service Management Journey and Organizational Readiness

Why does psychological safety matter when an organization begins its Agile Service Management journey?

  1. It encourages people to surface problems and experiment without fear of blame Correct answer.
  2. It allows teams to skip retrospectives when deadlines are tight
  3. It guarantees that every change initiative will succeed
  4. It removes the need for documented service management practices

Explanation

Transformation requires honest reporting of what is not working, and people only do that when they feel safe from blame. Psychological safety supports learning and experimentation, which underpin continuous improvement. It is a cultural enabler, not a guarantee of success or a reason to abandon practices.

Question 30The Agile Service Management Journey and Organizational Readiness

Which statement best describes the role of a sponsor in an Agile Service Management transformation?

  1. Approving every team-level retrospective action
  2. Performing daily operational incident triage
  3. Actively removing organizational impediments and championing the change Correct answer.
  4. Writing user stories for service teams

Explanation

Sponsorship is most effective when leaders visibly back the change and clear systemic blockers that teams cannot resolve alone. This differs from day-to-day delivery work, which belongs to the teams. Micromanaging team ceremonies or operations undermines the empowerment the change depends on.

Question 31The Agile Service Management Journey and Organizational Readiness

A service team adopts short iterations but still receives all requirements from a central process office that reviews and approves each item. Which readiness gap does this illustrate?

  1. Lack of monitoring for service availability
  2. Governance that constrains team autonomy and flow Correct answer.
  3. Absence of a formal incident management process
  4. Insufficient tooling for continuous integration

Explanation

Iterations cannot deliver their benefit if decision rights remain centralized and every item requires external approval, because that creates queues and limits responsiveness. The gap is in governance and empowerment rather than technology or operations. Agile Service Management requires governance that enables flow while retaining appropriate oversight.

Question 32The Agile Service Management Journey and Organizational Readiness

During a readiness assessment, leaders discover that teams are measured mainly on individual utilization. What is the most likely consequence for Agile Service Management adoption?

  1. Retrospectives will become unnecessary
  2. Teams will optimize local busyness rather than end-to-end flow Correct answer.
  3. Service quality will improve because everyone stays occupied
  4. Handoffs between teams will decrease automatically

Explanation

Utilization metrics reward keeping individuals busy, which encourages local optimization and work-in-progress accumulation rather than smooth delivery of value. Flow-based measures such as lead time and throughput align better with Agile Service Management. The other outcomes do not follow from a utilization focus.

Question 33The Agile Service Management Journey and Organizational Readiness

An organization wants to sequence its journey. It has executive backing and a shared vision but no shared understanding of current practice. What is the most sensible next step?

  1. Conduct a current-state assessment across key value streams Correct answer.
  2. Scale the model to every team simultaneously
  3. Outsource the service desk to accelerate change
  4. Retire existing process documentation immediately

Explanation

With sponsorship and vision in place, the next logical step is understanding the current state so improvements can be targeted and sequenced. Scaling before diagnosis spreads unproven practices. Removing documentation or outsourcing are separate decisions that should follow from assessment findings.

Question 34The Agile Service Management Journey and Organizational Readiness

Which indicator most strongly suggests an organization is ready to expand Agile Service Management beyond its first pilot team?

  1. The pilot shows improved flow metrics and other teams request to join Correct answer.
  2. The tooling vendor has delivered additional licenses
  3. The pilot team has adopted the new meeting calendar
  4. Senior leaders have approved a larger budget

Explanation

Readiness to scale is evidenced by demonstrated improvement plus organic demand from other teams, which signals credibility and pull. Calendar compliance or purchased capacity are inputs rather than proof of value. Budget approval alone does not show that practices work.

Question 35The Agile Service Management Journey and Organizational Readiness

A service manager worries that Agile practices will erode control over regulatory obligations. Which response best reflects Agile Service Management guidance?

  1. Controls can be embedded as automated guardrails within team workflows Correct answer.
  2. Compliance must remain a separate manual approval stage for every change
  3. Regulatory controls should be suspended during transformation
  4. Teams should decide individually which regulations apply to them

Explanation

Agile Service Management treats necessary controls as design constraints that can be built into workflows, for example through automated policy checks and defined acceptance criteria. This preserves compliance while avoiding queues. Suspending controls or decentralizing interpretation of regulations creates risk.

Question 36The Agile Service Management Journey and Organizational Readiness

Which set of measures best aligns with Agile Service Management principles?

  1. Individual utilization, hours logged, and ticket counts per analyst
  2. Frequency of management status meetings held
  3. Lead time, throughput, and customer satisfaction Correct answer.
  4. Number of process documents approved per quarter

Explanation

Flow and outcome measures such as lead time, throughput, and satisfaction reflect how well value is delivered to customers. Activity and output counts can be gamed and encourage local optimization. Document counts and meeting frequency measure effort rather than results.

Question 37The Agile Service Management Journey and Organizational Readiness

A transformation stalls because middle managers fear losing authority. Which action best addresses this readiness barrier?

  1. Bypass managers and communicate directly with frontline staff
  2. Announce that manager roles will be eliminated after the pilot
  3. Engage managers in redesigning decision rights and clarify their new role Correct answer.
  4. Increase reporting requirements so managers retain visibility

Explanation

Resistance from middle management is usually rooted in uncertainty about role and influence. Involving them in redesigning decision rights and defining their contribution as enablers of flow converts them into stakeholders. Bypassing or threatening them, or adding reporting, reinforces the fear.

Question 38The Agile Service Management Journey and Organizational Readiness

Why is a service-oriented value stream perspective important when forming Agile teams for service management?

  1. It ensures teams are organized around delivering end-to-end customer value Correct answer.
  2. It removes the need for service level agreements
  3. It allows teams to ignore dependencies on other services
  4. It guarantees that every team has identical skills

Explanation

Organizing around value streams aligns teams with the complete flow of service to the customer, reducing handoffs and clarifying accountability. Teams may still have varied skills, and service level agreements and dependencies remain relevant. The perspective changes alignment, not the need for agreements or coordination.

Question 39The Agile Service Management Journey and Organizational Readiness

An organization defines success for its transformation purely as completing a fixed training plan by year end. What is the main weakness of this readiness measure?

  1. Training cannot support Agile Service Management adoption
  2. Training plans are always too expensive to complete
  3. It measures activity rather than changed capability or outcomes Correct answer.
  4. It requires too much involvement from senior leadership

Explanation

Completing training is an output, not evidence that behavior, flow, or customer outcomes have changed. Readiness should be judged by observable capability and results, with training as one enabler. Cost, relevance of training, and leadership involvement are separate considerations.

Question 40The Agile Service Management Journey and Organizational Readiness

A pilot team reports faster delivery, but customer complaints about service quality have increased. How should the organization interpret this result?

  1. The pilot is a clear success because speed improved
  2. The pilot should be scaled immediately to spread the benefit
  3. The complaints should be excluded because they come from outside the pilot scope
  4. The pilot reveals a trade-off between speed and quality that must be investigated before scaling Correct answer.

Explanation

Agile Service Management aims at valuable flow, so faster delivery accompanied by worse quality signals an unresolved constraint, such as insufficient testing or skipped reviews. Scaling before understanding the cause would spread the defect. Excluding relevant customer feedback would hide the very outcome that matters.

Question 41The Agile Service Management Journey and Organizational Readiness

An enterprise has strong executive sponsorship and mature tooling but its teams operate in silos with reward systems tied to departmental targets. Which conclusion about readiness is most defensible?

  1. Readiness is irrelevant because executive support guarantees adoption
  2. The organization is ready because sponsorship and tooling are the decisive factors
  3. Readiness is blocked by structural and incentive misalignment that must be addressed Correct answer.
  4. Readiness can be achieved by purchasing additional tooling

Explanation

Sponsorship and tooling are enabling conditions, but siloed structures and departmental incentives work against end-to-end flow and collaboration. These structural and reward issues must be addressed for the change to take hold. More tooling or sponsorship alone cannot overcome misaligned incentives.

Question 42The Agile Service Management Journey and Organizational Readiness

Leaders want a single maturity score to decide whether to proceed. Why is a purely numerical maturity rating an insufficient basis for the decision?

  1. Maturity assessments require external consultants to be valid
  2. A score hides the specific capability gaps and cultural conditions that determine feasibility Correct answer.
  3. Maturity models cannot be applied to service management
  4. Numerical ratings are always inaccurate by more than ten percent

Explanation

A composite score compresses many dimensions into one figure, obscuring which capabilities are strong, which are weak, and whether cultural conditions support change. Decisions need the underlying evidence, not only the aggregate. Maturity models are applicable to service management, and external consultants are not mandatory.

Question 43The Agile Service Management Journey and Organizational Readiness

A global organization has some regions with mature DevOps practices and others still relying on manual change approval. What sequencing approach best fits Agile Service Management readiness principles?

  1. Tailor the pace and starting point to each region's context while sharing a common vision Correct answer.
  2. Let each region define its own unrelated objectives
  3. Apply one uniform adoption plan to all regions at the same pace
  4. Delay the entire program until every region reaches the same maturity

Explanation

Readiness varies by context, so a common vision with locally adapted sequencing respects differing starting points while preserving coherence. Uniform pace ignores real constraints, and waiting for universal maturity stalls progress indefinitely. Fully independent objectives would fragment the effort.

Question 44The Agile Service Management Journey and Organizational Readiness

Which practice best builds organizational readiness by making improvement visible and reinforcing desired behaviors early in the journey?

  1. Requiring every team to submit weekly status reports to leadership
  2. Running short improvement cycles with visible results and shared learning Correct answer.
  3. Restricting communication until the program is fully mature
  4. Publishing a comprehensive policy manual before any change begins

Explanation

Short improvement cycles generate early evidence of benefit and create opportunities for shared learning, which builds confidence and momentum. Visible results also reinforce the behaviors the change depends on. Large upfront manuals, communication blackouts, and heavy reporting do not build readiness.

Question 45Service Design and Agile Requirements Definition

In a service design effort, a team maps every interaction a customer has with the organization across channels and over time. Which artifact are they most likely producing?

  1. A burn-down chart
  2. A customer journey map Correct answer.
  3. A product backlog
  4. A sprint retrospective

Explanation

A customer journey map visualizes the end-to-end experience across touchpoints and time, exposing pain points and moments that matter. Backlogs, burn-down charts, and retrospectives are agile delivery tools, not experience-mapping artifacts.

Question 46Service Design and Agile Requirements Definition

A service blueprint differs from a customer journey map mainly because it adds which element?

  1. Frontstage and backstage layers plus supporting processes Correct answer.
  2. A prioritized list of user stories
  3. A definition of done for the team
  4. Estimated story points for each step

Explanation

Service blueprints extend journey thinking by exposing frontstage actions, backstage actions, and supporting processes beneath the line of visibility. This makes dependencies between customer experience and internal operations explicit.

Question 47Service Design and Agile Requirements Definition

Which statement best captures the purpose of a persona in service design and requirements work?

  1. It lists every acceptance criterion for a release
  2. It replaces the need for user research once written
  3. It records the technical architecture of the service platform
  4. It summarizes evidence-based user goals and behaviors to guide design decisions Correct answer.

Explanation

Personas synthesize research about user goals, behaviors, and context so teams can make defensible design trade-offs. They are communication and decision aids grounded in evidence, not substitutes for architecture or acceptance criteria.

Question 48Service Design and Agile Requirements Definition

A team writes a user story as: 'As a returning customer, I want my saved payment method pre-selected so that checkout is faster.' Which part of this story expresses the benefit or rationale?

  1. So that checkout is faster Correct answer.
  2. As a returning customer
  3. The story title only
  4. I want my saved payment method pre-selected

Explanation

The 'so that' clause states the value or motivation behind the story, helping the team judge whether a solution actually delivers the intended outcome. The role and the action are captured by the other clauses.

Question 49Service Design and Agile Requirements Definition

In agile requirements, what does the INVEST acronym primarily help a team evaluate?

  1. The quality of an individual backlog item Correct answer.
  2. The size of the operations budget
  3. The accuracy of a release forecast
  4. The maturity of the delivery process

Explanation

INVEST describes characteristics of a well-formed backlog item: independent, negotiable, valuable, estimable, small, and testable. It is a checklist for item quality rather than for process maturity or forecasting.

Question 50Service Design and Agile Requirements Definition

A product owner wants to express a large, uncertain initiative without committing to detailed requirements. Which backlog construct fits best?

  1. A spike
  2. A task
  3. An epic Correct answer.
  4. A bug report

Explanation

An epic is a large body of work that can be decomposed into smaller stories as understanding grows. It supports deferring detail while keeping the initiative visible in the backlog.