Pedro Arantes
HomeBlogMe

Identify in Advance Which Requirements You Would Consider Eliminating or Relaxing

If you preplan which requirements your team can scrap, you can structure your product architecture to make it easy to discard them.
#architecture
Zettelkasten, November 23, 2022.

Notes

In product development, when WIP becomes high, you can control it by shedding requirements. It's best to identify in advance which requirements you would consider eliminating or relaxing for two reasons.

First, you can make a more well-reasoned decision before the pressure of a congestion crisis occurs. Second, if you preplan which requirements your team can scrap, you can structure your product architecture to make it easy to discard them—you loosely couple them to the rest of the system, so you can cut them loose quickly.

Questions

  1. What are some factors to consider when deciding which requirements to eliminate or relax?
  2. How can you structure your product architecture to make it easier to jettison requirements later on?
RecommendationsDo you want to see all posts instead?
Control WIP by Shedding Requirements
Newsletter
On Tuesday (not weekly), I publish my most recent readings and thoughts. Subscribe to my newsletter if you want to follow posts about #startups, #product-development, #mental-models, and more.

By subscribing, you agree with Revue’s Terms and Privacy Policy.