Downloaded 66 times
Uploaded byToivo Vaje
The Roles and Responsibilities in an Agile Project and Organization
The document discusses the roles and responsibilities in an agile organization, specifically within Napa Technology. It highlights the importance of teams being responsible for quality and results without separate QA or project managers, emphasizing practices like continuous integration and test automation. Additionally, it outlines the structured process of release planning, sprints, and the collaborative approach taken by scrum teams.
More Related Content
Similar to The Roles and Responsibilities in an Agile Project and Organization
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 wemake Releases Roles in Agile Organization Responsibility for Quality and Results Statement: Learning is everything
- 5. History Annual majorreleases Projects (a lot of) Variable scope and schedule
- 6. How we makeReleases Now Stabilization Period
- 7. Different Levels ofAbstraction 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
- 9.
- 10.
- 11.
- 12. Release in anutshell 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 wemake Releases Roles in Agile Organization Responsibility for Quality and Results
- 15.
- 16. Scrum Teams: ScrumMaster
- 17. Scrum Teams: ProductOwner
- 18. Split work betweenProduct Owner and Manager
- 19.
- 20.
- 21.
- 22.
- 23. How we makeReleases Roles in Agile Organization Responsibility for Quality and Results
- 24. Responsibility for Qualityand 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.
- 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
Editor's Notes
- #2 Goal: Learning is everything.
- #3 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.
- #4 But then again, I work there. ;)
- #5 How we do things at NAPA
- #7 For us Release is a Project. We have well defined processes so by every iteration we learn to do things better.
- #9 Alignment Shared Vision Linking different abstraction levels Communication
- #13 Release Planning, Execution,
- #14 Short iterations Fractals. Same structure as Release but smaller scale Planning, Review (Demo), Retrospective (Post mortem)
- #15 How we do things at NAPA Team centered. Scaled Agile Framework.
- #16 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.
- #17 Scrum Master helps the team improve. Guardian of the process. LEARNING!
- #18 Product Owner says WHAT will be built Owns the Product Backlog
- #20 Product Roadmap & Vision Long term plans (big rocks) Close to customers
- #21 Product Roadmap & Vision Long term plans (big rocks) Close to customers
- #22 Product Roadmap & Vision Long term plans (big rocks) Close to customers Middle man
- #23 Facilitates Release events Gathers results Makes things visible
- #24 How we do things at NAPA
- #25 Tester not responsible for quality.
- #27 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