-
Using Structured Conversations to Discover Your MVP
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.
-
Book Q&A on Product Mastery
The best product owners are insatiably curious about their customers; they observe them in action, interview them, and collaborate with them and bring them into the development process, said Geoff Watts. In his new book Product Mastery he explores what he calls “the difference between good and great product ownership”.
-
Service Design: Consumer Journey Mapping
A process of identifying key customer interactions with the product. This is a holistic approach to envisioning customer interactions at various touchpoints through service design tools to help organizations to understand, visualize and envision their new or existing customer there by aligning their products.
What Does "Being Digital" Actually Mean?
This article gives a description of what Being Digital is and how it can be achieved. Digital is about putting less emphasis on tech for success and more on your customers. 4
Interview with Wesley Coelho on Challenges in DevOps
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.
Q&A with the Author on "Designing the Requirements”, an Alternative Approach
“Designing the Requirements: Building Applications that the User Wants and Needs" proposes an alternative way 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
WTF requirements in Agile Product 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
Waterfall Requirements in Agile Product 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.
Why ALM Is Becoming Indispensable in Safety-Critical Product Development
The story of how Medtronic Neuromodulation realized that in order to modernize their processes while maintaining compliance, adopting integrated Application Lifecycle Management was necessary
User Stories Are Placeholders for Requirements
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.
Q&A with Dave Snowden on Leadership and Using Cynefin for Capturing Requirements
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.
