03 : Establishing Team and Technical Agility

1. A virtual organization of 5 -12 Teams (50-125+ individuals) Sync on a common cadence- PI Aligned to a common mission via a single Program Backlog

2. Intro/Recap

3. 01 - Prepare to form cross-functionnal Agile teams

3.1. De 5 à 11 Personnes (Regular scrum team size+2) Avec 2 rôles : SM et PO Iteration : 2 weeks for PI objectives and Iteration goals One Kanban : A WIP(Work In Progress) limited + JIT (Just In Time)

3.1.1. Iteration and Execution

3.1.2. Kanban : Minimiser le delay et augmenter le JIT

3.2. Extend SAFe practices to Business : What Pair programming for RH ?

4. 03 - Organizing Agile Release Trains around the flow of value : ARTs

4.1. ARTs are cross-functionnal Teams on ARTs are Organized for flow To deliver Value continuously

4.1.1. Ideal Ratio 9 teams classic (End user value) 1 complicated subsystem team 1 platform team 1 - Enabling team

4.2. ROLES : Release Train Engineer System Archi/Engineering Business Owner Product Management The System Team

4.2.1. ARTs are cross functional & Teams on it are organized for Flow

4.2.2. Roles

4.3. Next Lesson

5. Software : TDD,BDD,Testings, Lean UX

6. 02 - Describe Built-In Quality practices

6.1. Ensure the following are applied properly : Establising Flow, Peer review and pairing, Collective ownership and standards, Automation, DOD

6.1.1. Hardware : Exploratory, Early iterations, Design Verification Model-Based Systems Engineering (MBSE)...