InfoQ Homepage Requirements Content on InfoQ
-
/articles/user-story-conversation/en/smallimage/user-story-a-placeholder-for-a-conversation-small-1695641308270.jpg)
User Story: a Placeholder for a Conversation
User stories are meant to be a placeholder for a conversation. This article dives into the differences between user stories and tickets, where stories came from and how recent trends are moving us away from conversations. It shows the impact this is having on product development and easy ways to improve collaboration through conversation and writing better stories.
-
/articles/TOGAF-enterprise-architecture/en/smallimage/togaf-logo-small-1536250135544.jpg)
How the TOGAF Standard Serves Enterprise Architecture
Any architect working with large enterprise systems has probably looked for guidance on how to manage the complexity and communicate with various stakeholders. This introductory overview of the TOGAF standard explains the structure of the framework, as well as discusses the benefits of using enterprise architecture to manage complex systems.
-
/articles/structured-conversations-mvp/en/smallimage/image001.jpg)
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.
-
/articles/agile2016-devops-challenges/en/smallimage/logo.jpg)
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; how DevOps and agile expose organisational silos and waterfall communications flows that need to become adaptive and automated.
-
/articles/designing-the-requirements-an-alternative-approach/en/smallimage/image001.jpg)
Q&A with the Author on "Designing the Requirements”, an Alternative Approach
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.
-
/articles/standardize-requirements-scrum/en/smallimage/logo-agile.jpg)
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.
-
/articles/wtf-requirements-agile/en/smallimage/logo-agile.jpg)
WTF requirements in Agile Product Development
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.
-
/articles/waterfall-requirements-agile/en/smallimage/logo-agile.jpg)
Waterfall Requirements in Agile Product Development
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.
-
/articles/alm-safety-critical/en/smallimage/iStock_82671183_MEDIUM.jpg)
Why ALM Is Becoming Indispensable in Safety-Critical Product Development
Integrated Application Lifecycle Management platforms are advancing product development in life and safety critical environments. The story of how Medtronic Neuromodulation were able to modernize their processes using ALM helps us understand current and future trends in the development of complex software-heavy products.
-
/articles/user-stories-placeholders-requirements/en/smallimage/agile-logo.jpg)
User Stories Are Placeholders for Requirements
It can be difficult to change from a Waterfall approach where ‘business analysts write big requirements up front’ to the Agile practice in which requirements are prepared ‘just in time’, and are the responsibility of the entire team. The secret to success in Agile is ruthless management of scope.
-
/articles/dave-snowden-leadership-cynefin-requirements/en/smallimage/logo.jpg)
Q&A with Dave Snowden on Leadership and Using Cynefin for Capturing Requirements
Dave Snowden gave a talk titled "Context is Everything" at the Scaling Agile for the Enterprise 2016 congress in Brussels, Belgium. InfoQ interviewed him about applying leadership models, the Cynefin model and how it can be used for capturing requirements, scaling agile, and sustainable change.
-
/articles/requirements-traditional-agile-outsourcing/en/smallimage/logo.jpg)
Q&A with the Authors on "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing"
Suzanne and James Robertson, authors of numerous publications in the requirements field, launched a video course called "Requirements: The Masterclass LiveLessons-Traditional, Agile, Outsourcing". InfoQ interviewed them on these video lessons to get further insights into some of the topics addressed.