🎯 Sprint atual
Tap PLAY to begin.
👥 Trabalho do time
Aguardando a Sprint
👩💻
👨💻
🧑🔬
PBI
Dev
Tests
Integration
Done
Objective
Complete four Sprints. Each Sprint has five simulated days. From day two through day five, work starts with a Daily Scrum.
📌 Conceito em jogo
Scrum uses transparency, inspection, and adaptation to deal with complex work.
📚 Product Backlog
Lista ordenada e emergente do que é necessário para melhorar o produto. O Product Owner é responsável por sua gestão eficaz e por maximizar valor.
✅ Done
Itens que atenderam à Definition of Done e já fazem parte do Incremento.
🎯 Sprint Goal
Observed velocity will appear here.
Wait for Sprint Planning.
🏃 Sprint Backlog
É composto pelo Sprint Goal, pelos Product Backlog Items selecionados e pelo plano acionável criado e atualizado pelos Developers.
🔎 Detalhamento do Sprint Backlog
Mostra o plano dos Developers, relação com o Sprint Goal e estágio em direção à Definition of Done.
📉 Sprint Burndown
Trabalho restante durante a Sprint. É uma prática comum, mas não é um artefato obrigatório do Scrum.
ActualLinear reference
📈 Product / Release Burnup
Valor acumulado entregue versus escopo conhecido. Mudanças de escopo ficam visíveis.
Delivered valueKnown scope
🌊 Cumulative Flow Diagram
Shows work to do, in progress and Done. A widening band suggests accumulation or a bottleneck.
To doIn progressDone
📊 Velocity
Pontos que chegaram a Done em cada Sprint. A mediana das últimas três Sprints é usada como evidência de capacidade no Planning; não é meta nem medida individual.
Done points
👥 Responsabilidades Scrum
🧭 Product OwnerMaximizes value, communicates the Product Goal, and effectively manages the Product Backlog. Does not assign tasks to Developers.
🛠️ DevelopersSelect work in Planning, create and adapt the Sprint Backlog, conduct the Daily Scrum, and deliver Increments that meet the Definition of Done.
🧩 Scrum MasterHelps Scrum be understood and effective, works on impediments, and promotes improvement. Is not the team manager and does not chair the Daily Scrum.
🗓️ Eventos representados
Sprint PlanningDefines why the Sprint is valuable, what can be done, and how the work will begin.
Daily Scrum15 minutes in reality; here it is compressed into one decision. Developers inspect progress toward the Sprint Goal and adapt the plan.
Sprint ReviewThe Scrum Team and stakeholders inspect the Sprint outcome and progress toward the Product Goal; the Product Backlog may be adapted.
RetrospectiveThe Scrum Team plans ways to increase quality and effectiveness.
🚦 Fluxo, WIP e Swarming
WIP (Work in Progress)The game suggests at most 2 items in progress at once. With 3 or more, flow efficiency drops because of context switching and coordination. When an item finishes, the team automatically pulls the next priority work to avoid idle capacity.
SwarmingTwo or three Developers can collaborate on the same item. This speeds up that item, but with diminishing returns.
VelocityCounts only product PBI points that reach Done. Emergent technical work consumes capacity without inflating velocity.
📏 Indicadores do jogo
Stakeholder trustRepresents how predictable and reliable customers and stakeholders perceive the product and team to be.
Technical debtRepresents future work created by technical shortcuts.
✅ Definition of Done
An item counts as part of the Increment only when it meets the Definition of Done.
🧠 Avaliação formativa
The diagnosis will appear at the end and will use the decisions made during the game.
📊 Histórico
| Sprint | Goal | Value | Velocity |
|---|---|---|---|
| No Sprint completed. | |||