Year: 2013
From Value to Solutions in Agile
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
The User Stories Iceberg
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
User Stories Are Not Requirements
The common wisdom is that Agile register requirements using the user stories format: “”As a , I want <goal/desire> so that “. In this article, Earl Beede explains why user stories are not requirements.
Read MoreWriting Executable Specifications
Elisabeth Hendricksson stated at Turku Agile Day 2010 that “Specs is an abbreviation for speculations”. She is right, specs are often speculations. How can this be avoided? Execution of code doesn’t leave any room for speculation. If the specs can be executed, they aren’t speculations anymore.
Read More
A Template for Software Requirements
When you are gathering and documenting software requirements, it is not always easy to remember all the dimension that should be included in this activity. The book “Mastering the Requirements Process” proposes a template that should help you in this activity.
Read More
Modeling with SoaML: Service identification
The power of a service-oriented architecture (SOA) is in its ability to enable business agility through business process integration and reuse. SoaML (Service-Oriented Architecture Modeling Language) is an Object Management Group (OMG) standard that is intended to help realize the potential of SOA.
Read More