Thoughts and conversation from our nomads.
The importance of size and proximity
Process is expensive. Bigger teams, working from a distance, part time team members, and many specialists are all factors that lead to a more elaborate process. This might be obvious, but the more companies we get to know, the more we experience that this is something being ignored. This article is...
Sometimes average is good.
The Big Estimation Debate There have always been, and no doubt always will be debate over estimation; the pros and cons, behaviour anti-patterns and the how and why of it all. In this post I am not going get into that debate but I want to share with you some experiences I have had with estimation th...
Daily stand-up with a goal
Why your daily standup should be driven by a daily goal Let’s face it, the daily standup can be a boring affair. I’m not talking about abominations with 16 people or half-hour long status reporting meetings. I’m talking about the ones that are kind of okay and adhere to the rules but nonetheless are...
Sprint planning - turning the what into how
What does your sprint planning meeting look like? Are you the "do it as fast as you can" efficiency hounds or the "sit and listen while the tech lead drones on" type, or are you a "real team" who fight for great designs and customer experiences? Having watched and attended a few hundred of these mee...
Could a "Definition of Ready" Help You Strike a Balance?
Many novice teams find it difficult to strike the balance between too much and too little detail when writing user stories. User stories often start their lives as big statements of intent with lots of unknowns and that’s okay. For something that’s not going to be developed in the near future it mak...
Evolving the Story map
I can't say enough about how useful story maps are and how essential they are on any Agile project. Jeff Pattonis the undisputed (certainly in my mind) master of the story map and it's well worth looking at the materials on his site. Jeff summarises a story map as, "A prioritized user story backlog...
It might look like rapids, but it's still a waterfall
This is my second post in my Scrum coaching patterns series. In my last post I asked for some help with a pattern format that I could follow and at least one person must have read my blog as I now have a shiny new format to follow thanks to Gareth Evans for this. This is based on Linda Rising and Li...
Why being a Scrum Master is a full time job
“An adequate Scrum Master can handle two or three teams at the time; a great one can only handle one”. (Michael James - An Example Scrum Master’s checklist) I found that organisations, teams and new Scrum Masters (even freshly certified ones) often aren’t sure what the Scrum Master role entails a...
The non challenging Scrum Master
Earlier this year I was invited to join the Scrum plop, to help write some patterns for the Scrum community, unfortunately the stars were not right and I was not able to attend. It did however help me answer a question that a great friend and fellow Agilist Sandy Mamoli put to me, which was "how do...
Interview with a developer turned Agile
Following last week’s interview with a newly-minted Scrum Master this week I have had a conversation with developer Mateusz Udowski. We talked about how SilverStripe’s adoption of Agile and Scrum have affected him and why he thinks SilverStripe is now more intelligent as a whole than it was before....
Interview with a newly-minted Scrum Master
Six months ago SilverStripe, an open-source Content Management System provider and Wellington web agency approached me to help them improve the way in which they deliver client and open source projects, increase employee happiness and, in general, just do the best possible job. To achieve this, we d...
Exploring servant leadership
A few weeks ago I was sitting next to a log fire, sharing a glass of wine with a few like minded individuals chatting about all things Agile, one of the things we discussed was a time when one of the party was a Scrum Master and that they had a team admin who used to collect all the story data and d...
Kanban is not for the Idle or Newbies
For four of my six and a half Agile years I was solidly in the Scrum camp, Lean, in my opinion, was already part of Scrum and its influence made Scrum even better. I don't think that any Agile practice is for the work shy and there is a lot of personal courage needed to get any practice working well...
Even done is never done
A “done” definition in an Agile project is a statement that the team use to measure whether they’ve met all of the requirements for completing a userstory / feature (and in some cases completing an iteration or release). Done is one of the major shifts from doing Agile to being Agile. So, what is “d...
The document dilemma
The Agile manifesto states “Working software over comprehensive documentation” – this seems to be one of the biggest mindset shifts that organisations need to make when adopting any Agile framework. For some people that simple statement brings up visions of chaos, lack of control, and the worst fear...
A template for the sprint review
Conducting an interesting and engaging end-of-sprint review is an often overlooked art: Not only do we want to show what we have built during the last sprint and collect feedback and good ideas for what to build next; we also want to give our audience a good experience. At my workplace we always in...