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

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

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

Contents

History -2012

Organizational change 2012

Release Planning Days 2014-

Taking the Market

Beginning 1989

Organic Growth

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

Annual major releases

Projects (a lot of)

Variable scope and schedule

Growth Pain

Contents

History -2012

Organizational change 2012

Release Planning Days 2014-

Structure and Processes

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)

Team Structure

How we make Releases Now

Stabilization Period

Different Levels of Abstraction

Splits down into

SprintsIs part of a

larger entity

Aiding the teams

• (Scrum of Scrums)

• Scrum Master Community of Practice

• Test Community

• System Team (tools)

Tools are important

Split work between Product Owner and Manager

5/2013

Product Manager

Release Train Engineer & Chief Scrum Master

Contents

History -2012

Organizational change 2012

Release Planning Days 2014-

Increasing Transparency

Release Planning

Whole company together

Event called Release Planning Day

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

Conclusions & What works

•Co-located teams

•Dedicated POs

• Increasing Transparency

•Working together

Enjoy Working Together!

#scanagile #NAPA

@ToivoVajeThank You!