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.
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.
When working on projects, it is most of the time necessary to forecast the project delivery time up front. Little’s Law can help any team that uses user stories for planning and tracking project execution no matter what development process it uses. We use a project buffer to manage the inherent uncertainty associated with planning and executing a fixed-bid project and protect its delivery date.
The book Scenario-Focused Engineering describes a customer-centric lean and agile approach for developing and delivering software-based products using a fast feedback cycle.
If you don't want to analyze all user stories in your project in order to estimate size then Randomized Branch Sampling can be used for portfolio related decisions and quotations on prospect projects.
The book "Agile! The Good, the Hype and the Ugly" provides a review of agile principles, techniques and tools. It explores the agile methods Extreme Programming, Lean Software, Scrum and Crystal. 5
This is a case story of how a supplier cooperated with a client to develop a huge project in an Agile way, by cutting it into smaller pieces and prepare a matching contract based on mutual trust.
One of the largest areas of development waste are poorly formed requirements. This post presents a very simple technique that can be applied to all user stories to improve quality and reduce waste. 3
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.
This article discusses “human experience” testing and uses concepts from human computer interaction design theory to establish a framework for developing “human experience” test scenarios.
User Experience is part of a collaborative, self-contained and balanced team that has all the necessary roles to be wholly responsible for building the right thing, and building the thing right.
Active Architecture is a type of documentation that is based on User Stories and helps to bridge the gap between User Stories in Agile Projects and large design deliverables on Traditional projects. 14