During agile training sessions, the most common question I get is, “Can you PLEASE just tell me what I need to document as an Agile BA?” So, let’s clear up this up once and for all! The answer is NOT simply user stories and acceptance criteria, or a traditional...
Success or failure often hinges on the questions we ask throughout the project lifecycle. It sounds a bit dramatic, but I’ve witnessed it many times—a single, thought-provoking question that changed the trajectory of a conversation, opened a floodgate of new ideas, or...
There are so many things that impact the quality of our requirements. We have the ability to influence many of them, but our influence is often limited. One thing we do have control over are the words we use to describe and document (if needed) requirements. It can be...
Most teams spend too much time on documentation. When planning, elicitation, and analysis are done well, documentation becomes simple and speedy. I think most people agree in theory. They are hungry to reduce documentation and speed up their requirements process, but...
How do you start your requirements process? Many agile and traditional teams start their process by defining features. While I don’t always disagree with this approach, it’s a potentially dangerous and slippery slope if teams are not careful. The mindset...
What are you hanging on to? What do you need to purge from you project closet? Still fond of the requirements equivalent of MC Hammer parachute pants, jackets with shoulder pads, stirrups, acid wash jeans or jelly shoes? If you’ve been using the same requirements...
