Dev360
Last updated
Last updated
Ensure all the metrics are configured as mentioned below for the Dev360 module -
You can configure DORA metrics (Cycle Time, Deployments, CFR, MTTR), with your specific internal process that may include Draft PRs, enforce correct branches for tracking, and use of Squash/Merge feature for streamlined commit history.
For detailed configuration steps, refer to each metric guideline in the links below -
[To be followed in your Issue Tracker]
Here are some best practices for your Issue tracker project management to fetch accurate data insights into Typo-
Epics: Large bodies of work that can be broken down
Stories: User-focused features or changes
Tasks: Technical work items
Bugs: Defects requiring fixes
Organize by functional areas (Frontend, Backend, Infrastructure)
Limit to 5-7 main components
Use labels for more granular categorization
Backlog → To Do → In Progress → Review/QA → Done
Backlog → To Do → In Progress → Code Review → Testing → Ready for Release → Done
Keep states minimal but sufficient
Each state should represent a distinct phase
Avoid creating states for edge cases
Consider adding a "Blocked" flag rather than a blocked state
Component
Priority (P1-P4)
Sprint
Story Points
Labels (for filtering)
Epic Link (when applicable)
Assign during sprint planning, not before
One primary assignee per issue
Use watchers for stakeholders
Consider team capacity before assignment
Single assignee per issue
Don't assign until sprint planning
Respect team member capacity (WIP limits)
Use watchers for additional stakeholders
Use Fibonacci sequence: 1, 2, 3, 5, 8, 13
Cap at 13 points - larger items should be broken down
Consider effort, complexity, and uncertainty
Don't assign points to bugs (use priority instead)
Use for initial backlog grooming
XS, S, M, L, XL
Convert to points during sprint planning
Fixed duration (typically 2 weeks)
Consistent sprint names: YYYY-MM-DD Sprint XX
Set sprint goals
Maintain velocity tracking
Regular backlog grooming (bi-weekly)
Sprint planning meetings
Daily standups using the board
Sprint retrospectives
Link PRs directly to issues
Use standard naming: [PROJ-123] Brief description
Automated status updates via Git integration
To set up deployment, you must integrate your CI/CD tool with Typo. Once integrated you can configure the settings using the configure button present on the top right corner.
By default, the data shown in investment distribution is based on your issue tracker ticket types. This can be configured as per your requirements. To set this up, use the "configure" button in the top right corner.
Some commonly used categories by engineering teams are mentioned in the next section.
Here are the core resource allocation categories in tech teams:
Features
New product development
Enhancements
Growth initiatives
Customer requests
KTLO
System maintenance
Critical bugs
Security patches
Production incidents
Tech Debt
Refactoring
Architecture improvements
Test coverage
Platform upgrades
Infrastructure
DevOps/CI/CD
Developer tooling
Monitoring
Scalability
Innovation
Technical spikes
Prototypes
New tech evaluation
Research
Support
Customer tickets
Operations
Data management
Compliance
To create a custom report, navigate to the Custom Report section & click on the Create Report button located at the top right corner of the screen.
To set up incidents, navigate to the incident section and click on the configure button located at the top right corner of the screen.
To set up incidents, navigate to the initiative section and click on the create button located at the center of the screen.