Ah, the plans… You spent hours preparing them and then… eh…
Agile, Kanban, Scrum, iterations, retrospectives etc. Working in an agile way is something I’ve done for years. Here I share my experiences. Enjoy!
Killing daily meeting (one dev at a time)
Daily meeting can go horribly wrong. One of the anti-patterns is to follow the “dev by dev” approach. There are better ways.
Team feedback – retrospective with goReflect
My experiences of using goReflect to run remote retrospective. Worked really well for me.
High WIP? Frustration guaranteed!
With too many tasks opened at the same time the only thing you achieve is a huge amount of frustration. Control your WIP or suffer.
A penalty for high WIP, or why spreading yourself thin will kill you
Too many tasks opened lead to various problems. Let us have a closer look at them.
What is WIP (Work in Progress)
WiP – Work In Progress. You better make sure you keep it at reasonable level.
Remote retro with RetroTool
Today we run our first remote retrospective using http://retrotool.io for cards & http://zoom.us for video conferencing. The context: two people developing remotely, after 1,5 week of work, we met to discuss how we are doing We decided to use the http://retrotool.io. Why this one? Few reasons: it is dead simple it seems to work it…
The carpet that bothered them
What are retrospectives good for? Surprisingly, even for teams that discuss things together on a daily basis, a meeting devoted to process improvement can make a difference.
3 Daily Scrum Questions Considered Harmful
Still using 3 standard questions for your daily Scrum? Oh, bad news for you: you are doing it wrong.
Transparency in Scrum and Sociocracy 3.0
The different approach to transparency by Scrum and Sociocracy 3.0.