I just gave a webinar about the context and basics of Agile Release Planning. Below is the 30-minute video, including questions from the audience. You may also download the PDF of the webinar slides. Enjoy!
To have a decent Agile-Scrum Team, here are my conditions: An important set of work An ability to define that work well enough (clearer requirements) A team that wants to do that work — an inspired team would be great A team that is willing to try Scrum The courage to face the truth Someone […]
If the Team does not see themselves as a Team, does not feel that “we win together or we lose together”, then the Scrum events (Sprint Planning Meeting, Daily Scrum, Sprint Review, and Retrospective) are likely to be pretty lame if not useless. I think lots of people do not naturally think of themselves as […]
Here is another lightning Webinar on this topic. A few of the key ideas: * A small suggestion, easily implemented (at least the basics are easy) * This is right in the area of the PO’s true responsibilities. * It yields, we find, huge benefits. Almost always. (I suppose your team could be doing something […]
Good group and fun to talk with. Thanks to Katie and everyone for having me! Put a fair amount into the deck and the drawings. But surely not self-explanatory for all. But maybe a good start or a good refresher for many. The drawings and the deck. Enjoy! Paper.Agile Halifax Oct 2018.2018.10.23 Agile Estimation Agile […]
At the Lean Agile Open (an Open Space event) last Friday, October 19th, I was having lunch with Gwen Kestin(a great coach at Vanguard) and others. Gwen was talking about the necessary conditions for a Team before you start coaching them. She mentioned someone who had come up with a list of about 6 conditions. […]
There are two main things to say about a ScrumMaster. The SM is a servant leader. The SM is the impediment-remover-in-chief. With this latter one, we are saying that the SM is not the only one who can remove impediments (the rest of the Team, Managers, people outside the company could all help do that). […]
We have been talking about this issue for years. Well, we do not entirely agree on what the issue is. Ron Jeffries calls it Dark Scrum. To quote (almost): “too often “Scrum” is used to oppress people”…and he explains that it was his aim that agile would make the world safe for programmers and testers. […]