The Wayferry Navigator is designed to collect the information needed to implement the new software. Since requirements specify WHAT the new software needs to deliver and is organized hierarchically, the Navigator can export them in WBS format. (Work Breakdown Structure). This export is used for the following:

• When estimating implementation work.
• To create the first draft of the implementation project plan.
• When managing the implementation project.

Exported requirements are in MS Excel in a WBS format that can be imported into a project management system like Smartsheet.

<aside> 💡 If a System Integrator's system can't import the WBS Excel file, it can be imported into Smartsheet and then exported in Microsoft Project format, which most project management systems recognize.

</aside>

Requirements not found during the requirements analysis are usually found during implementation. This is often called scope creep, but it is not; rather, it results from an inadequate requirements analysis. If requirements are not found during implementation, they are found when going live in production. The later requirements are found, the more the cost to satisfy.

For the above reasons, Wayferry requirements are organized hierarchically, and clients can go into as much depth as they want.

<aside> 💡 The "devils are in the details." Those devils are the assumptions the buyer makes about the software that, after the implementation, are found to be false.

</aside>

How to do a WBS export

When reporting the RFP, you MUST select the product from the “Evaluation products” page and click on [Export - Smartsheet] button. If you don't select a product, only the requirements will be exported.

Estimating implementation times

After importing requirements into a project management system like Smartsheet, the System Integrator looks at them as follows:

• Requirements rated as "Fully meets" are met "out of the box" and do not need any configuration time.
• Requirements rated as "Fully meets (system config)" need an estimate of how much time will be spent configuring the software to meet that requirement. Example: Configuring the chart of accounts in an ERP system.
• Requirements rated as "Fully meets (user config)" will not need any time spent on them, but users will need to be trained on them.
• Requirements rated as less than "Fully meets" will need some thought as to how they will be handled.

<aside> 💡 Almost all requirements in a Wayferry RFP are business requirements, not software requirements. Business requirements specify WHAT the software must deliver, while software requirements specify HOW the new software will be configured to deliver those deliverables.

</aside>

Managing the implementation project

When requirements are exported in WBS format, the following information from each requirement includes: