The Roles and Responsibilities in an Agile Project and Organization
•Télécharger en tant que PPTX, PDF•
2 j'aime•2,492 vues
Presentation at Finnish project conference called Projektipäivät (Project Days) 2014. Going through topics related to how we have implemented Agile at scale at NAPA. (Minimal amount of text, so not sure how this works just as slides)
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à The Roles and Responsibilities in an Agile Project and Organization
Similaire à The Roles and Responsibilities in an Agile Project and Organization (20)
Dernier
Dernier (20)
The Roles and Responsibilities in an Agile Project and Organization
- 1. w w w . n a p a . f i The Roles and Responsibilities in an Agile Project and Organization: Case NAPA Toivo Vaje @ToivoVaje Manager, Software Releases NAPA Technology #projektipäivät #onnistu2014
- 2. 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 9 COUNTRY OFFICES WORLDWIDE 175 EMPLOYEES © NAPA Software 3 25 YEARS DEVELOPMENT SITES
- 3. w w w . n a p a . f i Me • Master of Science (Physics) • 7+ years is Software Development • Developer, Scrum Master, Coach, Process Owner, Value Chain Owner, Manager • Jack of All Trades • Optimize the whole • @ToivoVaje
- 4. Contents How we make Releases Roles in Agile Organization Responsibility for Quality and Results Statement: Learning is everything
- 5. History Annual major releases Projects (a lot of) Variable scope and schedule
- 6. How we make Releases Now Stabilization Period
- 7. Different Levels of Abstraction Splits down into Sprints Is part of a larger entity
- 8. Release Planning • Whole company together • Event called Release Planning Day »Why? *see http://www.scaledagileframework.com
- 11. Communication
- 12. Release in a nutshell Plan Execute Learn Demonstrate Publish & Follow-up
- 13. Sprints Short iterations Same structure as Release, but shorter time span Planning Review Retrospective
- 14. Contents How we make Releases Roles in Agile Organization Responsibility for Quality and Results
- 15. Scrum Teams: Development Team
- 16. Scrum Teams: Scrum Master
- 17. Scrum Teams: Product Owner
- 18. Split work between Product Owner and Manager
- 19. Product Manager
- 20. Product Manager
- 21. Product Manager
- 23. How we make Releases Roles in Agile Organization Responsibility for Quality and Results
- 24. Responsibility for Quality and Results We don’t have separate QA function We don’t have Project Managers TEAMS are responsible for the quality and results
- 25. Aiding the teams • Continuous Integration + Test automation • Development Practice trainings • Scrum Master Community of Practice • Test Community
- 26. Conclusions
- 27. w w w . n a p a . f i Thank You @ToivoVaje Toivo.vaje@napa.fi +358-41-5372657 Manager, Software Releases NAPA Technology
Notes de l'éditeur
- Goal: Learning is everything.
- Just one slide about where I come from. We make software for maritime sector. We are global. We have been here for a while and we have customers. Respectful established company.
- But then again, I work there. ;)
- How we do things at NAPA
- For us Release is a Project. We have well defined processes so by every iteration we learn to do things better.
- Alignment Shared Vision Linking different abstraction levels Communication
- Release Planning, Execution,
- Short iterations Fractals. Same structure as Release but smaller scale Planning, Review (Demo), Retrospective (Post mortem)
- How we do things at NAPA Team centered. Scaled Agile Framework.
- Developers decide HOW it is built. How much can be done in a Sprint Distributed teams don’t work well. If possible, use local teams.
- Scrum Master helps the team improve. Guardian of the process. LEARNING!
- Product Owner says WHAT will be built Owns the Product Backlog
- Product Roadmap & Vision Long term plans (big rocks) Close to customers
- Product Roadmap & Vision Long term plans (big rocks) Close to customers
- Product Roadmap & Vision Long term plans (big rocks) Close to customers Middle man
- Facilitates Release events Gathers results Makes things visible
- How we do things at NAPA
- Tester not responsible for quality.
- You probably don’t hit all the targets with one shot. Well defined processes help repeatability Empower people to make daily decisions Continuously improve your operations