The paratransit-scheduling team wants to keep Scrum events and add a Kanban board. How should the SM/TC treat that mix?
Select an answer to reveal the explanation.
Short Explanation
A paratransit team can keep Sprint Goals and still put work on a board. That is Scrum using a Kanban system, not a secret third religion. Do not make them burn the events or invent a new method name.
Full Explanation
A paratransit-scheduling team that wants to keep Scrum events and add a Kanban board can do so: allow a Kanban system inside SAFe Scrum; the team-process choice remains Scrum or Team Kanban. Keeping Sprint Goals while visualizing work on a board is Scrum using a Kanban system, not a secret third religion. Coaches should not force a false dichotomy or invent a new official method name.
Forbidding the board because mixing practices creates an unofficial third method fails because visualization and WIP management inside Scrum are legitimate and common. Dropping Scrum events immediately because a board appears fails because a board alone does not equal a Team Kanban method choice. Registering the mix with the SPC as a new official team method name fails because the Framework's team-process choices remain Scrum or Team Kanban.
Exam caveat: practices can blend; the named team method is still one of the SAFe options, not a bespoke brand. Operational check: keep the paratransit team's Scrum events and goals if that is the method choice, add board columns and policies that aid flow, avoid declaring a third method, and inspect whether the board improves transparency without breaking Scrum empiricism.