Rome was not built in a day!!!
Rome was not built in a day and so is adopting and scaling agile methodology, which cannot be done overnight. It is not only the team that needs to be agile but entire organisation have to adopt agile. Along with team structures and processes scaling agile needs change in the mindset.
I would be presenting a case study of one of our projects which had more than 150 people working on the same product. At one point time there were more than 250 people working from 3 different locations and following agile methodology and releasing software every six weeks. This case study will cover different approaches and practices that we followed. Where did we excel and where we failed.
This case study would also sneak peek into some of the practices to be followed when the team is distributed, for e.g. remote pairing, remote stand ups, distributed retros, etc.
Outline/structure of the Session
- Introduction to the project.
- Different team structures.
- What worked and what did not?
- What if teams are distributed?
- Paradigm shift needed in the project.
- How do multiple teams work and coordinate among each other while working on the same product?
- What are the responsibility of a Product Owner in such a environment?
- What are the organisational changes needed?
Any large enterprise planning to adopt agile, any organisation following agile and wants to scale.