2. Benefits
• Lower Project Costs
– Significantly reduces costly rework
– Managing cost by reducing or eliminating extraneous features
– Significant defects are caught at the earliest possible time instead of the most
costly time after the system has been deployed.
– Promotes reuse of common requirement artifacts such as business rules, business
process models, etc.
• Promotes Communications
– Improves communications between team members and business owners through a
formal requirements requirements management planning process.
– Offers a formal process for proposing and managing changes to requirements.
– Keeps stakeholders involved through the project lifecycle including design
reviews, user acceptance testing, and deployment.
• Reduces Project Risk of Failure
– Good requirements significantly reduce the risk of project failure.
– Provides the means to more accurately estimate timeframes and work estimates
and control project scope
1
4. Requirement Excellence Framework™
The Enfocus Solutions’ Requirement Excellence
Framework™ is a new comprehensive approach, based on
industry best practices, to develop, manage, and improve
project requirements. It support the following activities:
• Business Rules • Elicitation
• Business Process Knowledge • Analysis
• Product Knowledge Management • Specification
• Stakeholder Knowledge Management • Validation
• Project Vision • Change Control
• Business Objective Definition • Requirement Bundling
• Project Scope Definition • Lifecycle Management
• Stakeholder Analysis • Project Retrospective
• Business Process Analysis
3
5. RequirementPro™
Enfocus Solutions’ Requirement Pro™ guides you through
creating a project vision, business objectives, and project scope
statements to ensure that the Project Owner, Project
Managers, Business Analysts, Developers, and Stakeholders all
have a shared understanding the expected project outcomes.
– Fully automates all activities defined in the Requirement
Excellence Framework™
– Enfocus Solutions’ Requirement Pro™ can be accessed
securely using a web browser without installing or
maintaining any additional software.
– Guides you to a more accurate cost estimate due to better-
defined and complete requirements.
4
6. Stakeholder Portal™
The Stakeholder Portal™ provides an intuitive web-based
system that encourages and engages stakeholder
participation in requirements management activities.
Stakeholders can define their own needs in words they
understand.
– Web-based collaboration
– Facilitates a common understanding of the project vision and
scope and the business objectives.
– Addresses all aspects of strategy, people, process, and
technology.
– Encourages active stakeholder participation in project lifecyle
events such as requirement
development, design, development, acceptance testing, and
deployment
5
7. Requirement Coach™
Requirement Coach™ is an integral component that provides not
only implementation and process guides, but also best practice aids
and templates to assist teams in successfully crafting and managing
requirements through the entire project lifecycle.
– Hundreds of templates, examples and checklists on a variety of subjects
– Full access to eLearning courses developed by industry expert Karl Wiegers
– Hundreds of pre-written Agile personas and Stakeholder analysis
templates
– Thousands of pre-written requirements organized by business process
– Business Process Benchmarking Tools
– Requirement Elicitation Questions for a variety of areas
6
8. Key Product Differentiators
• Requirement Coach™ - Examples and practice aids significantly improve get
requirements development off to a quick start and significantly improve
business quality.
• Business Vision and Expectations - Captures what the business expects from
the solution Most tools totally ignore this vital part of requirements.
• Stakeholder Focused - Uses collaborative technology to elicit needs from
stakeholder. Most tools on the market are focused on the developer and not
the stakeholder.
• Product and Project Relationship Mapping - Captures requirements that are
automatically related to both projects and products and services.
• Mapping of Needs to Requirements - Stakeholders can see how their needs
are mapped to requirement specifications provided to developers. Other tools
capture requirements for a product or project, but not both simultaneously.
7
9. Key Product Differentiators
• Patterns - Requirements and needs are defined using patterns. Other tools on
the market ignore this key best practice for managing requirements.
• Capture of Expanded Requirement Types - Capture non-software
requirements such as training, business process changes, infrastructure, etc.
Other tools focus only on software requirements.
• Requirement Bundling - Requirements are organized and managed as
bundles to support a wide variety of options. Most tools are very rigid and
assume that only one requirement document will be produced.
• Special Stakeholder Groups - Allows special stakeholders such as compliance
officers, internal auditors, etc., to actively participate in the requirements
process. - Other tools do
8