Benefits-eligibility developers never get training because it is "not sprint work." What should the Scrum Master / Team Coach schedule?
Select an answer to reveal the explanation.
Short Explanation
If eligibility rules never get a class because "that is not sprint work," the team is a clerk who never reads the new handbook. IP is the official classroom. Put training on the IP calendar and guard it.
Full Explanation
Continuing education belongs in IP and should be protected as an IP activity. Benefits-eligibility developers told training is “not sprint work” never skill-up, and eligibility mistakes hit residents. The Scrum Master / Team Coach schedules education in IP so capability compounds. After-hours-only training taxes people and signals learning is unpaid.
Sending people to training only after hours so iterations stay full externalizes cost onto staff. Waiting for a budget year and a separate training project delays needed skills. Substituting vendor webinars during Daily Stand-up and skipping IP misuses sync time and still fails IP purpose.
Exam caveat: IP explicitly supports education; do not defer all learning outside the cadence. Operational check: put at least one benefits training or practice item on the IP backlog each PI.
In municipal ARTs, residents experience these coaching choices as faster or slower public services—licensing lines, housing decisions, water bills, snow routes, and emergency response—so keep events and buffers tied to inspect-and-adapt outcomes. Record the decision, the owner, and the next inspection date so the team can verify civic impact. Confirm the next demo or metrics review will show whether the change helped residents.