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 a bit boring and lack focus and enthusiasm.
 

Risk registers and meetings are boring – try a project premortem instead …

What is a premortem?

A premortem is a project postmortem that’s run before a project. During a postmortem people analyse and discuss what went wrong, what went well and what could be improved.

While postmortems are very useful the problem is that by the time we run them the project is usually over and not much can be done about success and failure.

Successfully Teleported

Part of this fabulous deal with Telecom and the Galaxy Note II is that I switch to the Telecom network. I’ve been with Vodafone forever, it kind of goes along with being a Mac user, a Lambretta driver, a non-mainstream kinda girl. However Vodafone recently dropped my 3Gb data limit to 256MB for no apparent reason (I suspect I’d been left with a promotion for a bit too long and then they realised) and that proved a bit hard to live with. So switch I did and it was painless and good.
 

Nomad8 highlights of 2012

It is the time of year for winding down and reflecting on things before heading off to the beach for some BBQ-ing, drinking of things and general relaxing. So we wanted to thank you for your custom and support for 2012, wish you all the best for 2013 and share some of our reflections (we can share drinks and BBQs too, but that comes later).
 

Splitting a User Story along Acceptance Criteria

When breaking down a large user story to ensure it is sized appropriately, the default is to use Richard Lawrence’s excellent 9 Patterns for splitting a user story.
 
I also use an additional approach; in the first instance I look to see whether it can be split along its acceptance criteria. Every good user story should have acceptance criteria, and this approach ensures that not only do they exist, but they are also reviewed before we look to split.
 

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 helps to understand what to do next, but is a difficult tool for understanding what your whole system is intended to do.