For many years I’ve felt strongly that choosing to rewrite a piece of software is something you have to think really hard about. You have to have good reasons to do it, and it’s often the wrong choice. It’s a classic issue in software engineering where you think it won’t take long, and that you’ll quickly be back to productivity.
Experienced teams know the trap of assumptions. Every one assumes you are on the same page and is eager to jump into development, get it done, quick, quick, quick… and then nagging doubt sets in…
“Ah, that’s not how I imaged it”,”Ow, I think I might have misunderstood this”, “Well that’s not what I was thinking!”
A creative and focused retro, for mature teams – maximum size: 7 (storming and norming) – take a look at our impressive and remarkable gallery below!
Let’s face it, retro’s can get a bit stale. So it’s good to jazz it up once in a while. So if you are feeling adventurous, you might want to try an Artsy retro.
A fun and engaging retro format for distributed agile teams. Recommended for newly formed teams.
Collaboration within distributed teams can be a challenge. Without shared access to a whiteboard or flip chart, you have to look for alternative tooling. The TeamUp Labs online Example Mapping Tool makes it easy for teams to gain a shared understanding of what they are building, no matter their geographic location. If Example Mapping is new to you then check out our overview or dive straight into the tool and give it a go.
The creation of the Example Mapping tool was driven out of need while working in distributed teams. In these teams, we found many useful online tools that enable more successful collaboration. Below is an overview of our favorites.