Managing Products with Agility
PSPO II · 165 questions
- A city permitting portal Product Owner is pressed to promise a go-live date six months out, but discovery of permit types, integrations, and citizen journeys is still incomplete. What should the Product Owner do?
- Stakeholders for a municipal transit app demand a Gantt chart of every feature for the next twelve months. How should the Product Owner respond?
- A parks recreation booking product shows volatile throughput this quarter. Council wants a likely window for the next public release. What should the Product Owner use to brief them?
- Utilities billing stakeholders want a Sprint burn-down chart treated as a guarantee that a rate-change release will land on a published date. What should the Product Owner explain?
- A mayor asks when 100% of citizen requests will be online, but request types still vary widely and discovery is incomplete. How should the Product Owner reframe the forecast?
- A library digital-card team finished about half the stories hoped for this Sprint, but the Increment validated a risky assumption about cardholders proving identity online. What should the Product Owner do next with the release forecast?
- A county CRM for caseworkers has many half-finished initiatives in progress at once, and release forecasts keep slipping. What should the Product Owner do to improve forecast reliability?
- An emergency-alerts product faces a hard legal deadline for a required public notification path. What should the Product Owner do about scope and the forecast?
- Stakeholders for a municipal product want release planning to happen only in the annual budget workshop. What should the Product Owner insist on?
- A city product roadmap slide lists months of committed features. What should the Product Owner change?
- Developers on a public-works inspection app warn that capacity will drop after a holiday period. Stakeholders still want the original political date. What should the Product Owner do?
- A municipal marketing office published a release train of promises for a citizen app before the Product Backlog was refined. What should the Product Owner do about the forecast?
- Stakeholders ask when a citizen chatbot might deflect 30% of call-center volume. The Product Owner has historical throughput, not a detailed year-long design. How should the Product Owner forecast?
- Council wants a weekly percent-complete number for a multi-year permitting modernization whose remaining scope is still uncertain. What should the Product Owner offer instead?
- Two city departments each demand their unrelated must-have in the same Sprint for a shared municipal product. What should the Product Owner do?
- A vendor contract for a city services platform ties payment to a single big-bang go-live. What should the Product Owner advocate?
- After three Sprints of discovery on a building-permit workflow, several core assumptions failed. The original release narrative is now wrong. What should the Product Owner do?
- Stakeholders for a parks permitting product ask the Product Owner to commit to fixed scope, a fixed date, and a fixed cost together. What should the Product Owner do?
- A health-department vaccine-booking release is being forecast using only an optimistic best-case velocity. What should the Product Owner correct?
- A municipal Product Owner is mixing a citizen-outcome Product Goal with a hoped-for launch Friday. What distinction should the Product Owner make so the team can adapt scope?
- Stakeholders want every dataset on a municipal open-data portal in Q2, but demand is uneven and many datasets are still messy. How should the Product Owner forecast the release?
- A slow city identity vendor threatens the forecast for a citizen self-service portal. What should the Product Owner do?
- Sprint Review evidence for a building-permit product shows slower cycle time after a platform change. What should the Product Owner do about release expectations?
- City finance asks for a year-long committed feature list to lock next year's budget for a 311 request product. How should the Product Owner respond?
- A Product Owner is briefing transit leadership on when a rider-alerts Increment might be releasable. Remaining Product Backlog size is known, but several risky assumptions are still unvalidated. What should the briefing include?
- A school-enrollment product team is told to finish a separate 'release planning' phase and lock next year's dates before any Sprint starts. What should the Product Owner do?
- A public-health clinic scheduler has a Done Increment that already cuts no-show rates, two months before the city's published calendar go-live. What should the Product Owner do?
- In a council briefing on the building-permit portal, an official asks the Product Owner to 'commit the team' to a six-month forecast. How should the Product Owner respond?
- A city's 'digital transformation' slogan is being used as the Product Vision for a resident-services portal. What should the Product Owner put in a usable Product Vision?
- Building-permit stakeholders cannot agree whether the product is for inspectors or for residents applying online, and the Product Backlog is growing in both directions. What should the Product Owner do first?
- A parks recreation-booking Product Vision deck has not changed in three years, even though most reservations now start on phones and walk-up kiosk use has collapsed. What should the Product Owner do?
- City executives want the utilities-billing Product Vision to list every department's wish so everyone is represented. What should the Product Owner do?
- A transit-app manager tells the team the Sprint Goal is the Product Vision and both should be rewritten every Sprint. How should the Product Owner distinguish them?
- A town parking product team is drafting a Product Vision. Which statement should the Product Owner prefer?
- A new mayor wants the 311 Product Vision rewritten every week to match that week's press cycle. What should the Product Owner do?
- A library digital-card Product Vision is 'get a working card in the resident's hand the same day.' Marketing wants a social-feed feature that polls show people like but that does not advance same-day issuance. What should the Product Owner do?
- Cross-agency stakeholders for a public-benefits portal have never seen the Product Vision; it lives only on the Product Owner's private drive. What should the Product Owner do?
- A parks Product Goal for the next period is 'replace the reservation database,' while the Product Vision is 'families can book a picnic shelter in under five minutes.' What should the Product Owner do?
- Marketing drafts a transit Product Vision that names a container platform, a specific fare-engine vendor, and a mobile framework. What should the Product Owner do?
- A city 311 app and a separate 'report a problem' app publish overlapping visions, and residents do not know which to use. What should the Product Owner do?
- A county case-management Product Owner has been writing the Product Vision alone; caseworkers who will live in the product have not been asked. What should the Product Owner do?
- A public-health records compliance officer insists the Product Vision should be 'be compliant.' How should the Product Owner reframe it?
- A vacant-property inspection pilot failed because evidence showed landlords were not the users with the job to be done — neighborhood caseworkers were — and feature tweaks are not helping. What should the Product Owner do?
- A council slide for the water-quality product mixes the Product Vision, a twelve-month roadmap, and this Sprint's tasks on one page. What should the Product Owner do?
- The Product Owner of a snow-route notification product asks Scrum Team members to state the Product Vision without notes, and most cannot. What should the Product Owner do?
- A vendor implementing the city's business-license portal proposes replacing the city's Product Vision with the vendor product's marketing vision. What should the Product Owner do?
- A recreation-center Product Vision says only 'delight residents,' with no way to inspect progress. What should the Product Owner do?
- During budgeting, a council member funds a ceremonial city-history game by claiming it aligns with the permitting portal's Product Vision of faster, clearer permits. What should the Product Owner do?
- A legacy mainframe replacement for utility billing has a detailed project plan and no Product Vision. What should the Product Owner do?
- The utilities Product Vision is a long paragraph no one on the Scrum Team can recall mid-Sprint. What should the Product Owner do?
- Planning, Fire, and Public Works each want their own concurrent Product Vision for the city's single building-permit portal. What should the Product Owner do?
- A regional 311 product is drafting its Product Vision. Community advocates argue that equity of access for non-English speakers should be a first-class outcome, not a later ticket. How should the Product Owner treat that request?
- During a public-health clinic portal review, a council aide asks why a major backlog theme exists. What should the Product Owner do?
- The city merges its parks reservation app and its recreation-class registration app into one product, but conflicting old slogans still appear in stakeholder decks. What should the Product Owner do first?
- A Product Owner candidate for the municipal transit-fare product treats the city's framed mission poster ("Serve every resident with integrity") as the Product Vision. What distinction should the hiring panel insist on?
- A permitting dashboard team celebrates a record number of story points while citizen wait times at the permit counter keep getting worse. How should the Product Owner redefine success?
- Residents keep requesting a virtual park ribbon-cutting feature that analytics show almost no one would use, while a high-value trail-condition alert remains unfunded. What should the Product Owner do?
- Transit stakeholders assume residents want push notifications for every service change and want a full notification platform next quarter. The assumption is unvalidated. What should the Product Owner do before a large build?
- The 311 Product Owner can choose two options that deliver similar self-service functionality. Early measures show Option B reduces call-center load more than Option A. How should the Product Owner choose?
- Permit-office stakeholders say the portal is valuable because it shipped twelve features this quarter. How should the Product Owner reframe value?
- A quick-win one-off report on the public-health inspection app would need weekly babysitting and would crowd out later experiments. What should the Product Owner weigh before saying yes?
- The business-license renewal product is always green on server uptime, yet residents still abandon renewals. How should the Product Owner measure Current Value?
- A transit real-time arrival feature meets the Definition of Done but sits undeployed behind a quarterly release freeze. What should the Product Owner argue about value?
- A councilmember demands a low-value vanity splash page for a parks bond before the election. The page would displace a reservation-flow fix with clear outcome evidence. What should the Product Owner do?
- The parks-program registration product needs to decide whether a new youth-camp flow is working after two Sprints. Which measurement approach should the Product Owner use?
- A building-permit form redesign looks cleaner, but an A/B test shows worse completion than the current flow. Marketing wants a full rollout for a modern look. What should the Product Owner do?
- Developers on the clinic-immunization portal propose a full rewrite for value with no named resident or health-department outcome. What should the Product Owner ask next?
- The city is unsure why residents abandon the new curbside-compost signup, and uncertainty about the problem is high. How should the Product Owner order the next work?
- The transit Product Owner must order a safety-critical crossing-alert defect against a convenience enhancement that adds favorite-stop shortcuts. How should cost of delay inform the decision?
- The public-health department claims a huge records-overhaul project is required for compliance value, but much of the scope is gold-plating beyond the regulation. What should the Product Owner do first?
- Value for the building-permit product is discussed only at the annual budget hearing. What should the Product Owner change?
- Operations wants the parks digital team kept at 100% utilization, which would fill Sprints with low-value inventory no resident will use this season. What should the Product Owner do?
- A city services suite covering 311, permits, and utilities shows high login counts but low satisfaction scores. What should the Product Owner investigate?
- Finance wants lower cost-to-serve, clinic nurses want fewer callback minutes, and residents want faster shot appointments on the immunization product. What should the Product Owner do?
- Leadership wants the permit portal to deliver more value faster by relaxing the Definition of Done and shipping known defects. What should the Product Owner do?
- A county public-health clinic portal receives a federal grant earmarked for a wellness-points gamification module. Clinic staff and residents never asked for it; intake interviews show missed appointment reminders and language access as the real immunization-completion blockers. Grant language still allows digital engagement that improves immunization completion. What should the Product Owner do?
- A city transit-app Product Owner can either reduce drop-off in the existing trip planner—used by about 90% of riders—or launch a brand-new kiosk channel at two stations. Analytics show most abandoned journeys die on the current planner's transfer step. How should the Product Owner compare the two bets?
- Parks recreation booking just shipped a quick-reserve flow on the promised date. Completion rate and no-show measures have not moved. Stakeholders want to declare the release a success because it shipped. What should the Product Owner do?
- A municipal utilities billing product has no new resident-facing screens planned this quarter. Finance warns that a single payment-processor outage would halt water-bill collection for days. Developers can reduce that risk with failover work that residents will never see as a new feature. How should the Product Owner treat that work?
- On a building-permit portal, clerks want fewer clicks per review while residents want clearer status and fewer office visits. Each group says the other's request is not valuable. What should the Product Owner do?
- A deputy city manager assigns business-value points to 311 backlog items in a hallway meeting, with no usage data or outcome measures. The deputy wants that score to set Product Backlog order. What should the Product Owner do?
- Vendors pitch a machine-learning chat widget for the library digital-card site. Search logs show FAQ search already answers about 80% of patron questions; remaining failures are ranking and synonym gaps. Where should the Product Owner invest first?
- A building-permit Product Owner believes prefilling known applicant fields will raise form completion. Stakeholders want the idea added to every form this quarter. What is the most professional next move?
- Public-works inspection requests currently live in three department ticket queues plus a shared spreadsheet. Directors each pull Developers toward their own list. What should the Product Owner do?
- Top vaccine-booking items on a health-department Product Backlog are too vague for Developers to forecast a Sprint. A program office responds by demanding a 40-page specification covering the whole season before any further Sprint. What should the Product Owner do?
- Parks stakeholders insist every recreation-booking item carry a MoSCoW label. Three directors mark their items Must, which recreates the original fight under new stickers. What should the Product Owner do?
- A council aide loudly demands a vanity map theme at the top of a transit-app Product Backlog. Developers have also surfaced a high-risk fare-calculation dependency that could stall several upcoming items. How should the Product Owner order the work?
- A "rebuild online permitting" epic is so large that neither Developers nor stakeholders can forecast the next valuable release. What should the Product Owner do?
- Developers on a utilities billing team find a hidden dependency: the two highest Product Backlog items both need a shared rate-table change that is not yet on the backlog. What should the Product Owner do?
- A 311 Product Backlog mixes production defects, department project requests, and half-formed ideas with no type labels and no visible rationale for order. Directors cannot tell what is actually being chosen. What should the Product Owner do?
- A library branch manager keeps a spreadsheet of "the real work" and tells Developers to follow it instead of the Product Backlog. What should the Product Owner do?
- Parks stakeholders want every winter-sports idea fully specified in April, even though those items sit at the bottom of the recreation-booking Product Backlog. What should the Product Owner do?
- Sprint Planning for a public-health case-management product fails because Developers do not understand the top Product Backlog items. Stakeholders blame Planning for running too short. What should the Product Owner do?
- Mid-Sprint, a building-inspections manager adds an item to the Product Backlog and expects the Sprint Backlog to change automatically so Developers drop current work. What should the Product Owner do?
- A transit Product Backlog still carries items for a fare-pilot Product Goal that the city retired last quarter. Stakeholders say to leave them just in case. What should the Product Owner do?
- Acceptance criteria on a permit-status Product Backlog item specify exact pixel positions, hex colors, and a 12-pixel font. Developers say they cannot inspect value—only compliance with a mockup. What should the Product Owner do?
- One Scrum Team's list now contains parks-booking items, clinic-portal items, and permit-search items as if they were a single product. No one can say which Product Goal the order serves. What should the Product Owner do?
- Stakeholders keep pulling 311 items that do not serve the published Product Goal of reducing repeat contacts for the top five request types. The Goal is rarely shown in planning conversations. What should the Product Owner do?
- Emergency production defects hit the utilities payment flow. Operations wants them fixed "off the board" so the Product Backlog still looks like only new features. What should the Product Owner do?
- Stakeholders want story-point estimates for a hundred housing-portal ideas before anyone has refined them or discussed meaning with Developers. What should the Product Owner do?
- A building-permits Product Owner writes 40-page specifications for each backlog item so inspectors will never have to ask questions. Developers still misread intent, and Sprint Planning stalls. What should the Product Owner do?
- A state food-safety rule takes effect in four months. The public-health Product Owner receives dozens of disconnected tickets—label changes, report exports, training videos, and a new inspector tablet—scattered through the Product Backlog. What should the Product Owner do?
- On a transit real-time-arrivals product, Developers keep pulling refactor tickets from a private tech queue that never appears on the Product Backlog, while rider-facing reliability work stalls. What should the Product Owner do?
- Neighborhood associations lobby the parks-reservation Product Owner to add a custom waitlist for every sport. Three meetings of debate have not changed capacity. How should the Product Owner most effectively say no?
- Weekly refinement for the city's utilities-billing product has become a round-robin of what-did-you-work-on updates. Upcoming items stay vague and too large to forecast. What should the Product Owner do?
- Council aides complain they never see the 311 Product Backlog and therefore cannot approve changes. They propose a change-control board that must vote on every reorder. What should the Product Owner do?
- A coach insists every library-holds Product Backlog item must use the As a / I want / So that template or it cannot enter Sprint Planning. Several clear defect reports and a records-retention constraint do not fit the template well. What should the Product Owner do?
- The clinic-appointments Product Owner keeps only tiny copy tweaks at the top of the Product Backlog, while a larger bet on same-day walk-in capacity sits untouched for months. What should the Product Owner do?
- At Sprint Review, residents show that the parking-permit product's renewal reminder is the only thing they actually use—and it fails often. The Product Owner usually waits for the quarterly roadmap workshop to change order. What should the Product Owner do?
- A Definition of Ready checklist for the public-works inspection app now requires signed UX comps, a legal memo, and a cost-benefit PDF before any item may enter Sprint Planning. Work has stalled. What should the Product Owner do?
- Epidemiologists draft many Product Backlog items for a disease-reporting product, and an analyst formats them. Leadership then assumes the Product Owner is no longer accountable for content or order. What should the Product Owner do?
- City council adopts climate resilience as the top strategy. The flooding-alert Product Owner still orders work around a legacy newsletter open-rate goal. What should the Product Owner do?
- A parks-recreation booking product is thriving as its own mobile app with a separate login. City strategy now requires one resident account across permitting, transit, and parks. Local usage looks strong, but the standalone login undermines the citywide channel. What should the Product Owner do?
- The transit Product Owner wants to scale a fare-capping experiment citywide after a two-stop pilot. Finance is ready to fund a full rebuild. Kill criteria were never written. What should the Product Owner do?
- Budget staff ask the recreation-booking Product Owner for a five-year feature roadmap as the product's strategy—month-by-month screens and reports. What should the Product Owner offer instead?
- A neighboring city launches a same-day building-permit experience that residents now cite as how it should work. The Product Owner's portal still positions itself as the official place to upload PDFs. What should the Product Owner do?
- Council asks why the solid-waste Product Backlog contains three large initiatives. Staff answers with component names: routing engine, scale-house API, cart RFID. What should the Product Owner do?
- Parking-meter payments are a reliable fee engine. Leadership wants 100% of Scrum Team capacity on meter-fee enhancements that increase collections this quarter, starving discovery on curb-use equity. What should the Product Owner do?
- City strategy for the permitting product is self-service first. Inspection of the Product Backlog shows about 90% of near-term items are internal staff tools. What should the Product Owner do?
- A parks Product Owner orders a free citywide swim-lesson expansion as if budget were unlimited. Finance notes the product is funded by class fees, a youth-equity grant, and a city subsidy—each with different rules. What should the Product Owner do?
- The mayor's office wants a splashy launch day for a public-health vaccination dashboard. Evidence from a quiet pilot says the data model is still wrong and a big-bang go-live would mislead residents. What should the Product Owner do?
- Transit leadership simultaneously pushes maximize parking-at-stations fee revenue and maximize access equity for low-income riders. Both appear as Musts on the same Product Backlog. What should the Product Owner do?
- The city's strategy is one digital account for park pavilion reservations. A legacy phone-lottery product still has a small group of loud seasonal users and consumes a Developer full time. It no longer fits the strategy. What should the Product Owner do?
- The city's strategic goal is to reduce homelessness cycle time from intake to housing placement. The shelter-services Product Owner is briefed only on server uptime, story points, and number of screens shipped. What should the Product Owner do?
- The 311 platform vendor presents its three-year module roadmap and tells department heads this is now the city's product strategy. Several modules conflict with the city's self-service and equity goals. What should the Product Owner do?
- A city Product Owner for resident services can fund either a splashy parks-reservation skin or a shared resident identity-and-payments platform that would later unlock permit fees, transit passes, and clinic copays. Strategy wants several self-service outcomes next year. What should the Product Owner do?
- After the city's annual strategy offsite, public-health leadership hangs posters about healthier neighborhoods in the clinic lobby. The Product Owner of the immunization and clinic-booking product has no Product Goal tied to those posters. What should the Product Owner do?
- The parks department adopts a digital-everything strategy. Seniors who book picnic shelters and adaptive recreation still complete paper forms at rec centers because the current app fails basic accessibility and some residents have no smartphone. What should the Product Owner do?
- A building-permit Product Owner has spent two quarters on a same-day digital express-permit bet that assumed the state would waive a site-visit rule. The legislature instead tightens the rule, so same-day issuance is now illegal. Leadership wants to finish the remaining screens because so much is already built. What should the Product Owner do?
- The transit Product Owner's live app already sells passes and shows arrivals—the city's current value stream. Strategy also asks for exploration of on-demand microtransit in two neighborhoods. Finance wants 100 percent of capacity on pass-sales optimizations that print money now. What should the Product Owner do?
- The city merges parks-and-recreation with the public-health wellness unit. Each still has its own program catalog, membership rules, and resident-app narrative. Leadership names one Product Owner for the combined resident wellness product. What should the Product Owner do first?
- City strategy now includes food-pantry nonprofits as partners on the public-health benefits portal. Partners still email spreadsheets because the product has no partner workflow. What should the Product Owner do?
- A building-permits steering committee presents a 14-month Gantt of inspection modules, integrations, and go-live weekends and labels it the product strategy. What should the Product Owner do?
- Mid-year, the transit bureau cuts the product budget by 40 percent. The current Product Goal assumed a citywide fare-capping rollout. What should the Product Owner do?
- The building-permit Product Owner is told to make the app do everything the web and the permit counter already do. Counter staff handle complex multi-parcel cases; the web is strong at status lookup; residents want the app for photo uploads and inspection appointments. What should the Product Owner do?
- The city publishes an OKR to cut childhood vaccination gaps by 15 percent. The Product Owner of the public-health clinic portal is asked to support the OKR with more portal features. What should the Product Owner do?
- Parks leadership wants the recreation-booking product's strategy dashboard to include citywide tourism revenue and miles of new trail built by capital projects. The Product Owner cannot influence either through booking outcomes. What should the Product Owner do?
- A two-person skunkworks in the transit bureau shipped a weekend bus-bunching alert that riders actually use. Leadership wants it declared the official disruption product tomorrow without extra staffing or a Definition of Done. What should the Product Owner do?
- In the building-permit inspection scheduler, inspectors want default slots bunched on two weekdays to reduce drive time; residents want evenings and Saturdays. Each group is lobbying council. What should the Product Owner do?
- The public-health clinic portal's steering committee of bureau chiefs insists it speaks for residents. The Product Owner has never watched someone book a childhood immunization. What should the Product Owner do?
- The transit director wants a private preview of the fare-capping Increment and then to skip Sprint Review so the team does not air dirty laundry in front of riders and partner agencies. What should the Product Owner do?
- The permit-help desk's ticket volume is dominated by where-is-my-inspection messages. Stakeholders want the Product Owner to order a bigger ticket-queue interface because volume is the metric. What should the Product Owner do?
- The parks Product Owner maps friends-of-the-park groups, field supervisors, and the budget office by interest and influence. The highest-influence supervisor then demands the right to reorder the Product Backlog after every map review. What should the Product Owner do?
- Only neighborhood-association presidents attend the public-health portal's monthly forum. Clinic data shows most users are shift workers who never come to meetings and struggle with after-hours appointment search. What should the Product Owner do?
- The chief building official asks to be named co-Product Owner of the permit product so inspections and code interpretation have equal say on the backlog. What should the Product Owner do?
- Transit leadership wants a nine-month build of a trip-planner overhaul based on an internal slide. No rider has been interviewed about the current planner's failures. What should the Product Owner do?
- Legal counsel is a key stakeholder for the municipal records-request product because of retention and public-records law. Counsel sends a 40-item mandatory backlog that is mostly internal legal workflows. Residents still cannot file or track a request. What should the Product Owner do?
- A neighboring town both pays into the county's shared permitting platform and has clerks who use it daily. The town's manager wants features that help procurement reporting; clerks need faster plan-review queues. The two ask for opposite order. What should the Product Owner do?
- At Sprint Review for the parks pavilion-booking Increment, a recreation supervisor says the new fee calculator will cause more phone calls, not fewer. A deputy director wants the Product Owner to defend the Increment and keep the supervisor out of future Reviews. What should the Product Owner do?
- Clinic directors, council aides, and a vendor all email the public-health Product Owner with just-add-this-field requests and expect them to appear at the top of the Product Backlog. What should the Product Owner do?
- After a packed neighborhood meeting about the parks recreation booking product, residents demand that every requested amenity filter ship in the next Increment. What should the Product Owner do with that input?
- Agency directors keep sending the transit-app Product Owner new rider-feature lists and assume each list will ship. How should the Product Owner set expectations?
- County IT operations wants a multi-month production freeze on the public-health clinic booking product, arguing that any change risks an outage during flu season. The freeze would stop validated appointment improvements. What should the Product Owner do?
- During the Sprint Review for the building-permit portal, contractors suggest several adaptations after inspecting the Increment. What should the Product Owner do next?
- A transit rider advisory board wants a quarterly vote to set the Product Backlog order for the city’s trip-planning product. What should the Product Owner do?
- On the city’s building-permit product, residents seeking faster lawful permits, counter staff who operate the workflow, and the development-services director who funds the work all claim to be “the customer.” How should the Product Owner distinguish those roles?
- Utility-billing stakeholders skip the Product Owner and escalate new requests to the CIO every morning, creating drive-by interruptions. What should the Product Owner do?
- The public-health immunization scheduler has a high-risk no-show and eligibility journey that clinics keep misunderstanding. How should the Product Owner improve alignment on what “valuable” means?
- Language-access advocates ask to join vision and value conversations for the city’s 311 service-request product, arguing that non-English speakers are underserved. Some directors call that “out of scope politics.” What should the Product Owner do?
- Parks recreation booking missed the published late-summer release forecast after a spike in failures on a risky integration. Stakeholders have not heard yet. What should the Product Owner do?
- Bus-operations supervisors ask the Product Owner of the operator shift-swap tool to fund more classroom training because staff “keep using it wrong.” Ticket notes show repeated confusion in the same workflow. What should the Product Owner do first?
- Library-board members distrust the digital-card product after two years of slide-deck promises and few usable releases. How should the Product Owner rebuild trust?
- A public-works director walks to the Developers of the pothole-reporting product and assigns them a “quick dashboard” outside the Product Backlog. What should the Product Owner do?
- Parks booking analytics show a sharp drop in evening tennis reservations, but staff disagree about why. How should the Product Owner build customer insight?
- A new county ordinance changes who qualifies for the public-health home-visit program, shifting the jobs applicants and caseworkers need the product to do. What should the Product Owner do?