Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Empfohlen
Empfohlen (20)
Stay SAFe with Scrum
- 3. @bart_naroznik SAFe (Scaled Agile Framework) Scrum XP Kanban
- 4. SAFe overview Funnel Epic Epic Review Epic Analysis Epic Portfolio Backlog Epic Epic Implementing Epic Epic Portfolio Level Program Level Team Level Feature Feature Feature Program backlog Agile Release Train Program Increment (8-12 weeks) User Story User Story Team backlog User Story Sprint (2-3 weeks) @bart_naroznik
- 5. 2-level planning @bart_naroznik Program Increment (8-12 weeks) Sprint (2-3 weeks) Sprint (2-3 weeks) Sprint (2-3 weeks) Sprint (2-3 weeks)
- 6. Plan on cadence, release on demand @bart_naroznik Release candidates Release candidates Release 1.0 Release 1.0.1 Release 1.1 Release 1.2 Release 1.3 Release 2.0 Planning Event Planning Event Planning Event
- 8. Why SAFe? • Centralized strategy, combined with de-centralized agile development execution • Helps large organization teams to meet organization's strategic goals • Has three/four levels that centralize the strategic themes of an organization • Helps teams maintain alignment with business goals • Industry-proven. Value-focused. • Free of charge at fundamental level. @bart_naroznik
- 9. Where to start? www.scaledagile.com/enterprise-solutions/what-is-safe/ www.scaledagileframework.com www.qasymphony.com/blog/pros-cons-scaled-agile-framework-safe/ GOTO 2015 • Is SAFe Evil? • Lars Roost & Henrik Kniberg @bart_naroznik
Hinweis der Redaktion
- Most of us know scrum and we use it in our work. But what if we have really big interprise with hundreds of people and tens of teams that needs to be coordinated? Would Scrum work? Well... Probably we need some more than that.
- There are many framework for scaling agile. This is only few most popular ones. Since I have only five minutes I would like to tell you about only one of them which I know best.
- SAFe assumes Scrum at a team level Agile Release Train = Team of Teams Program Level: Program Backlog = Team/Product Backlog on a higher level; Features = bigger User Stories (too big to fit an iteration); They stick together for 4-5 sprints Portfolio: Epic = mini business case; you may never even finish Epic – it’s an area we are doing work; a factory that generates features
- A lot of companies do it anyway
- Long cycle is just a planning cycle. We don’t batch changes
- In PFA: 350+ people, 32 teams, 4 Agile Release Trains And it was environent where most of people didn’t really know agile at all. Almost two years now.
- +It answers the questions like "How do we plan?", "How do we budget?", and "How do we become cross-functional in architecture and DevOps?" 1. SAFe helps large organization teams to meet organization's strategic goals, not just individual project goals. +The framework offers the ability to maintain and create a centralized strategy to deliver value. 2. The SAFe model has three/four levels that centralize the strategic themes of an organization. 3. Centralized strategy, combined with the de-centralized agile development execution. 4. industry-proven, value-focused method for scaling Agile at the Enterprise level.