Lesson 3: Establishing Team and Technical Agility

Question 1

Build cross-functional Agile Teams

Answer 1

Agile Teams are cross-functional, self-organizing entities that can define, build and test, and where applicable, deploy increments of value.

• Optimized for communication and delivery of value
• Deliver value every 2 weeks
• 2 Specialty roles:
  
  • Scrum Master
  • Product Owner

Question 2

Teams execute Iterations with

Answer 2

Scrum and Kanban

Question 3

Scrum

Answer 3

Is built on transparency, inspection, adaptation, and short learning cycles

Question 4

Kanban

Answer 4

Visualizes and optimizes the flow of work through the system

Question 5

Agile Business Teams foster

Answer 5

true Business Agility

Question 6

Roles in the Agile Team

Answer 6

Agile Team
Scrum Master
Product Owner

Question 7

Agile Team

Answer 7

• Create and refine User Stories and acceptance criteria
• Define, build, test, and deliver stories
• Develop and commit to team PI Objectives and Iteration plans
• Five to eleven members

Question 8

Scrum Master

Answer 8

• Coaches the Agile Team and facilitates team meetings
• Removes impediments and protects the team from outside influence
• Attends scrum of scrum meetings

Question 9

Product Owner

Answer 9

• Defines and accepts Stories
• Acts as the Customer for developer questions
• Works with Product Management to plan Program Increments (PI)

Question 10

Build quality in

Answer 10

“You can’t scale crappy code (or hardware, or anything else).”

• Ensure that every increment of the Solution reflects quality standards
• Is required for high, sustainable development velocity
• Many practices apply to every team, whether business or technology
  
  • Establish flow
  • Peer review and pairing
  • Collective ownership and standards
  • Automation
  • Definition of done

Question 11

Built-in Quality practices for technology-focused teams

Answer 11

• Include software quality practices (most inspired by XP) like, Agile testing, behavior-driven development, test-driven development, refactoring, and code quality, Agile structure
• Support hardware quality and exploratory, early iterations, frequent system-level integration, design verification, Model-Based Systems Engineering (MBSE), and Set-Based Design

Question 12

Agile Release Trains (ARTs) continuously deliver value

Answer 12

• A virtual organization of 5-12 teams (50 - 125+ individuals)
• Synchronized on a common cadence, a Program Increment (PI)
• Aligned to a common mission via a single Program Backlog

Question 13

Roles on the Agile Release Train

Answer 13

Release Train Engineer
System Architect/ Engineer
Business Owners
Product Management
System Team

Question 14

Release Train Engineer

Answer 14

Acts as the chief Scrum Master for the train.

Question 15

System Architect/ Engineer

Answer 15

Provides architectural guidance and technical enablement to the teams on the train.

Question 16

Business Owners

Answer 16

Are key stakeholders on the Agile Release Train.

Question 17

Product Management

Answer 17

Owns, defines, and prioritizes the Program Backlog.

Question 18

System Team

Answer 18

Provides processes and tools to integrate and evaluate assets early and often.