Agile techniques for software requirements: user stories, product backlog, design thinking, MVP minimum viable product, etc.
There is no business analyst role in the Scrum Agile project management framework. Based on this fact and some perceptions about Agile, Roland Hesz tries to answer the questions “Do we need a business analyst on an agile project? Are there Agile business analysts?”.Read More
Agile uses mostly user stories to capture requirements. In his blog post, Jean-Jacques Dubray explains that there is a problem with user stories because they tend to focus on the solution and not on the problem definition.Read More
This short video presents the Mike Cohn’s Iceberg Analogy for User stories. It discusses User Stories and the Backlog, how you can perform grooming and rightsizing and how you should establish a grooming cadence for sprint, release and roadmap.Read More
System-building projects which fail (which is many of them) do so more often because they build the wrong thing, not because they do a bad job of building the right thing. The Agile community has developed a range of techniques for making sense of system requirements and capturing them in artifacts that are familiar and […]Read More