Building quality in the SAFe way
•Download as PPTX, PDF•
0 likes•466 views
The document discusses the Scaled Agile Framework (SAFe) for building quality when scaling Agile development. SAFe addresses the different context of scaling from single teams to hundreds of teams. It describes operating cross-functional Agile teams and teams-of-teams at the module/component and program levels with common vision, architecture and user experience guidance. SAFe also defines levels of "Definition of Done" and promotes practices like continuous integration, automated testing, code quality standards, and early system testing to optimize program velocity and quality when scaling Agile.
Report
Share
Building quality in the SAFe way
- 1. Building 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. 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
- 3. Scaled Agile Framework™ Big Picture
- 4. 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; Slide adapted from Scaled Agile Framework public slidedeck
- 5. Slide 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 adapted from Scaled Agile Framework public slidedeck
- 6. Slide 6 Definition of Done applies at different levels SAFe 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 S y n c h r o n i z a t i o n & c a d e n c e
- 7. Slide 7 Optimize Program Velocity Quality Image source: Scaled Agile Framework website Moderate the team velocities for optimizing the program velocity
- 8. Slide 8 Continous Integration at different stages may be employed Copy from Mainline Marge to Mainline Test Test Develop 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
- 9. Slide 9 This pattern can repeat at multiple release trains too SAFe Large programs can be composed of multiple ARTs
- 10. Slide 10 Summary of deployed practices Quality Frequent integration Between module and program branches Tooling & Automation Optimized infrastructure for quicker turnaround times Code Quality Common program understanding on clean code practices Program level Guidance Guidance on tooling and automation frameworks Early system tests Move towards compliance with Program DOD Specialists at Program level Specialists for NFR, domain and compliance tests
- 11. QUESTIONS & ANSWERS Go ahead. Don‘t hesitate.
- 12. Slide 12 Let us stay in touch! CONTACT Twitter twitter.com/srv_subbu LinkedIn ln.linkedin.com/in/srvsubbu E-Mail Srv.subbu@yahoo.in