Making Agile Requirements Work-No. 1
The problem with many current methods of Elicit Requirements on software development projects is that they don’t add economic value to the solution effort. Many projects develop unrealistically...
View ArticleMaking Agile Requirements Work-No. 2
The BABOK® says the purpose of eliciting requirements is to identify and understand the stakeholders needs and concerns, and understand the environment in which they work. This goes beyond documenting...
View ArticleUnderstanding the Customer vs Customer Value
The Gilb’s have started a series of posts against Agile. The first on is Wrong Focus. “It is not about working software. It is not about your preferred working process. It is not about user stories. It...
View ArticleMaking Agile Requirements Work-No 4
We have proposed that Agile Requirements must be built at a purpose and outcome level, must leverage shared language that communicates context and intent, and must be based on a stable view of the...
View ArticleMaking Agile Requirements Work-NO 5
I hear a lot about emergent outcomes, and progressive elaboration, and self organization on Agile projects. These are slippery slope concepts, and far too often are applied irresponsibly. Emergent...
View ArticleClik here to view.
Making Agile Requirements Work-NO 6
On many software development projects, teams that are interested in getting started writing code early start by building the things they understand first. While this gets code started and in front of...
View ArticleClik here to view.
The Agile Bargains
There is a nice summary of Kanban at http://www.kanbandistilled.com/. It shows Feature Requests going into the Software Development Pipeline and Improved Software coming out.The article does a great...
View ArticleClik here to view.
Project Conversations-Shared Understanding
Most of the studies that discuss failed software development projects find misunderstood requirements and inadequate change management among the leading causes of failure. These failures can’t be...
View ArticleClik here to view.
I Signed the Oath of Non-Allegiance
Alistair Cockburn, in the Oath of Non-Allegiance, has issued a call to action for the software development community to stop bickering and calling out contending methodologies. He has called for...
View ArticleDeciding “What” To Build
This is my presentation from Product Camp Atlanta. I address two big issues facing product management. First, establishing an approach to connect product strategy with business strategy, customer...
View Article
