📖
Typo Help Docs
  • Welcome
  • Getting Started
    • Onboarding
    • Integrations
      • Git
        • GitHub
        • GitLab
        • BitBucket
        • Azure Repos
        • Gitlab On-prem
      • Issue Tracker
        • JIRA
        • Linear
        • GitHub Issue
        • Shortcut
        • ClickUp
      • CI/CD Tool
        • Circle CI
        • Jenkins
        • Heroku
        • GitHub Actions
        • Azure DevOps
        • Custom Deployment Webhook
      • Slack
    • How Requestly setup Typo in a few days
  • Platform
    • Dev Analytics
      • DORA
      • Insights
        • Teams
        • Members
        • Sprints
        • Pull Requests
        • Deployments
      • Incident
      • Goals
      • Investment
      • Initiative
      • WorkLog
      • Custom Reports
      • Settings
        • Teams
        • Member
        • Repository
        • Projects
        • Manage Access
        • Notifications
    • Code Health
      • Code Review
      • Code Coverage
    • DevEx
  • Implementation Plan
    • Phase 1 - Setting Up Data Sources
    • Phase 2 - Metric Configuration
      • Dev360
      • Code Health
      • DevEx
    • Phase 3 - Team Rollout
  • Engineering Metrics
    • DORA
      • Cycle Time
      • Deployment PRs
      • Change Failure Rate
      • Mean Time to Restore
    • Pull Request Metrics
      • Avg. Commits During PR Review
      • Coding Days
      • Coding Time
      • Merge frequency
      • Merge Time
      • Pickup Time
      • PR Size
      • PRs Merged without Review
      • Review Time
      • Efficiency Score
    • Sprint Metrics
      • Carry over
      • Developer Workload
      • Issue Cycle Time
      • Issues At-Risk
      • Scope creep
      • Team Velocity
      • Work Breakup
      • Work Progress
    • Code Quality Metrics
      • OWASP Top 10
      • Vulnerability
      • Security
      • Performance
      • Duplication
      • Code Smell
    • Deployment Metrics
      • Deployment - Failure
      • Deployment - Frequency
      • Time to Build
    • Incident Metrics
      • Incident - Opened
      • Avg Resolution Time
    • DevEx Metrics
      • DevEx Score
      • Space mood
      • Response Rate
      • Manager Support
      • Developer Flow
      • Product Management
      • Development & Releases
      • Culture & Values
  • Configurations
    • Cycle Time
    • Deployment PRs
    • Change Failure Rate (CFR)
    • Mean Time To Restore (MTTR)
    • CI/CD - Deployment
    • Incident
    • Initiative
    • Investment Distribution
    • PR Labels
    • Code Health
    • Code Coverage
    • DevEx
    • Notifications
    • Manage Access
  • FAQ's
    • Data Security
      • GitHub App Permissions Details
      • Why does Typo need write permission to my code?
      • Does Typo has access to my code?
      • What data security guidelines does Typo follow?
    • Integrations
      • Can Typo application work with on-prem Gitlab?
      • How do I get Issue Tracker data?
      • How do I get Git data?
    • Pricing
      • How does the pricing work?
      • How do I upgrade my plan?
    • Access Management
      • My team member is not able to login to Typo
    • Metrics
      • How does Typo predict developer burnout?
      • Is there a way to change the branch that Deployment PRs are measured against?
      • Synchronize “CFR” & “MTTR” without incident management?
      • How quick does the pull-request page update? I closed a PR but the Typo still shows Awaiting Review
      • How do I add any new repo?
      • How to Configure Typo Code Health Checks to Block a PR Merge in Git
      • Can I exclude a person from metrics calculation?
      • Can I track the Cycle time based on the status of the JIRA tickets?
      • How do I unlink the JIRA tracker & integrate Linear?
      • How to exclude a PR from any metric calculation?
      • My data is not visible, I have synced the repo
    • Platform
      • Can I use your application on-premise?
    • Delete Account
      • How can I delete my account?
Powered by GitBook
On this page
  • Pre-Launch Demo
  • Granting Access
  • Post-Launch Support
  • Primary Support Channel
  • Channel Members
  • Support Protocol
  • New Releases
  1. Implementation Plan

Phase 3 - Team Rollout

Here’s a quick checklist for the phase 3 setup -

Pre-Launch Demo

We recommend conducting a product walkthrough session with the entire team to introduce the product. A few suggested talking points:

  • Position Typo as a platform introduced to help improve the overall engineering efficiency across teams

  • This step is a data-driven approach to bring transparency in the system

  • Not a system to rate developers/teams, but more towards bringing visibility across the delivery cycle

  • Show the developer view to give confidence on how they would be able to visualize data. Plus, code review automation/alerts to fasten their workflows

If required, our team can also be a part of this call to conduct the demo alongside you. Once done, then grant access to the users.

Granting Access

While inviting users, 3 types of roles to be assigned :

  • Admin

    • Views entire data

    • Able to configure the entire platform

  • Manager

    • Only views data of the teams assigned to them

    • Able to configure only for their respective teams

  • Developer

    • Only views their data - Git commits/PRs/Tickets/Goals

    • Able to view their teams’ DORA metrics

The users can log in either with their Git accounts or Google account. We recommend Git users use their Git account login only.

Post-Launch Support

We recommend creating a new Slack channel where some of your team members (a mix of managers/devs) can be added alongside our team members to have direct feedback discussions.

Here’s a detailed protocol of our Customer Support on Slack Channel -

Primary Support Channel

  • Dedicated Slack channel "#typo-company_name>"

  • The channel monitored 24/5 by the Typo team

  • SLA: Critical issues - 2-4 hours, General queries - 24 hours

Channel Members

  • Engineering leads/heads from your team

  • Selected developers (power users)

  • Typo support engineers

Support Protocol

  • Use thread replies for issue discussions

  • Pin important announcements and resources

  • Standardized issue reporting format:

    Issue Type: [Bug/Question/Feature Request]
Priority: [High/Medium/Low]
Description:
Steps to Reproduce:

New Releases

  • Feature announcements in the channel

  • Optional demo sessions on request

  • Beta testing opportunities for power users

Available support resources and documentation links are pinned to the channel.

PreviousDevExNextEngineering Metrics

Last updated 3 months ago

Here’s a detailed guide to managing access of your team members