Download to read offline
Uploaded byMatthias Luebken
How to scale product development when you no longer fit in one room
The document discusses strategies for scaling product development in a startup environment, emphasizing the importance of adaptive processes and cross-functional teams. Key insights include the challenges of restructuring, the necessity of clear goals, and the value of continuous improvement through retrospectives. It advocates for a culture that embraces change and collaboration, rejecting rigid frameworks like SAFe that may hinder agile practices.
More Related Content
Similar to How to scale product development when you no longer fit in one room
How to scale product development when you no longer fit in one room
- 1. How to scaleproduct development when you no longer fit in one room Matthias Lübken The product guy @luebken
- 2. About me •Software Developer • Agile Coach • Director of software development • Product Manager Next generation PaaS for grownups. Based on Docker. Visit http://giantswarm.io
- 3. Our setting •Company: • A startup with product / market fit • Process: • Just do whatever works, and if you get stuck, ask someone in the room. • Challenge: • Scale product development • 1 4 teams. 7 30 colleagues.
- 4. Our (implicit) vision “No process is a good process “It’s about the people and their interactions
- 5. Topics • Crossfunctional teams • Adaptive product roadmap • Feedback in dev teams • Continuous improvement • Other ideas
- 6.
- 8.
- 9. Feature Team Product Devel-opment Feature Team Feature Team
- 10. Feature Team Product Devel-opment Feature Team Feature Team Functional Team
- 11. Feature Team Product Devel-opment Feature Team Feature Team Functional Team Community of practice
- 12. Lessons learned •Slicing is hard • Restructuring is painful • Clear goal is crucial
- 13.
- 14.
- 15. Product Jour Fixe CPO Developer POs CEO/CTO Architect Other Agile Coach
- 16.
- 17. Lessons learned •High discipline needed • Be prepared for hard questions
- 18. Feedback in dev teams
- 21. Lessons learned •Be open to new ideas • Coach teams
- 22.
- 23. If you doone thing in your process do retrospectives. “
- 24. Small and big retrospectives
- 25. Authority boards seemangement30.com
- 26. Lessons learned •Optimise locally and globally • Take the time needed • Be a good pace maker •Make authority clear
- 27.
- 28. No Blueprints •Blue Prints like SAFe don’t work • They are against all our instincts “Dave Snowden Put brutally SAFe seemed to be PRINCE II camouflaged in Agile language. ... SAFe is not only a betrayal of the promise offered by AGILE but is a massive retrograde step giving the managerial class an excuse to avoid any significant change.
- 30. Agile Scaling Cycle • Based principles and working Agile teams • "Autonomous business facing teams taking ownership of their process.” @StefanRoock • http://scaledprinciples.org/
- 31. Jimdo • Createdculture manual ! > acknowledge mistakes > have fun ! > strive for the best ! > ok to be crazy ! > no deadlines • Feel good manager • Weekly Teamverløtung • Goal #1 • Open Prio Meetings http://bit.ly/jimdostory
- 32. Take aways •Pickexamples that fit •Do collaborative change •Know your runway
- 33. Matthias Lübken Theproduct guy @luebken It’s hard but fun! Next generation PaaS for grownups. Based on Docker. Visit http://giantswarm.io