Agile: adjective – able to move quickly and easily.
In this post, I take a short sail through the waters of refining an Agile Team’s backlog. The ideal condition for a team’s backlog (of both user stories and non-stories) is for it to be: Owned by the team High with signal Low on noise From this state, the crew can plan …
Don’t let the simplicity of the daily stand up agenda – “Yesterday, today, in my way” – fool you into thinking that it is easy to master. Behind this elegant minimalism you’ll discover fine grained coordination, emergent discovery, accountability, and the heartbeat for an entire team. Know what a good stand up looks like …
Agile User Stories are short, simple descriptions of a feature or function told from the perspective of the person who desires the new capability represented by the story, usually a customer. They focus on the result or value that the user or customer gets. User stories can be big (but not …
It’s a pretty tired discussion in my house: Multi-threading, multi-tasking, the cost of context switching, etc. Especially with a teenager at the dinner table… So I found a nifty exercise to drive the point home. Supplies Needed: One volunteer who considers themselves an expert context-switcher / multi-threader Three decks of …
The Challenge In the pursuit of delivering business value, there is no shortage of obstacles to overcome to achieving high levels of trust, good communication, and the ability to have productive conflict on agile scrum or kanban teams. Those impediments have the potential to restrict continuous improvement and get in the way of …
