Métricas Agile
Team organization
New features
Production
Are they delivered on time?
Burndowns
Quality
Measuring meeting times
Code review
Defects
how frequently defects are raised and how long they remain unresolved.
Commit-to-Deploy Time (CDT)
When a developer is done writing the code, but you stil have automated tests, QA and/or User Acceptance Testing, and the actual deployment/release process
Customer satisfaction
Number of toughpoints with clients
Stick to standard time limits for Scrum meetings
How quickly your software improves business results.
Lower cost
Less cycle time
Boost earnings
Cycle time
Lead Time
Fix rate
measure how many development tasks are completed over time
The time taken to drive a change in the application and deliver it into production
The time taken to open and close a specific production issue
The duration between the formation of an idea and its delivery
Number of peer code review
Measuring number of new feature completion
Scheduling short meetings with the developers to listeng to their problems
Number of cards that the team places in the done section of their Kanban board
hitting release dates.
Monitoring
Measuring time spent on a subtask
Time Logs versus Historical Data
track historical time records for story point levels (e.g., the median 2-point user story takes n hours from birth to death).
Measuring time spent on a subtask