CS 577b: Software Engineering II

1. CS 577b: Software Engineering II Scaled Agile Framework (SAFe)

2. Schedule • 04/14 : Transition Readiness Review • 3-4pm, 4-5pm, 5-6pm (Team 9) • OHE 122 • 04/21 : Project Showcase • 15 minutes per team • Fix all bugs and complete all functionalities • TechTalk (C)USC-CSSE

3. Agile - Scrum (C)USC-CSSE

4. (C)USC-CSSE Ref: http://www.scaledagileframework.com/

5. New things in SAFe • Program Portfolio • Value Stream • Enterprise Architect and Epic Owner • Agile Release Train • Architecture Runway • System Demos • Program Increment (C)USC-CSSE Ref: http://www.scaledagileframework.com/

6. Program Portfolio • Program portfolio represent the enterprise level strategy. • Program portfolio management (PPM) works closely with program management office (PMO) to guide program execution and government (C)USC-CSSE Ref: http://www.scaledagileframework.com/

7. Program Portfolio (C)USC-CSSE Ref: http://www.scaledagileframework.com/

8. Product Roadmap https://roadmunk.com/ (C)USC-CSSE Ref: http://www.scaledagileframework.com/

9. Value Stream • is series of steps used to deliver value or a tangible result to the customer in a shortest possible lead time. (C)USC-CSSE Ref: http://www.scaledagileframework.com/

10. Value Streams (C)USC-CSSE Ref: http://www.scaledagileframework.com/

11. Value Streams (C)USC-CSSE Ref: http://www.scaledagileframework.com/

12. Enterprise Architect • Hands-on architect who defines holistic enterprise vision and initiatives to support business and technical perspectives (C)USC-CSSE Ref: http://www.scaledagileframework.com/

13. Epic Owner • Work with solution management team to split epic into value stream  features / backlogs (C)USC-CSSE Ref: http://www.scaledagileframework.com/

14. Agile Release Train • is the primary value delivery construct that is organized around value streams to deliver the product and benefits to the end user. • Key roles: Release train engineer (chief scrum master), product management team, business owners, development teams (C)USC-CSSE Ref: http://www.scaledagileframework.com/

15. Splitting large value streams • Effective train size : 50 – 125 people • Split value streams • By solution capabilities or feature • By subsystems • By customer or market segment • By value • Train should be focused on a single, primary product or solution objectives (C)USC-CSSE Ref: http://www.scaledagileframework.com/

16. Architecture Runway • refers to technological infrastructure that supports the emergent design and development of the agile implementation. • Feature team vs Enabler team (C)USC-CSSE Ref: http://www.scaledagileframework.com/

17. System Demos • is a fortnightly product demonstration from the agile release train. The demoed product is fully integrated from all teams. • CI/CD: Continuous integration & continuous deployment (C)USC-CSSE Ref: http://www.scaledagileframework.com/

18. If full integration at every iteration is too costly? • Integrating a subset of capabilities, components, or subsystems • Integrating to illustrate a particular feature, capability, or non-functional requirements • Integrating with prototypes, mock-ups, simulations • Integrating every other iteration (C)USC-CSSE Ref: http://www.scaledagileframework.com/

19. Program Increment • or an iteration is a plan-do-check-adjust learning cycle, which covers building, validating, and demonstrating the working software, and getting feedback from the stakeholders. (C)USC-CSSE Ref: http://www.scaledagileframework.com/

20. Executing the program increment (C)USC-CSSE Ref: http://www.scaledagileframework.com/

21. Scrum of Scrums • Release Train Engineer as Chief Scrum Master • Twice a week; attendance is mandatory • Status check • What did your team accomplish since the last meeting? • What will your team accomplish between now and the next meeting? • Are there any blocking issues? • Are you about to put a block on someone else’s way? (C)USC-CSSE Ref: http://www.scaledagileframework.com/