The Challenge of Enterprise Requirements Management: Boosting Business Value with Index Cards |
|
| Saturday, 05 January 2008 09:55 |
Defect reduction
through early and detailed requirements specification is a common outcome of
process improvement efforts in product development. Enterprise requirements management becomes a
specialization that requires expert business systems analysts to gather and
document specifications that are detailed, accurate, and complete. If we
apply Lean principles to the requirements gathering effort we see a backed up
queue. Working to "Eliminate Waste" is a fundamental premise of
Lean thinking in Software Development. Mary and Tom Poppendieck consider
this so fundamental that they make it principal number 1 of 7 in their
Principles of Lean Software Development.[i]
They dispel the myth that "early specification reduces waste."
In fact, for software development, early specification is waste. This article extends this myth-busting by
exposing what can happen when process improvement techniques are blindly
applied to requirements gathering. The suggested solution is to replace
early detailed specification with solution roadmaps that can be detailed by
collaborative teams at just the right time. Agile methods provide the
structure and mechanics to allow business vision to lead product development
with cross-functional teams that unfold detailed requirements when needed. Defect reduction
through early and detailed requirements specification is a common outcome of
process improvement efforts in product development. Enterprise requirements management becomes a
specialization that requires expert business systems analysts to gather and
document specifications that are detailed, accurate, and complete. If we
apply Lean principles to the requirements gathering effort we see a backed up
queue. Working to "Eliminate Waste" is a fundamental premise of
Lean thinking in Software Development. Mary and Tom Poppendieck consider
this so fundamental that they make it principal number 1 of 7 in their
Principles of Lean Software Development.[i]
They dispel the myth that "early specification reduces waste."
In fact, for software development, early specification is waste. This article extends this myth-busting by
exposing what can happen when process improvement techniques are blindly
applied to requirements gathering. The suggested solution is to replace
early detailed specification with solution roadmaps that can be detailed by
collaborative teams at just the right time. Agile methods provide the
structure and mechanics to allow business vision to lead product development
with cross-functional teams that unfold detailed requirements when needed.Read more >>
Set as favorite
Bookmark
Email this
Hits: 1037 Trackback(0)Comments (0)
|


Defect reduction
through early and detailed requirements specification is a common outcome of
process improvement efforts in product development. Enterprise requirements management becomes a
specialization that requires expert business systems analysts to gather and
document specifications that are detailed, accurate, and complete. If we
apply Lean principles to the requirements gathering effort we see a backed up
queue. Working to "Eliminate Waste" is a fundamental premise of
Lean thinking in Software Development. Mary and Tom Poppendieck consider
this so fundamental that they make it principal number 1 of 7 in their
Principles of Lean Software Development.
