Scaling Scrum Angga Pratama - Ekipa 11-02-2020

Do we need it ? 1. How many product backlog do you have ? 2. How about the product owner ? 3. Development team skills ? 4. “Definition Of Done”, is it really Done ? 5. Involvement of stakeholders ? 6. How is your Sprint Planning ? 7. Who has the product vision ? https://medium.com/serious-scrum/7-things-to-check-before-you-de cide-to-scale-scrum-881aeec91153

Don’t scale until you have fixed your issues with Scrum adoption. Many reasons to scale Scrum can be removed by ‘doing Scrum’ properly. https://medium.com/serious-scrum/assessment-of-6-approaches-to-scale-scrum-46319fcbca1a

No content

1. Scaling with simplicity in mind 2. One single Product Backlog 3. Maximize the value of a Product 4. Multiple scrum teams work together on a product basis 5. Sprint Release as a whole integrated product 6. Sprint Review to demonstrating the product in its entirety. 7. Scale-up to scaling down Scaling Scrum is Just Scrum

Spotify model How they work ● Autonomous squad ● Tribe member < 100 people ● Chapter & Guild to increase communication in the company ● Scrum in Scrums on demand ● Highly Service-Oriented Architecture ● System Owner Chapter

Frameworks https:/ /kendis.io/scaling-agile/comparison-agile-scaling-models/

No Silver Bullet for Scaling Your Scrum

Thank You Let’s Get Connected ● eMail: angga.pratama@ekipa.co ● Phone: 08121067583 ● Linkedn: https://www.linkedin.com/in/angga -pratama-78919013/