Agile Release Train

How do we split the team into Project teams?

Vertically with a mix of Dev, Tester and BA.

Experience level

Depending on complexity or Project type

Higher level structure

Lead Scrum Master

Governing SM A, B and C

Lead Tech Lead

Governing Tech leads across projects

Lead Product owner???

Forums

Community of Practices

to share

Frequent struggles

Best practices

Types

IM CoP

PM CoP

BA CoP

Dev CoP

Test CoP

Tracking and Continuous improvement

Risk assessment forum

Regular Scrum of Scrums

Regular Team and Mgmt Retrospectives

Create value days / Fedex days

STRUGGLES THAT COULD TAKE TIME.
(Give yourself time)

USM Alarming

Firewall Burns

F5 Engagements

New Project on F5?

SAD

SAD review / rework

BAU

Model: Kanban

Normal and Expedite queues

Team Structure

Devs, Testers, 1 BA (maybe), IM (shared)

Should we do it?

No. Give it out.

We shall provide consultation

Tech lead and BA's shared time

Content only

Model: Kanban

Normal and Expedite queues

Team Structure

1 BA, Devs, Testers, IM (shared)

Should we do it?

No, Give it out.

DS shall provide consultation

Tech lead, BA's shared time

Content + Component

Model : Scrum

2 week Iterations

Team Structure

BAs, Dev, Testers, IM (Shared / dedicated)

DevOps: Ops involved from start

Should we do it?

Yes

We will gain experience

Tighter control on changes

Content, Component + Platform

Model: Scrum

2 week iterations

Team Structure

BAs, Dev, Testers, IM (Shared / dedicated)

DevOps: Ops involved from start

Should we do it?

Tighter control on changes

Gain experience.

Jira for Agile Lifecycle Management

RTC for feature visibility

Bamboo for Build, continuous integration

GIT for Source control

Wiki for Document management