Skip to content
Dev Management Guide (public)
  • Pages
    • Welcome
    • Introduction
    • Blog
      • Why do we need a team lead?
    • Tech Manager Guide
      • Intro
      • Speak to your people
      • icon picker
        Measure important stuff
      • New developer in the team
      • Performance Papers ;)
    • Product Management
      • Test Free
      • Release planning
    • Recruiting
      • Job interview
    • Organisaton
      • Professioncy Level
        • Junior Developer
        • Senior Developer
      • Company
        • CEO
        • CFO
        • Team Lead
    • Library
      • Velocity
      • Effort Expenditure
      • FTE
      • PERT
      • RACI
      • CAPEX
      • OPEX
      • KPI
    • ACME Development
      • AREA
      • DB
        • Teams
        • People
        • Sprint
        • Product
        • RACI
        • Role
        • Performance
        • Backlog
      • Performance
      • Board
    • KIRA
Dev Management Guide (public)
/
/
Measure important stuff
Share
Explore

Measure important stuff

Build a system of reliable and meaningful figures for your team

Introduction

Or painful real-world experience
I have managed many different teams in the last 20 years. Most of them are Scrum or Kanban-driven and can really create a

Figures you need


1. Time Tracking

The most teams you know, had already a time tracking in place. They tracked time spent on conception, development and testing of each ticket. This information creates a steady base for future planning, but some important information is still missing.
Types of tickets

Product



Customer Support


Sales Activities

Support of a your sales team without a paid customer contract.
technical presentation, visits of trade fair
setting up and mandaging a conference room pilot of our product

Sprint by sprint measurement


Gallery
 
Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.