Team & Technical Agility

Get Started. It's Free
or sign up with your email address
Team & Technical Agility by Mind Map: Team & Technical Agility

1. Scrum

1.1. Ceremonies

1.1.1. Iteration Planning -beginning

1.1.2. Stand up daily

1.1.3. Iteration Review

1.1.4. Retro

1.2. Flow

1.2.1. Kanban Optimize Visualize

1.3. Agile Team

1.3.1. atributes cross function self organised 5-11 optimized to communication

1.3.2. Roles & Responsibilites Create & Refine User stories Deliver value per iteration (2w) Define Build Test Deploy Develop and commit to team PI objective & iteration plans Special Roles SM PO

1.4. built on

1.4.1. transparency

1.4.2. Inspection

1.4.3. adoption

1.4.4. short learning cycle

2. Built in quality

2.1. Ensure every increment reflect quality standard

2.2. Required

2.2.1. high sustainable development Velocity

2.3. Business & technical team practices

2.3.1. Established flow Continuous Delivery Pipeline

2.3.2. Peer Review & Pairing

2.3.3. Collective ownership & Standard

2.3.4. DoD

2.3.5. Automation

2.3.6. technology focus team Software quality XP Practices hardware quality exploratory and early iteration frequent Model Based System Engineering Set based design design verfication

3. ART

3.1. 5-12 Agile teams (50-125+ individual)

3.1.1. Roles RTE Scrum master for train System Architect/ engineer defines the overall architecture of the system Nonfunctional Requirements (NFRs), major system elements, subsystems, and interfaces. Business Owners key stakeholders of the ART and have ultimate responsibility for the business outcomes of the train. product. management is responsible for 'what gets built,’ as defined by the Vision, Roadmap, and new features in the Program Backlog. They work with customers and Product Owners to understand and communicate their needs, and also participate in solution validation. system team assist in building and maintaining development, continuous integration, and test environments. Customer ultimate buyers of the solution

3.2. Continuous Delivery Pipeline

3.2.1. continuous exploration

3.2.2. continuous integration

3.2.3. continuous deployment

3.2.4. Release on Demand

3.3. Program Increment

3.3.1. program backlog common mission