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.
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.
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.
The book fifty quick ideas to improve your user stories aims to help people to write better user stories and support teams in iteratively delivering products that satisfy their customers' needs.
Lean’s major concept is reducing waste: removing anything that is not adding value to the customer from the process. Steven Peeters explains how you can apply Lean principles in an IT environment. 2