InfoQ Homepage Customers & Requirements Content on InfoQ
-
Humble Programmers’ Reflections by Example on Unit Tests, TDD and BDD
Bruce Meacham discusses using user stories and business requirements for writing good tests that lead to good code, with examples in C#/SpecFlow and JavaScript/Cucumber.
-
Back to the Future
Emma Langman explores the usefulness of some of the Quality tools that have been around since the 50s for gathering requirements, tackling repeat problems, or innovating more efficiently as a team.
-
Voice of the Customer
Barb Spurway, Tracy Bowman discuss Voice of the Customer (VoC), a Total Quality Management/ Lean Manufacturing concept helping teams build quality products from the customers’ perspective.
-
Story Mapping
David Hussman advises on story mapping: pick an idea, choose someone that might be helped by that idea, build a story map as a way to explore that person’s experience, and start the customer journey.
-
Beyond Contracts: An Exploration into Unified Specifications
Paul deGrandis emphasizes the importance of using specification-as-a-value, a way of unifying core.contracts, test.generative, and external systems under a single common specification in Clojure.
-
Questions not Stories
Adrian Howard introduces a Lean Startup practice that could be complementary to stories: making hypothesis and creating experiments meant to validate or invalidate those hypothesis.
-
Better Product Definition with Lean UX and Design Thinking
Jeff Gothelf explains how to create better product definitions with Design Thinking and Lean UX.
-
The Importance of Descriptions in Understanding the Impact of Change
Steve Ross-Talbot discusses the what, why and how of describing things, in particular requirements, along with a set of tools serving that purpose and called Zero Deviation Lifecyle.
-
AMQP 1.0 Core Features
Robert Godfrey discusses the requirements set at AMQP’s foundation: Applicability, Reliability, Fidelity, Interoperability, Manageability, Ubiquity, explaining how AMQP was designed for the future.
-
Agile Architecture: Linking Requirements and Architecture to Solve the Right Problem
Mario Cardinal explains how to use agile practices to incrementally introduce non-functional requirements into the architecture in order to reduce the complexity of the solution.
-
When it Just HAS to Work
This talk gives practical tips for adopting an agile approach to planning, team interactions and risk management. When the culture shifts, teams achieve goals sooner and safety is greatly enhanced.
-
Forging ahead - Scaling the BBC into Web/2.0
Dirk-Willem discusses the change program underway at the BBC - empowering the creative community in the use of dynamic technologies, web/2.0 and social networking in order to talk to their audience.