2013 Agile Conference Need 4 Speed Leverage new metrics to boost your velocity without compromising on quality.

Post on 02-Jan-2016

213 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

Transcript

2013 Agile Conference

Need 4 SpeedLeverage new metrics to boost your velocity without compromising on quality

• Introduction• The Challenges• The ALI Concept • Using The ALI Model

Outline

• Over 3000 developers globally distributed. • An average project size is ~100 developers.

Hewlett Packard (HP)

• In this project involved over 150 developers, QA and PO distributed in Israel, Ukraine, Czech, Vietnam, China and the US.

Agile project management solution

• Collaboration• Time zones

• Velocity • Dependencies & Defect resolution

• Quality • From 18-24 month releases to 2 weeks release

• Readiness of Value Delivery Chain (VDC) • Not enough time

The Challenges

• The idea is the extraction of information stored in various tools and leverage a complete end to end traceability to compile new metrics and reports.

The ALI Concept

• Theme, Feature, User Story • Source code files and lines of code • Unit test, Functional tests, Static code analysis test,

performance test, security scan • Builds and deployments • Defects • Practitioners

Entities

• Source Code Management (SCM) • Build System and Continuous Integration tools • Unit test tools, Static Code Analysis and Functional testing

tools • Code coverage tools • Integrated Development Environment tools (IDE) • Agile project management and issues tracking tools

Tools

• Line of Code (LOC) per user story • Number of Files (NOF) per user story• Number of developers\contributors (NOC) per feature\theme. • Unit test coverage per user story• Unit Test success per user story• No of defects per user story

Metrics

Build Reports• Build reports composed of the metrics

Build TrendsBuild trends report show trends on1. Number of outstanding defect 2. Volume of changes per user stories vs. defects.3. Top contributors – based on LOC4. Percentage of build success vs. failures

Heat map• The report maps the application based on the structure of code

in the Source Code repository.

The report list following related entities and activities per defect1. Related user stories2. Tests 3. Latest code changes related to the user stories

Root cause analysis report

• Dev Manager• Quality Assurance• Developers• Operations• Marketing

Using The ALI Model

• It shares the additional analytics and metrics that allowed HP to enable cross time zones collaboration and alignment through transparency and provides insights into quality and risk.

Conclusion

top related