Supporting PI Execution
RTE · 39 questions
- Mid-PI, a state DMV licensing ART steering group asks why a team objective about one licensing workstation and an ART objective about statewide issuance flow appear interchangeable. How should the RTE distinguish them?
- A sponsor on a city housing-voucher ART asks the RTE to rewrite ART PI Objectives every week as new council requests arrive, with no re-planning. What should the RTE do?
- Mid-PI, a county elections systems ART dashboard shows only feature completion percentages, and nobody can say which PI Objectives are on track. What should the RTE emphasize?
- On a municipal utilities billing ART, Business Owners assigned planned business value during PI Planning and never looked at those scores again. What should the RTE restore during execution reviews?
- A team on a public works work-order ART silently drops a committed PI Objective mid-increment and does not mention it in any ART sync. What should the RTE expect?
- After the PI, airport operations digital ART leadership marks every missed uncommitted objective as a delivery failure and lowers the ART's predictability score. What clarification should the RTE provide?
- A court case-management ART publishes ART PI Objectives that no team has work for, and Product Management calls them direction. What should the RTE require?
- Executives ask which fire-EMS records ART PI Objectives are at risk this iteration, and the RTE has no current view because teams only discuss risk at PI Planning. What should the RTE use?
- A team on a social-services eligibility ART pads its ART-visible PI Objectives with internal chores no Business Owner valued during planning. What should the RTE coach?
- Mid-PI, an open-data and civic-engagement ART treats this iteration's team goals as a replacement for the PI Objectives agreed at planning. What distinction should the RTE reinforce?
- A fleet telematics ART has healthy team boards but no ART Kanban, so features and enablers appear only on disconnected team walls. What visualization does the RTE need?
- Dependencies on a city permits portal ART live only in long email threads, and teams miss handoffs because nobody sees the same picture. What should the RTE put in place?
- Leaders on a county tax-assessment ART keep starting new projects because work in process is invisible, so queues grow while the start rate does not slow. What should the RTE make visible first?
- A municipal transit fare-system ART board shows only a Done count for the PI, while work in analysis, build, review, and waiting-for-ops stays invisible. What visualization is missing?
- A public-health immunization registry ART bought a digital flow board, then stopped updating it after two iterations, and leaders still quote the stale columns in steering. What should the RTE insist on?
- Risks for a library consortium digital-services ART live only in a private RTE spreadsheet, so teams and Business Owners cannot see ROAM status during the PI. What should the RTE do?
- A parks reservation and facility ART can see that blockers exist but cannot tell which ones have been stuck for days versus hours. What should the flow visualization include?
- Stakeholders on a wastewater SCADA modernization ART cannot tell which features are in development, test, staging, or production, because team boards show stories rather than feature delivery state. What should the RTE add?
- A 911 CAD/RMS integration ART built a program board in PI Planning, then threw it away on Day 3 of the first iteration, and dependencies immediately went dark. What should the RTE do?
- A school-district student-information ART runs two dashboards that disagree on feature status, triggering arguments in every ART Sync. What should the RTE establish?
- The state DMV licensing ART parks all testing in a final hardening week and treats earlier iterations as code-only. What built-in quality expectation should the RTE summarize for the train?
- Teams on the city housing-voucher ART each call stories done against different bars and skip a shared Definition of Done. What basic Agile quality practice should the RTE reinforce?
- Leaders on the county elections systems ART ban pairing and peer review so developers can go faster. What quality practice should the RTE summarize?
- Regression tests on the municipal utilities billing ART are still entirely manual, and a sponsor tells the RTE to personally script the suite this weekend. What is the RTE's appropriate quality-practice stance?
- The public works work-order ART never runs architecture spikes, so integration surprises appear in the last iteration. How should the RTE connect exploration to quality?
- The airport operations digital ART treats performance, security, and availability as production-only surprises. What built-in quality concern should the RTE raise?
- Feature branches on the court case-management ART stay open for months, and merges fail just before System Demo. What quality risk should the RTE summarize?
- The fire-EMS records ART System Demo keeps exposing brittle integrations that teams had not combined until demo week. What quality discipline should the RTE reinforce?
- Security scanning for the social-services eligibility ART happens once a year, after several PIs have already shipped. What quality practice should the RTE summarize?
- Teams on the open-data and civic-engagement ART plan zero capacity for refactoring or enablers, and technical debt is growing. What quality practice should the RTE coach into the plan?
- Leaders on the fleet telematics ART plan to do DevOps by hiring one person to run all deployment tickets. What should the RTE summarize?
- The city permits portal ART starts building features without exploring applicant and reviewer needs. Which Continuous Delivery Pipeline element is the train skipping?
- Integration on the county tax-assessment ART is still a rare, fully manual event. What Continuous Integration purpose should the RTE summarize?
- The municipal transit fare-system ART can technically deploy fare changes, but leaders refuse to release because they treat deploy and go-live as the same event. What CDP distinction should the RTE clarify?
- Continuous Deployment automation is absent on the public-health immunization registry ART, so every validated change waits for a quarterly cutover. What CD purpose should the RTE summarize?
- A director tells the RTE of the library consortium digital-services ART to personally configure the CI pipelines this PI. What is the RTE's proper CDP stance?
- Value stream mapping on the parks reservation and facility ART shows work sitting idle for weeks after development is marked complete. What should the RTE treat those waits as?
- The wastewater SCADA modernization ART reports only project milestones and never tracks deployment frequency or change-failure signals. What DevOps measurement awareness should the RTE summarize?
- Product Management is excluded from Continuous Exploration on the 911 CAD/RMS integration ART, leaving engineers to guess dispatcher needs. What CDP practice should the RTE restore?