Team Metrics for Agile Software Development

Presentation to the Triangle Qlik User Group on collecting & presenting metrics for agile software development teams at scale

Transcript

1. — — 10/11/2017 Team Metrics for Agile Software Development Vinay Augustine & Will Snipes
2. — Overview October 19, 2017 Slide 2 ABB Present in Billion in revenue Formed in employees countries merger of Swedish ASEA (1883) and Swiss BBC (1891)
3. — A global leader in power & automation technologies October 19, 2017 Slide 3 ABB Present in Billion in revenue Formed in employees countries merger of Swedish ASEA (1883) and Swiss BBC (1891)
4. — Team Metrics in Qlik Sense October 19, 2017 Slide 4 Vinay Augustine (CR) • Test automation • Developer productivity Will Snipes (CR) • Defining R&D metrics • Analytics for R&D metrics Pat Ryan (GA) • Director of product development product excellence • Monitors & improves GA development practices John Hudepohl (SDIP) • Company-wide software metrics portal • Developer training Corporate Research (CR) • Develop new & emerging technologies • Exploit synergies between disparate businesses • Facilitate knowledge sharing Grid Automation (GA) • Produces power grid management software • Globally distributed • Agile SAFe Framework Software Development Improvement Program (SDIP) • Global program • Improve software development across ABB Corporate Research + Business Operational Excellence
5. — • Software engineering data collected in different silos • TFS • Github • VersionOne • Jenkins • Salesforce • Limited reporting tools • Pre-built analysis in each tool • Manual collection & analysis via Excel The problem
6. — The problem • Manual reporting is error-prone • Limited connections between multiple data sources • Agile teams change slowly • No cross-team sharing • Software engineering data collected in different silos • TFS • Github • VersionOne • Jenkins • Salesforce • Limited reporting tools • Pre-built analysis in each tool • Manual collection & analysis via Excel
7. — • Automatic aggregation from all data sources • Easy data connections via associative model • Centralized web-based reporting • Updated nightly Developer work items Use case The Team Metrics Qlik Application Customer reports Source code Tests Builds
8. — Demonstration October 19, 2017 Slide 8 Team Overview
9. — Demonstration October 19, 2017 Slide 9 Current Sprint
10. — Demonstration October 19, 2017 Slide 10 Historical Summary
11. — Demonstration October 19, 2017 Slide 11 Cycle Time Detail
12. — Demonstration October 19, 2017 Slide 12 Unplanned Work Detail
13. — Demonstration October 19, 2017 Slide 13 Monthly Product Quality Indicators
14. — Entire Solution
15. — There were several lessons learned during the rollout of the QSMP related to stakeholder interaction, infrastructure/process, design considerations, and project organization. We learned to engage business units with metric success stories. We followed an agile iterative development process with a two-week delivery cycle. We had part-time metric coordinators within the business units. We learned that we needed to dedicate servers for both development and production. We shortened refresh times by implementing automated incremental data loading. We track how much and when people in each business unit are using it. When designing dashboards, we incorporated features that provide • fast visualization rendering and filtering, • increase interactivity, • improve ease of navigation, • drill-down capability, • navigation buttons. Lessons Learned October 19, 2017 Slide 15