napa agile story: from zero to hero in two years

22
www.napa.fi NAPA Agile Story: From Zero to Hero in Two Years Toivo Vaje @ToivoVaje Manager, Software Releases NAPA Technology #NAPA #scanagile

Upload: toivo-vaje

Post on 15-Jul-2015

240 views

Category:

Software


1 download

TRANSCRIPT

Page 1: NAPA Agile Story: From Zero to Hero in Two Years

w w w . n a p a . f i

NAPA Agile Story: From Zero to

Hero in Two Years

Toivo Vaje

@ToivoVaje

Manager, Software Releases

NAPA Technology

#NAPA

#scanagile

Page 2: NAPA Agile Story: From Zero to Hero in Two Years

w w w . n a p a . f i

Context: NAPA IN NUMBERS

95%OF SHIPS BUILT ANNUALLY

ARE DESIGNED BY OUR

CUSTOMERS USING NAPA

9COUNTRY OFFICES

WORLDWIDE

185 EMPLOYEES

© NAPA

>25 YEARS

Software 3DEVELOPMENT

SITES

Page 3: NAPA Agile Story: From Zero to Hero in Two Years

w w w . n a p a . f i

Me

• Master of Science (Physics)

• 8+ years in Software Development

• Developer,

Scrum Master,

Coach,

Process Owner,

Value Chain Owner,

Manager

• Jack of All Trades

• Optimize the whole

• @ToivoVaje

Page 4: NAPA Agile Story: From Zero to Hero in Two Years

Contents

History -2012

Organizational change 2012

Release Planning Days 2014-

Taking the Market

Page 5: NAPA Agile Story: From Zero to Hero in Two Years

Beginning 1989

Page 6: NAPA Agile Story: From Zero to Hero in Two Years

Organic Growth

http://www.napa.fi/About-NAPA/Background

Page 7: NAPA Agile Story: From Zero to Hero in Two Years

Annual major releases

Projects (a lot of)

Variable scope and schedule

Growth Pain

Page 8: NAPA Agile Story: From Zero to Hero in Two Years

Contents

History -2012

Organizational change 2012

Release Planning Days 2014-

Structure and Processes

Page 9: NAPA Agile Story: From Zero to Hero in Two Years
Page 10: NAPA Agile Story: From Zero to Hero in Two Years

NAPA Technology 2/2012

Finland

India

Romania

Software

Development

Process

nn

Release

Team

nn

Platform &

Architecture

nn

Log / Voyage

Nn

Nn

Nn

Nn

Nn

Ship

Model

Nn

Nn

Nn

Nn

Nn

Nn

Statutory

Nn

Nn

Nn

Nn

Nn

Nn

Nn

Nn

Nn

Steel

Nn

Nn

Nn

Nn

Nn

Nn

Nn

Nn

Nn

Hydro

Nn

Nn

Nn

Nn

Nn

Reporting &

Office

nn

nn

nn

nn

Ship

Model

nn

Statutory

nn

Steel

nn

Hydro

Nn

Report. &

Office

nn

Log / Voyage

Nn

Product Owners

(in Business Units)

Page 11: NAPA Agile Story: From Zero to Hero in Two Years

Team Structure

Page 12: NAPA Agile Story: From Zero to Hero in Two Years

How we make Releases Now

Stabilization Period

Page 13: NAPA Agile Story: From Zero to Hero in Two Years

Different Levels of Abstraction

Splits down into

SprintsIs part of a

larger entity

Page 14: NAPA Agile Story: From Zero to Hero in Two Years

Aiding the teams

• (Scrum of Scrums)

• Scrum Master Community of Practice

• Test Community

• System Team (tools)

Page 15: NAPA Agile Story: From Zero to Hero in Two Years

Tools are important

Page 16: NAPA Agile Story: From Zero to Hero in Two Years

Split work between Product Owner and Manager

5/2013

Page 17: NAPA Agile Story: From Zero to Hero in Two Years

Product Manager

Page 18: NAPA Agile Story: From Zero to Hero in Two Years

Release Train Engineer & Chief Scrum Master

Page 19: NAPA Agile Story: From Zero to Hero in Two Years

Contents

History -2012

Organizational change 2012

Release Planning Days 2014-

Increasing Transparency

Page 20: NAPA Agile Story: From Zero to Hero in Two Years

Release Planning

Whole company together

Event called Release Planning Day

http://agilehope.blogspot.com/2014/05/release-planning-day.html

Page 21: NAPA Agile Story: From Zero to Hero in Two Years

Conclusions & What works

•Co-located teams

•Dedicated POs

• Increasing Transparency

•Working together

Page 22: NAPA Agile Story: From Zero to Hero in Two Years

Enjoy Working Together!

#scanagile #NAPA

@ToivoVajeThank You!