This document discusses tools that can help scale agile practices in large, distributed organizations. It introduces continuous integration as a practice to integrate work frequently through automated builds and testing. Common excuses for not implementing CI are addressed. Benefits of CI include fast feedback, collaboration, and quality. Examples of Hudson CI outputs like build statistics and test results are shown. An agile lifecycle management tool can provide visibility across multiple teams, facilitate prioritization, work distribution and decision making. Pain points of existing tools are outlined. The proposed solution centralizes requirements, project management, and development in one tool with custom views and reporting. Benefits of this agile lifecycle management tool include live dashboards, process visibility, customizability, and

1. Agile Scaling using Tools
Hedwig Baars
Head – BMUM R&D India

2. Agenda
Agile Mindset
Agile Life Cycle Information
Continuous
Integration Management Radiators
Tool

3. Continuous Integration

4. Continuous Integration Definition
“Continuous integration is a software development practice
– members of a team integrate their work frequently
– each integration is verified by an automated build
(including test)
– to detect errors as quickly as possible.”
http://martinfowler.com/articles/continuousIntegration.html

5. Top excuses for not doing CI
• We have so complex product !
• Quality Doors are preventing us to commit frequently
• We have to keep the quality in the Main branch
• Merge is too laborious and eats our bandwidth
• The tasks have too many dependencies
• Branching for features were required from us
• Risky changes must be done in a branch
• CI effort will impact our current commitments
• Our current branch strategy is working fine .Why Change?

6. Benefits with CI
• Fast feedback loop
• No hiding behind the branches
• No Big Bang at the end
• Fosters collaboration among the developers
• Confidence Booster for developers
• Quality starts with the first code written. Not a
Gatekeeper.

7. Build Statistics-Hudson CI

8. Build Time Trends – Hudson CI

9. Integrated Test Statistics-Hudson CI

10. Agile Life Cycle Management Tool
Scaling Agile Teams

11. A Scrum team
Customer
Product Owner
Scrum Master
Agile Team

12. What about the Organization ?
Customer Customer Customer Customer Customer
Unit Unit Unit Unit Unit
Technology Technology Deploy & Deploy & Deploy &
Leadership Leadership Support Support Support

13. Challenges
• How to successfully handle multiple feature development
in a large, internationally distributed organization?
• How do we Cater to :
– Prioritization
– Decision making
– Capability management
– Work distribution
– Change
– Scenario and product lifecycle handling
– Cooperation with external parties and product
management.

14. Pain Areas with existing Tools
• Lack of visibility
• Inadequate tool support
• Lack of traceability
• Not Aligned with Agile Teams

15. One solution covering all needs
Requirement definition
Centralized tool
Scrum Master
Requirement management APM
Management
Customer
Custom Views
Project management
Development

16. Advantages of ALM Tool
• Live Dashboard, no obsolete presentations
• Process visibility and traceability
• Custom tool tailored to the company process
• Customizability
• People-oriented approach
• Freedom on team level
• Bottom-up reporting (centralized information)

17. Prioritized requirements flow

18. Sprint Backlog visualization

19. Velocity Trends across teams

20. Aggregated Project Progress View

21. Automatic report generation

22. Information radiators

23. Why Is important ?
• Visualizing impediments is the first step to remove
impediments
• Docs, Ppts become obsolete data , as soon as you take out
report from live system
• Online Dash boards always gives you the current status
• Motivation for teams and stakeholders to inspect and adapt

24. Info Radiators

25. THANK YOU
www.agiletour.org