When growing a startup product development you encounter major challenges: How do you scale your product development teams? How do you keep as fast and responsive as you used to be? And how do you leverage the existing knowledge? In this talk I’ll show a couple of practices and rituals based around a Kanban board which captured our whole product development efforts with about 30 participants. I’ll show the design of the Kanban board, the policies and meetings around it and the personal duties ranging from a developer to a product manager up to the CEO. I will also compare it to other approaches from the community and what our lessons learned are.
Slides from the talk at the Jax: https://jax.de/2015/sessions/how-do-product-development-when-you-no-longer-fit-one-room
20. DevOps team
• Created in the dev teams
• Lots to learn and understand
• Extracted into functional team
• Rotating 2nd level support in teams
rotating participation in the
DevOps team
39. 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.
40.
41. Agile Scaling Cycle
• Based principles and
working Agile teams
• "Autonomous business
facing teams taking
ownership of their process.”
@StefanRoock
• http://scaledprinciples.org
42. Jimdo
• Created culture manual
• Feel good manager
• Weekly Teamverløtung
• Goal #1
• Open Prio Meetings
> acknowledge mistakes
> have fun
> strive for the best
> ok to be crazy
> no deadlines
http://bit.ly/jimdostory
43.
44. •Pick practices that fit
•Challenge yourself
•Do collaborative change
•Know your runway
Take aways
45. Matthias Lübken
The product guy
@luebkenQuestions?
Microservice Infrastructure
based on Docker.
Visit http://giantswarm.io