Agile Software Development: Agile Metrics

Question 1

Swarm

Answer 1

Swarm: An agile technique where entire team collaboratively focuses on one user story or problem

Question 2

Escaped Defects

Answer 2

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

Question 3

Agile Metrics

Answer 3

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

Question 4

Gold plating

Answer 4

adding features not asked for by the customer to drive up the cost

Question 5

downside of metrics

Answer 5

Only a snapshot

It May be misleading when lacking context

Question 6

Traditional metrics vs Agile metrics

Answer 6

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

Question 7

Important metrics SCRUM

Answer 7

Burn Down Chart
Burn Up Chart
Velocity Chart
Committed vs. Delivered chart

Question 8

Important Metrics KANBAN

Answer 8

Lead time

Cycle time

Question 9

What makes Agile metrics special?

Answer 9

Focuses on tracking value DELIVERED to the customer

Question 10

Purpose of a scope line in the burn-up chart?

Answer 10

forecasts the initial scope

Shows scope creap

Question 11

Difference between burning down and burn up chart

Answer 11

Burnup charts show work already completed and includes a scope line.

Question 12

Velocity chart

Answer 12

Shows amount of story points completed per sprint

Question 13

How is Velocity calculated

Answer 13

Average = Total number of story points / Sprints completed

Needs a minimum of 3 - 5 sprints

Question 14

Committed vs Delivered chart

Answer 14

Contrasts commited and delivered work per sprint

Question 15

Ideal Goal of Committed vs Delivered Chart

Answer 15

Delivered is within 10% of committed

Question 16

If SCRUM is about managing sprints then KANBAN is about …

Answer 16

managing the flow, by removing bottlenecks

Question 17

Cycle time

Answer 17

The average time it takes for work goes from WIP column to the TEST column in KANBAN chart

Time spent ACTIVELY working on software

Question 18

LEAD TIME

Answer 18

The average time it takes for an item of work placed in the Backlog column to move to the Done column

Question 19

Code Coverage

Answer 19

Code Coverage: shows a % of lines of code that have a corresponding test that validates that line of code

Question 20

How to improve flow in Kanban

Answer 20

Reduce WIP (cycle time)
Reduce Lead Time

Question 21

Kanban time to completion

Answer 21

Time to completion = Lead Time * Number of items in Backlog

Question 22

SLA

Answer 22

Service Level Agreement

Question 23

Problems with escaped defects

Answer 23

MOre costly to fix after release

It may be dangerous to customer

Question 24

Calculate escaped defects

Answer 24

Escaped Defects = Bugs in PRODUCTION / total Bugs

Question 25

Strategies for minimizing escaped defects

Answer 25

``` 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) ```

Question 26

TTD

Answer 26

Test-Driven Development

Question 27

TTD Process

Answer 27

1. New User Story 2. Write Test Cases: Test will fail, as no code has been written yet 3. Write Code to pass the test 4. Refactor/Optimize Code 5. User Demonstration

Question 28

Code Coverage

Answer 28

Code Coverage= = Lines of Code / Automated tests for each line of code

Question 29

Why use TDD?

Answer 29

Forces discipline Ensures code is tested Automates testing Makes Regression testing easier

Question 30

When would it be appropriate to end a Sprint Early?

Answer 30

When doing exploratory work of an unknown issue/technology at the beginning of a project

Question 31

Watermelon Project Management Status

Answer 31

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