Establishing Team and Technical Agility - Lesson 3

On a Role

100

Removes impediments, protects the team from outside influences and facilitates team meetings.

What is a Scrum Master _{(Lesson 3, page 95)}

200

Defines and accepts stories, acts as the Customer for developer questions, and works with Product Management to plan PI.

What is the Product Owner role. _{(Lesson 3, page 95)}

300

Creates and refines User Stories and acceptance criteria, and develops and commits to team PI Objectives and iteration plans.

What is the Agile Team. _{(Lesson 3, page 95).}

400

Owns, defines, and prioritizes the program backlog,

What is Product Management. _{(Lesson 3, page 99)}

Get On Board

100

Provides technical guidance and architectural enablement.

What is a System Architect/Engineering. _{(Lesson 3, page 99).}

200

Organization of 5-12 teams aligned to a common mission via a single Program Backlog.

What are ARTs. _{(Lesson 3, page 98)}

300

The number one rule when creating cross-functional Agile Release Trains.

What is "you won't get it right the first time."  _{(Lesson 3, page 99, noted during training)}

400

Acts as the chief Scrum Master for the train.

What is the Release Train Engineer. _{(Lesson 3, page 99)}

Got Quality?

100

You can't scale this type of code, hardware, or anything else.

What is "crappy."  _{(Lesson 3, page 96).}

200

Where the definition of 'done' is captured in Agile documentation.

What is Acceptance Criteria.  _{(Lesson 3, page. 96, noted during training).} 

300

Many practices apply to every team, whether business or technology.  Name three of the five practices associated with building quality in.  

1) Establish flow, 2) Peer review and pairing,             3) collective ownership and standard, 4) automation, 5) definition of done. _{(Lesson 3, page 96)}

400

Organize Agile Release Trains around the flow of this.

What is value.  _{(Lesson 3, page 98).}