A public-works digital twin team asks whether a daily coordination meeting is mandatory. How should they contrast Scrum and Kanban on this point?
Select an answer to reveal the explanation.
Short Explanation
Scrum’s Daily Scrum is on the calendar like a required morning roll call for the Developers. Kanban might hold a standup if it helps flow—but it’s not the same mandated Scrum event with Scrum’s rules. Required versus optional is the key nuance.
Full Explanation
For a public-works digital twin team asking whether a daily coordination meeting is mandatory, the accurate contrast is that the Daily Scrum is a required Scrum event, while Kanban may use daily standups optionally without Scrum’s same event rules. Method choice changes whether the daily meeting is prescribed with Scrum’s purpose and structure or merely an optional flow coordination habit for the civic engineering software team.
Claiming Kanban requires a Daily Scrum with the three Scrum questions while Scrum makes standups optional reverses the methods’ rules. Claiming neither approach ever uses short daily coordination meetings of any kind fails because Scrum requires Daily Scrum and Kanban teams often choose standups when helpful. Claiming only the city attorney may facilitate daily meetings regardless of method fails because facilitation is not reserved to counsel by either method’s core rules.
Exam caveat: Daily Scrum is mandatory in Scrum; Kanban standups are optional practices, not the same prescribed event. Operational check: if the digital twin team uses Scrum, run Daily Scrum as a Developers’ coordination event within the timebox rules; if using Kanban, adopt a standup only if it helps flow, without importing Scrum mandates by accident.