Agile Software Development: Agile Metrics Flashcards
Swarm
Swarm: An agile technique where entire team collaboratively focuses on one user story or problem
Escaped Defects
Escaped Defects: Bugs or defects in the software that have escaped Quality Assurance and reported by the customer after the software has been released. An increase in escaped defects can be a signal in issues with Software Engineering or Quality Assurance practices and processes
Agile Metrics
Visual representation of Progress
- Tells the story as it unfolds
- Live and up to date
- Volumes of information at a glance
- Drive team decisions
- Drive management decisions
- Allows teams to find and correct problems earlier
- helps management decide when the team needs a course correction
Gold plating
adding features not asked for by the customer to drive up the cost
downside of metrics
Only a snapshot
It May be misleading when lacking context
Traditional metrics vs Agile metrics
Agile metrics focus on:
Outcomes not outputs:
- Outcomes measure the value the work is providing to the customer
- focuses on completion: 98% is not done!,
- Ouputs measures the teams effort instead, anything has value, even if it doesn’t work, Gives credit for work in progress. SLOC
Important metrics SCRUM
Burn Down Chart
Burn Up Chart
Velocity Chart
Committed vs. Delivered chart
Important Metrics KANBAN
Lead time
Cycle time
What makes Agile metrics special?
Focuses on tracking value DELIVERED to the customer
Purpose of a scope line in the burn-up chart?
forecasts the initial scope
Shows scope creap
Difference between burning down and burn up chart
Burnup charts show work already completed and includes a scope line.
Velocity chart
Shows amount of story points completed per sprint
How is Velocity calculated
Average = Total number of story points / Sprints completed
Needs a minimum of 3 - 5 sprints
Committed vs Delivered chart
Contrasts commited and delivered work per sprint
Ideal Goal of Committed vs Delivered Chart
Delivered is within 10% of committed
If SCRUM is about managing sprints then KANBAN is about …
managing the flow, by removing bottlenecks
Cycle time
The average time it takes for work goes from WIP column to the TEST column in KANBAN chart
Time spent ACTIVELY working on software
LEAD TIME
The average time it takes for an item of work placed in the Backlog column to move to the Done column
Code Coverage
Code Coverage: shows a % of lines of code that have a corresponding test that validates that line of code
How to improve flow in Kanban
Reduce WIP (cycle time) Reduce Lead Time
Kanban time to completion
Time to completion = Lead Time * Number of items in Backlog
SLA
Service Level Agreement
Problems with escaped defects
MOre costly to fix after release
It may be dangerous to customer
Calculate escaped defects
Escaped Defects = Bugs in PRODUCTION / total Bugs
Strategies for minimizing escaped defects
Track bugs by the environment Establish a "Bug Bounty" to reward team members for finding bugs Increase the number of testers Implement Code Standards Enforce standards with Code Reviews Introduce Test Driven Development (TDD)
TTD
Test-Driven Development
TTD Process
- New User Story
- Write Test Cases: Test will fail, as no code has been written yet
- Write Code to pass the test
- Refactor/Optimize Code
- User Demonstration
Code Coverage
Code Coverage= = Lines of Code / Automated tests for each line of code
Why use TDD?
Forces discipline
Ensures code is tested
Automates testing
Makes Regression testing easier
When would it be appropriate to end a Sprint Early?
When doing exploratory work of an unknown issue/technology at the beginning of a project
Watermelon Project Management Status
A term for traditional waterfall project management when the project is showing ‘on track’ with the color green but when you look through in detail you realize the last 1% of the project finalization can take significant time. That’s why we say it’s Green on the outside, Red on the inside. Like a watermelon
