Agile requirements

Freshness Warning
This blog post is over 20 years old. It's possible that the information you read below isn't current and the links no longer work.

The Rational Edge describes how to do effective requirements management and mitigate software risk within an agile development project in Agile Requirements Methods.

The article is written by Dean Leffingwell, one of the authors of the excellent Managing Software Requirements: A Unified Approach.

Leffingwell sets forth some basic principles of managing requirements. Software development teams should only create the documentation that adds value. Creating documentation is a time-consuming and expensive process, so if that documentation doesn’t help the development process then it shouldn’t be created at all.

Teams should choose a methodology that is appropriate to the project. Generally the larger and more distributed the team or the more critical a project is, the greater the need for documentation.

Lefingwell also sets out the requirements framework for three distinct types of projects. One using Extreme Programming, a larger project still using an agile methodology, and a project requiring a more robust methodology.

By understanding that requirements documents are created to manage risk and by recognizing likely sources of project risk, a development team can tailor their requirements methodology to meet the needs of an individual project.

Recently Written

The Trap of The Sales-Led Product (Dec 10)
It’s not a winning way to build a product company.
The Hidden Cost of Custom Customer Features (Dec 7)
One-off features will cost you more than you think and make your customers unhappy.
Domain expertise in Product Management (Nov 16)
When you're hiring software product managers, hire for product management skills. Looking for domain experts will reduce the pool of people you can hire and might just be worse for your product.
Strategy Means Saying No (Oct 27)
An oft-overlooked aspect of strategy is to define what you are not doing. There are lots of adjacent problems you can attack. Strategy means defining which ones you will ignore.
Understanding vision, strategy, and execution (Oct 24)
Vision is what you're trying to do. Strategy is broad strokes on how you'll get there. Execution is the tasks you complete to complete the strategy.
How to advance your Product Market Fit KPI (Oct 21)
Finding the gaps in your product that will unlock the next round of growth.
Developer Relations as Developer Success (Oct 19)
Outreach, marketing, and developer evangelism are a part of Developer Relations. But the companies that are most successful with developers spend most of their time on something else.
Developer Experience Principle 6: Easy to Maintain (Oct 17)
Keeping your product Easy to Maintain will improve the lives of your team and your customers. It will help keep your docs up to date. Your SDKs and APIs will be released in sync. Your tooling and overall experience will shine.


What I'm Reading


Adam Kalsey

+1 916 600 2497


Public Key

© 1999-2023 Adam Kalsey.