Background

To reduce the RFP Responder workload, most Wayferry projects have two RFPs. The only difference between these two RFPs is the number of requirements.

• The Demo RFP which, as the name implied, contains only requirements that are on the demo script. Typically the Demo RFP has only about 5% of the total number of requirements.
• The Full RFP. which, as the name implies, contains all requirements prioritized by the client.

How to rate your product

Rating a requirement is assigning a rating value that describes how well your software product meets a particular requirement, e.g., Fully meets. We use these ratings to calculate your product’s fit score, objectively measuring how well it meets the client’s business requirements.

When you respond to an RFP, your ratings are added to the Navigator library and can be reused for future RFPs.

<aside> 💡 About 20% of all requirements are parent requirements with children. Do not respond to parent requirements.

You only respond to green “leaf” requirements that don’t have children requirements.

</aside>

Open the evaluation

Open the evaluation as described on the Getting Started page. After opening the evaluation, you should see a screen similar to the one below. (This is if you clicked the list view)

Open the evaluation as described on the Getting Started page. After opening the evaluation, you should see a screen like the one below. (This is if you clicked the Descendants view)

Navigating to a requirement

To see how to rate a requirement, you need to navigate to it. We'll use "Financials" as an example, so click on the "Financials" row on the list. You will see a screen that looks like the one below.

"Financials" is a "parent" requirement. However, parent requirements can't be rated; only leaf requirements can. You'll need to navigate down to a "Leaf" requirement, which can be rated. Click on the "General Ledger" requirement (3), and then on the "Transaction audit trail" requirement (not shown), which will open a page similar to the one below.

Rating a requirement overview

When a requirement is opened for rating, you will see the requirement itself on the left [1]. At the top of the requirement is the name [2], to the right is the unique requirement ID [3], and below that is the description [4] which describes what the software must do to create value for the buyer. There may also be examples [5] to contextualize the requirement and remove ambiguities.