Upload
jeyaprakash-rajaram-jp
View
62
Download
0
Tags:
Embed Size (px)
Citation preview
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
in.linkedin.com/pub/jeyaprakash-rajaram-
jp/8/330266/en
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
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
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
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
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
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
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)
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