The document discusses the imperatives of tools and engineering practices for scaling agile. It notes that when 10-15% of team members are not co-located, communication gaps can occur in requirements engineering, dependency management, integration, and more. Two types of tools are identified to help resolve these issues: collaboration tools and development accelerators. Specific tools and practices are recommended, including using video conferencing for ceremonies, application lifecycle management tools for planning, and development accelerators to break problems and accelerate code work. Benefits of adopting the right tools include increased throughput, velocity, test coverage, and more, as well as decreased cycle time, defects and failures.

1. Slide 1
Imperatives of Tools and Engineering Practices - while
scaling
Jeyaprakash Rajaram PMP, PMI-ACP, CSM, CSP
Co- organizer ISEC Chennai Chapter
14- March -2015 , Chennai
jeyaprakash.rajaram@gmail.com
in.linkedin.com/pub/jeyaprakash-rajaram-
jp/8/330266/en

2. Slide 2
Agile Principles

3. Slide 3
Agile Principles while Scaling
How the below facts are possbile while Scaling
 Face to Face communication
 Frequent Delivery
 Sync-up between Business and Scrum team
 Architecture and Technical excellance

4. Slide 4
Minimum 10%-15% of Scrum team members and stakeholders are
not co-located.
Communication Gaps in Requirements Engineering
Gaps in Dependency management
Issues while Code Integration /Build/ Packaging & Deployment
Lack of Automations but more relying on manual testing
Lack of Release Co-ordination and Look-ahead Planning
Observations while scaling

5. Slide 5
Two types of Tools - To resolve the previous
observations

6. Slide 6
Collaboration Approach – While Scaling (1)
Mandate the use of video conferencing or webcam for agile ceremonies. Start
mimicing face to face like environment

7. Slide 7
Collaboration Tools – While Scaling(2)
1. Application Life Cycle Management Tools - A Right balance between Concept and Scrum team (ALM – IBM
RRC, RTC, Rally, Version one, Jira)
2. Concept team: At Product Portfolio needs to be at least one release ahead of Scrum team by Logging the
artifacts in ALM Tools
3. Scrum Team: Set proper sprint level look ahead by Logging the artifacts in ALM Tools
Imbalance between Concept teams and Scrum team
1. Late Requirements intake by Product Portfolio
2. Lack of Look ahead Planning
3. Lack of Capacity based intake
4. Poor Dependency management

8. Slide 8
Engineering Practices – While Scaling
http://en.wikipedia.org/wiki/Theory_of_constraints
Break the constraints i.e. developers are the major constraints - a water fall way of perception will
be diluted by right engineering practices, involvement of testing and concept team

9. Slide 9
Development Accelerators – While Scaling
1. Break the day to to day problems and accelerate
your development by right tools in Code,
Build,Test, Deploy space
2. Practice single program level view for – build
Failures, Code Coverage, Code Quality Metrics
3. Be Pracmatic while implementing the Tools

10. Slide 10
Directions towards betterment - while scaling
Constant Inspect
and Adapt based on
Tools Data in more
Pracmatic way(6)
ALM usage for right
balance between
product portfolio
and scrum teams
(2)
Use of Development
Accelarators(5)
Better Collaboration
by ground rules
during Agile
ceremonies (3)
Engineering
Practices (4)
Mimic Face to Face
Communication (1)

11. Slide 11
Benefits of Right Tools Usage
Increased throughput
Increased % Test Coverage
Increased % Test automation
Increased Velocity
Increased Openness to Change
Increased Code Commits / day
Reduced Cycle time
Reduced Defect Density
Reduced Code complexity
Reduced Sprint Duration
Reduced % Build Failure
Reduced Debugging Time
Reduced Scope Creep

12. Thank you!