Agile techniques for software requirements: user stories, product backlog, design thinking, MVP minimum viable product, etc.
Product design and development remains difficult, even when applying Lean or Agile principles. Why is developing a great product so hard? How come it takes so many iterations? Why don’t users know what they want? Why don’t I know what they want?Read More
Creating requirements for your web or mobile application can be tedious and managing ideas even more. The larger the project, the more difficult it becomes. Add in the flexibility that Agile brings to projects, and things could quickly get out of hand.Read More
User stories are a technique taken from the agile development playbook that can easily be applied in traditional systems development and maintenance. User stories help you document needs in a structured way, from the users’ perspective. They’re a good basis for test cases, so as to support integrated requirements management and testing. In this article, […]Read More
How do agile requirements work? Where does documentation fit in? For many of us, the transition from the security of upfront analysis and detailed specification documents to ‘doing Agile’ and embracing the process of discovery is a terrifying prospect. Agile theories don’t readily address the concern ‘how will we know where we’re going if we […]Read More
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