Coverage

Coverage focuses solution discovery and development processes on meeting specific organization needs, with a clear definition of completion.

Ideally, requirements should cover all organization needs within a scope. However, if some requirements cost too much, stakeholders negotiate to satisfy them another way. For example, they may choose to perform some processes manually because they don’t justify automation.

Discovery completes when requirements cover 100% of the needs within scope. Development completes when a solution covers 100% of the requirements within scope.

Click a title to see excerpts

Coverage: How Much is Enough? (Key Story)

Coverage: How Much is Enough? excerpts:

• Ideally, you want to discover all of the user needs within the solution scope. Stakeholders rarely have enough time, energy and attention to reach that goal. They rarely think of everything they need from a new solution. If your solution replaces an existing solution, the stakeholders may not recall everything that your replacement solution should cover. Upcoming posts in this blog will show you how to get closer to ideal coverage.
• The Business Analyst, Architect, and stakeholders should at least discover the downside of uncovered needs. Those needs may not be worth fulfilling in the current scope, making the risk acceptable. If you develop solutions for a regulated industry, you need to have 100% coverage of regulatory requirements.