InfoQ Homepage Requirements Management Content on InfoQ
Articles
RSS Feed-
/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/making-scaling-agile-work-2/en/smallimage/logo-small-1506438802059-1509141610250.jpg)
Scaling Agile - Slice and Understand Together
This second article in the series about making scaled agile work digs into how to slice requirements. If this is done right, it will not only result in good slices, but also a common understanding of the product we’re about to build or enhance.
-
/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/use-case-20-slices-Dutch-Railways/en/smallimage/logo-agile.jpg)
Keeping Development ‘On Track’ with Use-Case Slices at Dutch Railways
How can you get from high level system requirements (features/epics) to the right level of specification to enable agile development? This article describes how Dutch Railways made the transition from large use cases which were completely written before development, to “Use Case 2.0” and why this helps them to deliver apps faster and with the right business value.
-
/articles/quality-hierarchy-needs/en/smallimage/logo-agile.jpg)
The Hierarchy of Needs
What may be valuable to customers whom you do not even know in an unstructured and completely individualized market? This article suggests prioritizing your backlog using an enhanced quality model based on Maslow’s hierarchy of human needs. Search for most valuable features using the Need-Feature-Capability matrix and give those features highest priority in your backlog.
-
/articles/resurrection-pra/en/smallimage/logo1.png)
The Resurrection of Product Risk Analysis
Product risk analysis (PRA) is not only useful in testing but is also applicable during the various phases of sequential or agile system development. This article introduces a different application of PRA that elevates it from project level to domain level. It shows how you can go from risk and requirement-based testing to risk and requirement-based development.
-
/articles/50-ideas-user-stories/en/smallimage/50book-logo.png)
Q&A with Gojko Adzic on Fifty Quick Ideas to Improve Your User Stories
The book fifty quick ideas to improve your user stories aims to help people to write better user stories, supporting teams in iteratively delivering products that satisfy the needs of their customers. InfoQ interviewed Gojko Adzic about the format of his new book, when and when not to use user stories, the ideas that the book provides, organizing product backlogs and prioritizing user stories.
-
/articles/applying-lean-thinking-to-software-development/en/smallimage/logo.jpg)
Applying Lean Thinking to Software Development
Lean’s major concept is about reducing waste, meaning anything in your production cycle that is not adding value to the customer is considered waste and should therefore be removed from the process. Steven Peeters explains how you can apply Lean principles in an IT environment.