Agile
Agile techniques for software requirements: user stories, product backlog, design thinking, MVP minimum viable product, etc.
Is the Product Owners Owning His Product?
This blog post tries to answer the following questions: Does a Product Owner indeed own his product? What are the duties of a Product Owner? Who is the Product Owner? What qualities should a Product Owner possess? Starting from the description in the Scrum Guide, the blog provides interesting material to understand the high level […]
Read More
Successful Feature Injection
Feature injection is a business analysis approach that focuses on business value, an approach similar to Behavior Driven Development (BDD). It transfers knowledge to the team about how the project can deliver value and what are the features needed to deliver that value. Examples are used to transfer this information to the team in the […]
Read More
User Stories Walking Exercise
In this blog post, Dhaval Panchal proposes a technique that help slicing agile user stories. He uses it for stories ‘not-done’ at the end of sprint or team that have problems to split stories horizontally across components. The idea is linked to the experience of taking your dog to a park for a walk. The […]
Read More
Comprehensive User Stories
A user story is a high-level requirement of a feature provided from the perspective of a stakeholder. A comprehensive user story has acceptance criteria that cover all possible functional scenarios or conditions needed to satisfy the user requirements. In development and testing terms, this means defining positive and negative scenarios. This article defines what differs […]
Read More
Using Use Cases or User Stories in Scrum
This blog post defines the concept of use cases and user stories and discusses how and when they should be used in an Agile software development project. User stories are different from use cases because they are centred on the result and the benefit of the thing you’re describing, whereas use cases are more granular. […]
Read More
An Agile Method for Model-Driven Requirements Engineering
This article provides a methodological approach that focuses on requirements engineering within the Model-Driven Development (MDD) context. Our approach is an OpenUP extension in which the requirements discipline is placed in the model-driven context. We believe that the integration of requirements engineering and MDD into one consistent process will provide practitioners with the benefits of […]
Read More