Agile Release Train

Honelako gehiago

Understanding Behaviour in Organisations

by Joerg Bauer

Daily Dashboard

by Mindomo Team

CLIL History

by Michaela Praßl

StructureFramakey.mm

by Laura Grave

Agile Release Train

Discovery

Tools

Wiki for Document management

GIT for Source control

Bamboo for Build, continuous integration

RTC for feature visibility

Jira for Agile Lifecycle Management

Types of Projects

Content, Component + Platform

Gain experience.

Model: Scrum

2 week iterations

Content + Component

Yes

Tighter control on changes

We will gain experience

DevOps: Ops involved from start

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

Model : Scrum

2 week Iterations

Content only

Tech lead, BA's shared time

DS shall provide consultation

No, Give it out.

1 BA, Devs, Testers, IM (shared)

BAU

Should we do it?

Tech lead and BA's shared time

We shall provide consultation

No. Give it out.

Team Structure

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

Model: Kanban

Normal and Expedite queues

Release Management

Time consuming (but necessary)

SAD

SAD review / rework

F5 Engagements

New Project on F5?

USM Alarming

Firewall Burns

STRUGGLES THAT COULD TAKE TIME. (Give yourself time)

Feature / Project teams

Forums

Tracking and Continuous improvement

Create value days / Fedex days

Regular Team and Mgmt Retrospectives

Regular Scrum of Scrums

Risk assessment forum

Community of Practices

Types

Test CoP

Dev CoP

BA CoP

PM CoP

IM CoP

to share

Best practices

Frequent struggles

Higher level structure

Lead Product owner???

Lead Tech Lead

Governing Tech leads across projects

Lead Scrum Master

Governing SM A, B and C

Experience level

Depending on complexity or Project type

How do we split the team into Project teams?

Vertically with a mix of Dev, Tester and BA.