building quality in the safe way
TRANSCRIPT
Building Quality inThe SAFe way
Agile Testing Alliance Global Gathering
2015 BENGALURU Oct.9
S R V Subrahmaniam PMP, ACP, CSP
SAFe Program Consultant (SPC)
Altimetrik
Slide 2
When Scaling, the context is different
CONTEXT
Single team Agile at Scale
7-9 > 100sTeam Size
Co-located GlobalGographic Distribution
Single Division Multi-departmentOrganizational Distribution
Less or none
Life CriticalCompliance
Straightforward
ComplexDomain Complexity
Straightforward
Multi-platform / complexTechnical Complexity
Less or none
Upstream / DownstreamIntegration needs
Homogenous
Heterogenous mixEnvironment complexity
Scaled Agile Framework™ Big Picture
Sl ide copied from Scaled Agi le Framework publ ic s l idedeck
Slide 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;
Sl ide adapted from Scaled Agi le Framework publ ic s l idedeck
Slide 5
Program LevelSAFe
▸ 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
Sl ide adapted from Scaled Agi le Framework publ ic s l idedeck
Slide 6
Definition of Done applies at different levelsSAFe
Team level Definition of Done• User stories completion• Regression at Module / Component level• Module specific performance tests
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
Teams integrate their work frequently within the Iteration
Synchronization & cadence
Slide 7
Optimize Program Velocity
Qual ity
Image source: Scaled Agi le Framework website
Moderate the team velocities for optimizing the program velocity
Slide 8
Continous Integration at different stages may be employed
Copy from Mainline
Marge to Mainline
TestTest
Deve
lop
Test & Merge
Stable Code
Merge
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
TECHNICAL PRACTICES
Slide 9
This pattern can repeat at multiple release trains too
SAFe
Large programs can be composed of multiple ARTs
Slide 10
Summary of deployed practices
Qual ity
Frequent integrationBetween module and program branches
Tooling & AutomationOptimized infrastructure for
quicker turnaround times
Code QualityCommon program understanding on
clean code practices
Program level Guidance Guidance on tooling and automation frameworks
Early system testsMove towards compliance
with Program DOD
Specialists at Program levelSpecialists for NFR, domain
and compliance tests
QUESTIONS &ANSWERS
Go ahead. Don‘t hesitate.
Slide 12
Let us stay in touch!CONTACT
Twittertwitter.com/srv_subbu
LinkedInln.linkedin.com/in/srvsubbu
THANKYOUFor your attention!