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:
Please check the articles associated with this category for more detail:
An understanding of the Agile Product Backlog Grooming process is important. A metaphor of an “Iceberg” is often used to visualize how the process works. What Is Product Backlog Grooming? The “Product Backlog” in an Agile/Scrum environment is a prioritized queue of work to be done. It normally consists of user stories which are short […]
Agile Product Backlog Grooming Iceberg Read More »
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 »
Questions frequently come up about “What’s the Right Level of Detail to Put in an Agile User Story?” – I want to share some thoughts with you on that subject. There is no absolute right/wrong answer about how much detail a story should contain – the best answer is “it depends”. Level of Detail in
What’s the Right Level of Detail in an Agile User Story? Read More »
