ATAGG2015 - S R V subrahmaniam

1. Building Quality inBuilding Quality in
The SAFe way
Agile Testing Alliance Global
Gathering
2015 BENGALURU Oct.
9
S R V Subrahmaniam
PMP, ACP, CSP
SAFe Program Consultant
(SPC)
Altimetrik

2. When Scaling, the context is different
CONTEXT
7-9 > 100sTeam Size
Co-located GlobalGographic Distribution
Single Division Multi-departmentOrganizational Distribution
Less or none Life CriticalCompliance
Slide 2
Single team Agile at Scale
Straightforward ComplexDomain Complexity
Straightforward Multi-platform / complexTechnical Complexity
Less or none Upstream / DownstreamIntegration needs
Homogenous Heterogenous mixEnvironment complexity

3. Scaled Agile Framework™ Big Picture
Slide copied from Scaled Agile Framework public slidedeck

4. Module / Component
teams
SAFe
▸ Cross-functional Agile Teams deliver working software every two weeks
▸ Scrum roles and project management practices, XP-inspired technical
practices;
Slide 4
Slide adapted from Scaled Agile Framework public slidedeck

5. Program Level
SAFe
▸ Cross-functional teams-of-agile-teams deliver working system increments every two
weeks
▸ Operate with common Vision, architecture and UX guidance
▸ Collaborate, align, and adapt with face-to-face planning and retrospectives
Slide 5
Slide adapted from Scaled Agile Framework public slidedeck

6. Definition of Done applies at different levels
SAFe
Program level Definition of Done
• Features completion
• End-to-end system tests
• Non-functional tests
System team helps meet DoD
• Set-up and maintain dev & test
infrastructure
• System Integration
• End-to-end tests and performance
testing
• System demo
S
y
n
c
h
r
o
n
i
z
a
t
i
o
Slide 6
Team level Definition of Done
• User stories completion
• Regression at Module / Component level
• Module specific performance tests
Teams integrate their work frequently within the Iteration n
&
c
a
d
e
n
c
e

7. Optimize Program
Velocity
Quality
Slide 7
Image source: Scaled Agile Framework website

8. Continous Integration at different stages
may be employed
Copy from Mainline
Test
Test
Develop
Test & Stable
Code
Merge
TECHNICAL
PRACTICES
Slide 8
Marge to Mainline
Develop
Merge Code
Developers
merge code
to local team
branch
Different
teams merge
their code to
mainline
branch
Stable code at Program Level
Source: http://damonpoole.blogspot.in/2008/01/multi-stage-continuous-integration-part_05.html

9. This pattern can repeat at multiple release trains too
SAFe
Large programs can be composed of multiple ARTs
Slide 9

10. Summary of deployed
practices
Quality
Frequent integration
Between module and program branches
Tooling & Automation
Optimized infrastructure for
quicker turnaround times
Early system tests
Move towards compliance
with Program DOD
Slide 10
Code Quality
Common program
understanding on
clean code practices
Program level Guidance
Guidance on tooling and
automation frameworks
Specialists at Program level
Specialists for NFR, domain
and compliance tests

11. QUESTIONS &
ANSWERSANSWERS
Go ahead. Don‘t hesitate.

12. Let us stay in touch!
CONTACT
Twitter
twitter.com/srv_subbu
LinkedIn
ln.linkedin.com/in/srvsubbu
E-Mail
Slide 12
E-Mail
Srv.subbu@yahoo.in

13. THANK
YOUYOU
For your attention!