Quick Start
Once SprintUnity is installed and your tenant is active, seven setup steps make the rest of the app much more useful from day one. Walk through them in order below — each one only takes a couple of minutes.
1. Confirm your tenant is active
This happens automatically on first load — you can double-check it under General Settings.
- Verify your tenant statusEnsure your tenant is active and connected.
2. Set up Roles & Permissions
Decide who can configure the app, who can run evaluations, and who has read-only access, before opening it up to the wider team.
- Assign global roles (Admin, Manager, Evaluator, Member).
- Set module-level permissions and access.
- Review default permissions and adjust if needed.
3. Set up Team Management
Define your teams and add members — capacity, evaluation, and voting are all scoped to a team.
- Create your teams (e.g., Platform Team, Delivery Team, QA Team).
- Add team members and assign their primary role.
- Teams will be used across capacity, evaluation, voting, and reports.
Why this step matters
You'll configure
- Teams
- Members
- Member Roles
Example
4. Configure Sprint Capacity
Set the maximum Dev and QA hours a sprint should be planned against, so the app can flag over-commitment before it happens.
- Define maximum Development hours for the sprint.
- Define maximum QA hours for the sprint.
- Set a warning threshold to get early alerts when capacity is at risk.
Example Configuration
What you'll get
- Capacity utilization tracking
- Over-commitment warnings
- Better sprint planning accuracy
- Healthier, more predictable delivery
Capacity Utilization Preview
5. Configure Story Point Mapping
Decide how your team's sizing scale (T-shirt sizes, Fibonacci, or a custom scale) maps to story points for voting.
- Choose your sizing method (T-shirt, Fibonacci, or Custom).
- Define the hour ranges for each size.
- Map each size to the story point value used for voting.
- Save the mapping — it will be used across all voting sessions.
Example: Fibonacci Mapping
Hour Range Configuration
6. Run the Evaluation Setup Wizard
Define role-specific, weighted evaluation criteria and how often evaluations recur — this only needs to be done once per team.
- Select evaluation roles (e.g., Developer, QA, Team Lead).
- Define evaluation criteria and assign weights.
- Set scoring method for each criterion.
- Choose evaluation frequency and start/end dates.
- Review the summary and save your configuration.
Your Evaluation Summary
7. Review Settings and Issue DOR rules
Check general tenant settings and set your Definition of Ready (DOR) rules so Issue DOR checks match how your team actually works.
- Review general application settings (notifications, dashboard, defaults).
- Define your Issue DOR rules and assessment profile.
- Ensure rules reflect your team's workflow and quality standards.
- Save and you're all set to start using SprintUnity.
Configuration Overview
Anyone reading this documentation can mark whether it answered their question — no permission required.