Statistics: (492 Views) (0 Comments) Posted by: Adrian Marchis on Tuesday, March 04, 2008 Categories: Requirements Analysis (BABOK KA), Agile Methods, Requirements Management and Communication (BABOK KA), Solution Assessment and Validation (BABOK KA)

To be honest, I'm not very enamored with the term "best practice". I believe that the term "contextual practice" makes far more sense because what is a "best practice" in some situations proves to be a "worst practice" in others. Having said that, people are interested in best practices so here they are when it comes to agile requirements modeling:

• Stakeholders actively participate
• Adopt inclusive models
• Take a breadth-first approach
  Model storm details just in time (JIT)
• Prefer executable requirements over static documentation
  Your goal is to implement requirements, not document them
• Create platform independent requirements to a point
• Smaller is better
• Question traceability
• Explain the techniques
• Adopt stakeholder terminology
• Keep it fun
• Obtain management support
• Turn stakeholders into developers
• Treat requirements like a prioritized stack

Author: Scott W. Ambler