1 / 15

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

Need 4 Speed Leverage new metrics to boost your velocity without compromising on quality. 2013 Agile Conference. Outline. Introduction The Challenges The ALI Concept Using The ALI Model. Hewlett Packard (HP) . Over 3000 developers globally distributed.

faye
Download Presentation

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

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Outline • Introduction • The Challenges • The ALI Concept • Using The ALI Model

  3. Hewlett Packard (HP) • Over 3000 developers globally distributed. • An average project size is ~100 developers.

  4. Agile project management solution • Inthis project involved over 150 developers, QA and PO distributed in Israel, Ukraine, Czech, Vietnam, China and the US.

  5. The Challenges • Collaboration • Time zones • Velocity • Dependencies&Defect resolution • Quality • From 18-24 month releasesto 2 weeks release • Readiness of Value Delivery Chain (VDC) • Not enough time

  6. The ALI Concept • The idea istheextraction of information stored in various tools and leverage a complete end to end traceability to compile new metrics and reports.

  7. Entities • 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

  8. Tools • 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

  9. Metrics • 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

  10. Build Reports • Build reports composed of the metrics

  11. Build Trends Build trends report show trends on 1. Number of outstanding defect 2. Volume of changes per user stories vs. defects. 3. Top contributors – based on LOC 4. Percentage of build success vs. failures

  12. Heat map • The report maps the application based on the structure of code in the Source Code repository.

  13. Root cause analysis report The report list following related entities and activities per defect 1. Related user stories 2. Tests 3. Latest code changes related to the user stories

  14. Using The ALI Model • Dev Manager • Quality Assurance • Developers • Operations • Marketing

  15. Conclusion • 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.

More Related