www.napa.fi Journey From Project Organization to a SAFe Company Toivo Vaje @ToivoVaje Manager, Software Releases NAPA Technology #NAPA #SAFe
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
w w w . n a p a . f i
Journey From Project Organization to
a SAFe Company
Toivo Vaje
@ToivoVaje
Manager, Software Releases
NAPA Technology
#NAPA
#SAFe
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
175 EMPLOYEES
© NAPA
25 YEARS
Software 3DEVELOPMENT
SITES
w w w . n a p a . f i
Me
• Master of Science (Physics)
• 7+ 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
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)
Split work between Product Owner and Manager
5/2013
Product Manager
Release Train Engineer
Contents
History -2012
Organizational change 2012
Release Planning Days 2014-
Increasing Transparency
w w w . n a p a . f i
9-9:15 Business Context
9:30-10:30 Product Roadmaps
10:30-10:45 Planning Process and Requirements
10:45-12 Team Breakout #1
12-13 Lunch
13-14 Draft Plan Review
14-15:30 Team Breakout #2 + Problem Solving & Adjustments
15:30-> Final Plan Review
Vote of Confidence & Plan rework if needed
Release Planning Day Rough Schedule
5/2014
Common event
Release Planning
• Whole company together
• Event called Release Planning Day
»Why?
*see http://www.scaledagileframework.com
Shared Vision
Linking Abstraction Levels
Communication
Conclusions & What works
•Co-located teams
•Dedicated POs
• Increasing Transparency
•Working together
Enjoy Working Together!
w w w . n a p a . f i
Thank You
@ToivoVaje
+358-41-5372657
Manager, Software Releases
NAPA Technology
Related Documents
