Event Storming
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.
This template was created by Judith Birmoser.
Get started with this template right now.
Retrospective - Summer
Works best for:
Retrospectives, Agile Methodology, Meetings
The Retrospective - Summer template offers a seasonal and themed approach to retrospectives, perfect for capturing the spirit of summer. It provides elements for reflecting on achievements, experiences, and goals amidst the summer backdrop. This template enables teams to relax, recharge, and recalibrate their efforts for the upcoming season. By promoting reflection and rejuvenation, the Retrospective - Summer empowers teams to celebrate successes, learn from setbacks, and embark on new adventures with renewed energy and enthusiasm effectively.
Start, Stop, Continue Template
Works best for:
Retrospectives, Meetings, Workshops
Giving and receiving feedback can be challenging and intimidating. It’s hard to look back over a quarter or even a week and parse a set of decisions into “positive” and “negative.” The Start Stop Continue framework was created to make it easier to reflect on your team’s recent experiences. The Start Stop Continue template encourages teams to look at specific actions they should start doing, stop doing, and continue doing. Together, collaborators agree on the most important steps to be more productive and successful.
Skill Cards
Works best for:
Agile
Skill Cards are a dynamic tool for assessing and developing skill sets within Agile teams. They provide a structured framework for reflecting on strengths, weaknesses, and learning goals, fostering a culture of continuous improvement. With Skill Cards, teams can identify skill gaps, distribute knowledge, and tailor professional development plans, empowering you to cultivate a high-performing team with diverse skill sets and shared expertise.
Agile Product Roadmap
Works best for:
Roadmap, Planning, Mapping
The Agile Product Roadmap template enables teams to visualize and communicate the strategic direction of their product development in an agile environment. It allows for flexibility and adaptation to changing requirements while providing a clear overview of priorities and timelines. By incorporating feedback loops and iterative planning, teams can ensure alignment with stakeholder expectations and deliver value incrementally.
Starfish Retrospective
Works best for:
Retrospectives, Agile Methodology, Meetings
The Starfish Retrospective template offers a structured approach to retrospectives using the metaphor of a starfish. It provides elements for identifying what to start, stop, continue, do more of, and do less of. This template enables teams to reflect on past iterations, identify actionable insights, and prioritize improvements. By promoting clarity and focus, the Starfish Retrospective empowers teams to drive meaningful change and continuous improvement effectively.
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.