Technical spikes are a great way for teams to scope out some work that they don’t fully understand before they begin work on it. Spikes are used by teams to suss out or do [...]
One of the hardest concepts for some teams to understand, especially when they first start using user stories, is that of story points. “What is a point?” they [...]
When I train agile teams – especially Scrum teams – I always bring up my experience as a developer starting with eXtreme Programming (at least my company’s [...]
Agile task breakdown and estimating can be a difficult conversation to have with teams. I had a conversation with one of our teams several days ago and we were discussing decomp [...]
I received the following question from a colleague a few days ago: Name: Randy Raypole Subject: User story design work Message: With regards to team understanding of stories. I& [...]
Learn more about Velocity Partners offshore software development company In part-1 of this series we began the exploration of user stories from “concept to executio [...]
I teach quite a few teams about User Stories. Most struggle with the concept, at least initially. One of the key challenges for many is the notion that stories are iterative. Th [...]
The user story has nearly become the ubiquitous requirements artifact in agile contexts. So much has been written about the user stories, their format, how to write them, the [...]
If you’ve any experience in agile approaches for software development, one of the common arguments surrounds documentation. Mostly it centers on software requirements, but it [...]
I read a recent article/blog post by Steve Johnson where he made the case for something he calls “market stories”. Here’s a snippet from the post: Lately I’ve been [...]