Agile Requirements

This category contains topics associated with Agile Requirements Practices.  The approach for managing requirements in an Agile environment is very different from the approach that is commonly used in a traditional plan-driven environment and the approach is directly related to the overall project planning approach.

Some of the major differences include:

  • Instead of attempting to define a complete set of detailed requirements for the project upfront, an Agile approach is based on further evolving and elaborating detailed requirements as the project is in progress
  • An Agile approach requires a much higher level of collaboration between the project team and the users and Business Sponsor.  Project requirements are based much more on direct communication rather than detailed requirements documents.  That reduces or eliminates major sources of miscommunication and errors

Please check the articles associated with this category for more detail:

Functional Decomposition – How Does It Apply to Agile? Why Is It Important?

What is Agile functional decomposition? (and why is it important?) Investopedia defines “functional decomposition” as follows: “A method of business analysis that dissects a complex business process to show its individual elements. Functional decomposition facilitates the understanding and management of large and/or complex processes and can be used to help solve problems: Basically, functional decomposition …

Functional Decomposition – How Does It Apply to Agile? Why Is It Important? Read More »