In the book “Designing the Requirements: Building Applications that the User Wants and Needs”, the author Chris Britton proposes an alternative path that goes from understanding the requirements to deliver spot on solutions.
Standardizing Requirements Descriptions on Scrum Projects for Better Development and Testing Quality
Standardizing requirements descriptions on Scrum projects benefit development and testing quality. Without standardizing, the project may suffer. Standardizing requirements descriptions provides a minimum of eight benefits from requirements descriptions unification, which in turn positively affects testing and makes management of ongoing changes in requirements easier with the help of tools.
The use of all-conclusive, hard-defined, non-negotiable BRDs is not appropriate in agile development. It will lead to an array of dysfunctions, including Local Optimization, deterioration of relationships between Product Owners and Feature Teams as well as loss of trust by end-customers. A refined, well-prioritized Product Backlog is the right place to store requirements in agile development.
Iterative development requires gradual flow of small-sized, prioritized requirements from end customers to delivery teams. The use of all-conclusive, rigid, non-negotiable BRDs leads to dysfunction.
The story of how Medtronic Neuromodulation realized that in order to modernize their processes while maintaining compliance, adopting integrated Application Lifecycle Management was necessary
It can be difficult to change from a Waterfall approach to the Agile practice in which requirements are prepared ‘just in time. The secret to success in Agile is ruthless management of scope.
InfoQ interviewed Dave Snowden about applying leadership models, the Cynefin model and how it can be used for capturing requirements, scaling agile, and sustainable change.
InfoQ interviewed Suzanne and James Robertson on the "Requirements: The Masterclass LiveLessons - Traditional, Agile, Outsourcing" to get further insights into some of the topics addressed.
This is the last of three articles exploring the culture and practices that makes Menlo Innovations such a joyous workplace. This article examines their approach to user experience and requirements
This article shows how to prioritize your backlog using an enhanced quality model using Maslow’s hierarchy of human needs. Search for most valuable features using the Need-Feature-Capability matrix 2
The book "Agile! The Good, the Hype and the Ugly" provides a review of agile principles, techniques and tools. It explores the agile methods Extreme Programming, Lean Software, Scrum and Crystal. 5
One of the largest areas of development waste are poorly formed requirements. This post presents a very simple technique that can be applied to all user stories to improve quality and reduce waste. 3