Event Storming
Workshop-based method to quickly find out what is happening in the domain of a software program.
Workshop-based method to quickly find out what is happening in the domain of a software program.
What is Event Storming?
Event Storming is a communicative brainstorming method in which knowledge and understanding of a specific, delimited field of knowledge (a domain of expertise) is jointly developed and visualised in a workshop. The starting point are so-called domain events.
The 4 evolution stages of Event Storming
Step 1: Collect Domain Events - discover them
Step 2: Refine Domain Events - placing them in sequence
Step 3: Track causes - modelling out the broader ecosystem
Step 4: Re-sorting & result - categorize the events and build Bounded Contexts
Get started with this template right now.
OKR Drafting Board
Works best for:
Agile
The OKR Drafting Board (New) is a visual tool for defining and tracking Objectives and Key Results (OKRs). It provides a structured framework for setting ambitious goals, defining measurable outcomes, and aligning teams around shared objectives. This template enables organizations to articulate their strategic priorities, track progress transparently, and foster accountability and alignment across teams. By promoting focus, alignment, and agility, the OKR Drafting Board empowers organizations to achieve breakthrough results and drive continuous improvement.
Roadmap Planning Template
Works best for:
Roadmap, Agile
The Roadmap Planning Template in Miro is a dynamic tool designed to streamline the process of planning and tracking project milestones. This template is part of Miro's Intelligent Templates offering, which integrates AI, interactive widgets, and automation to enhance productivity. One key feature of this template is its real-time collaboration capability, allowing team members to work together seamlessly, regardless of their location. This feature ensures that everyone is on the same page, making it easier to assign tasks, set deadlines, and track progress effectively.
Mad Sad Glad Retrospective
Works best for:
Brainstorming, Ideation
It's tempting to measure a sprint’s success solely by whether goals and timelines were met. But there’s another important success metric: emotions. And Mad Sad Glad is a popular, effective technique for teams to explore and share their emotions after a sprint. That allows you to highlight the positive, underline the concerns, and decide how to move forward as a team. This template makes it easy to conduct a Mad Sad Glad that helps you build trust, improve team morale, and increase engagement.
Quick Retrospective Template
Works best for:
Education, Retrospectives, Meetings
A retrospective template empowers you to run insightful meetings, take stock of your work, and iterate effectively. The term “retrospective” has gained popularity over the more common “debriefing” and “post-mortem,” since it’s more value-neutral than the other terms. Some teams refer to these meetings as “sprint retrospectives” or “iteration retrospectives,” “agile retrospectives” or “iteration retrospectives.” Whether you are a scrum team, using the agile methodology, or doing a specific type of retrospective (e.g. a mad, sad, glad retrospective), the goals are generally the same: discovering what went well, identifying the root cause of problems you had, and finding ways to do better in the next iteration.
Rose, Bud, Thorn Template
Works best for:
Retros, Agile
The Rose, Bud, Thorn template is a structured method for team reflection and feedback, designed to help teams identify positive aspects, potential opportunities, and challenges within a project or situation. One key benefit of using this template is its ability to promote balanced feedback and productive discussions, which can lead to improved team processes and outcomes.
STATIK Canvas
Works best for:
Agile, Kanban
STATIK Canvas template provides a structured framework for implementing Kanban methodology within teams. By focusing on understanding, shaping, and sharing knowledge, this template facilitates continuous improvement and alignment with organizational goals. Teams can visualize their workflow, identify improvement opportunities, and implement changes iteratively to achieve higher efficiency and effectiveness in their processes.