Can you guess the number one question I get from requirements leaders across the world? Whether their team is agile, traditional or hybrid, whether their team has 2 members or 250, whether they are creating cutting edge products or maintaining legacy systems, their...
Over the years, I’ve helped many teams find success by identifying and removing roadblocks. One roadblock that seems to be appearing with greater frequency is “project prominence”— an emphasis on the project over the product or solution being delivered. Teams spend so...
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...
Is it possible for Business Analysts to shift seamlessly between agile, traditional, hybrid, waterfall and package software projects? Yes! BAs can build a toolkit that promotes success in every environment, and honestly, that Swiss-Army skill set is a necessity for...
