Thunderdome is a fun way to facilitate agile scrum practices including Story pointing (battles), Sprint Retrospectives, Story mapping, Async Daily Standup (team standup) and more.
As a new warrior in this realm, let this be your guide. First, we need to know who you are.
Create a new account, or join as guest.
Having an account lets you save your battles and more.
- Name
This will be visible to others. - Email (for account)
- Password (for account)
Use a strong password. Type it again to confirm.
You will receive an email to confirm your new account.
Use the email/password you created when registering.
- Password
OIDC Providers coming soon.
Forgot your password? Thunderdome can send a password reset link to your email.
Warrior, it is all about you! Control your Thunderdome experience.
- Name
This will be visible to others. - Email
Update your account email, or enter one if you are a guest. - Country (optional)
- Locale, default: English
8 locales to choose from. - Company (optional)
- Job Title (optional)
- Theme, default: auto
The default lets the operating system and browser define dark or light, if supported. If you prefer a darker or lighter interface, you may choose it here. - Option: Enable Battle Notification, default: true
- Avatar, default: robohash
Several others to choose from, pick your flavor; mp, identicon, monsterid, wavatar, retro.
Create an API key to integrate Thunderdome with your tools.
See API Documentation here Thunderdome API Docs
Integrate directly with your team's backlog to import your stories to point.
Other integrations coming soon.
This is the Thunderdome, but you are free to leave. We will erase all data about you.
This is permanent: All poker sessions, retros, story maps, and orgs/teams directly owned by your account will also be deleted.
In Thunderdome, an agile poker planning session is known as a Battle.
You can create a battle to determine the size of a story, or join one in progress.
- Name
- Team (optional)
- Point Range Allowed, default: [ 1, 2, 3, 5, 8, 13, ? ]
- Plans
Upload an XML or CSV for plans, or add manually. See note in Plans. - Point Average Rounding, default: Ceil
Other options; Round, Floor. - Option: Auto Finish Voting, default: true
- Option: Hide Voter Identity, default: false
- Passcode (optional)
- Leader Code (optional)
The planning session is real-time, each warrior chooses the size for the story and votes are shown when everyone has finished.
If the team agrees, the battle is over. If not, then it has just begun!
This can be a list of Stories, Bugs, Tasks, etc. and serves as a queue for team voting.
Premium feature.
Upload.
The CSV file must include all the following fields with no header row:
Type,Title,ReferenceId,Link,Description,AcceptanceCriteria
- Type, default: Story
Other Types: Bug, Spike, Epic, Task, Subtask - Name
- Reference ID
- Link
- Priority
Priorities; Blocker, Highest, High, Medium, Low, Lowest - Description
A full text editor is supplied to provide a detailed description. - Acceptance Criteria
A full text editor is supplied, feel free to use Gherkin statements.
See who is voting or become a spectator.
Send a link for others to join the battle.
Facilitates an agile sprint retrospective.
Retrospectives happen in phases. The first phase is the Prime Directive. You may edit or delete the retro at any time.
- Prime Directive
- Brainstorm
Add comments. What went well? What needs improvement? I want to ask... - Group
Organize comments into topics. Drag and drop to sort. - Vote
Vote for groups to discuss first. - Action Items
Add Action Items, the grouping and voting phases become locked. - Done
Export the Retro
- Name
- Team (optional)
- Join Code (optional)
- Fac. Code (optional)
- Max Group Votes per User, default: 3
- Brainstorm Phase Feedback Visibility, default: Feedback Visible
Other options include concealed and hidden. Determines if team members can see each other's suggestions.
Stories are units of work that need to be sized.
A goal is a way to group stories.
- Name (optional)
A column is customizable and serves as a way to track stories throughout the goal.
- Title Text (optional)
A story is a unit of work. It can be in an open or closed state.
- Name
- Link
- Points
- Color
- Content
- Discussion
Coming Soon
- Name
- Role
- Description
A palette is provided so that you can choose to apply meaningful colors to story cards.
This is where you can define what each color means.
- Name
- Team (optional)
- Passcode (optional)
- Facilitator Code (optional)
Teams can be simple, or they can be within Organizations and Departments.
- Name
- Name
- Name
- User Email
- Role
Admin or Member
Asynchronous daily standup tool to aid in speeding up standup or making standups completely async depending on team practices.
Provide your daily standup report. What did you do yesterday? What are you doing today? Any blockers? Anything to discuss?
Choose your timezone.
Creating these sessions within a Team, Organization, or Department will pre-populate those fields.
See each individual section for further details about creating battles, retros, and storyboards.
🌍 Thunderdome has made every effort to be an international tool, and help developers of all nationalities unite together.
Thunderdome is released as open source software, the code is hosted on Github and licensed Apache 2.0.
v3.6.3