In an increasingly more complex world, finding the smallest possible chunk to deliver to get feedback is essential. This is the idea behind the term MVP. This article describes a model where business and technology together explore the product needs along seven product dimensions, which is a great way of finding small slices of work to develop.
At the Agile 2016 Conference InfoQ spoke to Wesley Coelho, Senior Director of Business Development for Tasktop, about the communication challenges inherent in DevOps and how to overcome them; how DevOps and agile expose organisational silos and waterfall communications flows that need to become adaptive and automated.
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 by enablling full coverage, minimizing errors, and facilitating scheduling and requirements changes. 1
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
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