M³ for Police
M³ for Mobility
M³ for Well-Being
Trafic light Controllers
Development Mood M³ (copy)
Product Team M³
9. Suitable Process
Good : Our way of working fits us perfectly
Bad : Our way of working sucks
Good : We are a totally gelled super-team with awesome collaboration !
Bad : We are a bunch of individuals that neither know nor care about what the other people in the team are doing
1. Delivering Value
Good : We deliver great stuff! We are proud of it and our stakeholders are really happy.
Bad : We deliver crap. We feel ashamed to deliver it. Our stakeholders hate us.
Good : We are learning lots of interesting stuff all the time 8
Bad : We never have time to learn anything
Good : We know exactly why we are here and we are really excited about it!
Bad : We have no idea why we are here, there is no high lever picture or focus. Our so called mission is completely unclear and uninspiring
7. Pawns or Players
Good : We are in control of our destiny! We decide what to build and how to build it.
Bad : We are just pawns in a game of chess, with no influence over what we build or how we build it
Good : We get stuff done really quickly. No waiting, no delays.
Bad : We never seem to get done with anything.We keep getting stuck or interrupted. Stories keep getting stuck on dependencies
Good : We always get great support & help when we ask for it!
Bad : We keep getting stuck because we can’t get the support & help that we ask for.
Good : We love going to work and have great fun working together!
Bad : Booooring ...
2. Easy to release
Good : Releasing is simple, safe, painless and mostly automated.
Bad : Releasing is risky, paintful, lots of manual work and takes forever.
4. Health of Codebase
Good : We are proud of the quality of our code ! It is clean, easy to read and has great test coverage.
Bad : Our code is a pile of dung and technical debt is raging out of control.