I was reading this 2016 article from Dave West, which is very interesting since he suggests some simple ideas to improve scrum value in the team:
- Put the values on a wall and have each team member write up how they are going to demonstrate the value in their working day.
- Add a ‘values moment’ to your retrospective. This gives everyone an opportunity to inspect and adapt on their values.
you can 3 find more on the Dave’s article.
Today i was attending an interesting webinar about the topic “Keeping Retrospective fresh”, here my notes.
Why do we retrospect?
First of all it’s clear we make retrospectives not because the Scrum guide says we should, but because we want to understand and improve performance!
Warning signs of ineffective retrospectives & root causes
Because doing things is not the same as getting things done
Continue reading “Keeping Retrospective fresh”
Hofstadter’s Law says “It always takes longer than you expect, even when you take into account Hofstadter’s Law”.
Continue reading “Hofstadter’s Law”
Adding new developers to an already-late project tend to make it even later
Continue reading “Brooks’s law”
Work expands so as to fill the time available for its completion
What does it means?
- a task is estimated in 10h
- a developer will do it in 10+h even if he could take less
It’s possible to write in this way
The demand upon a resource tends to expand to match the supply of the resource. The reverse is not true.
Here a nice video about Objectives and Key Results from Patrick Lobacher @ T3CON16
In an article Mike Cohn tell us his view of the difference and in the comments there is a really funny and clear example by Ian Mitchell let me quote here: Continue reading “The difference between user stories and tasks”
I recently read this interesting article by Dave West about Working with a web development company using Scrum.
Since I’m a scrum master and web developer this is going to interest me very much. Continue reading “Working with a web development company using Scrum”