Please enable JavaScript.
Coggle requires JavaScript to display documents.
Métricas Agile (Team organization (Measuring meeting times, Stick to…
Métricas Agile
Team organization
Measuring meeting times
Stick to standard time limits for Scrum meetings
Scheduling short meetings with the developers to listeng to their problems
New features
Production
Measuring number of new feature completion
Number of cards that the team places in the done section of their Kanban board
Are they delivered on time?
Burndowns
measure how many development tasks are completed over time
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
Cycle time
The time taken to drive a change in the application and deliver it into production
Lead Time
The duration between the formation of an idea and its delivery
Fix rate
The time taken to open and close a specific production issue
hitting release dates.
Quality
Code review
Number of peer code review
Defects
how frequently defects are raised and how long they remain unresolved.
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
Customer satisfaction
Number of toughpoints with clients
How quickly your software improves business results.
Lower cost
Less cycle time
Boost earnings