If your RFP makes it to the demo shortlist and you are invited to demonstrate your software to our client, to help you prepare your proposal we will export your RFP in WBS format to Excel. You can then import the file into smartsheet.com as a project and view it as a Gantt chart.
This file defines WHAT the software should deliver and you, as the system integrator, need to decide how much work it will take to implement that functionality.
- The spreadsheet is organized hierarchically and can be imported into Smartsheet as a work breakdown structure. You can expand and collapse the rows as needed to view details.
- There are different types of requirements:
- Leaf requirements (i.e. at the end of a branch). These are what you implement.
- Parent requirements contain other requirements. These provide the hierarchical structure, but you don't implement them.
- Root requirements. These are top-level parent requirements and are what you will see when you open the spreadsheet.
- The spreadsheet specifies WHAT is wanted by the client. You, as project manager, can add HOW long it will take to configure your product to deliver the WHAT. Note that to manage costs, the client may decide not to implement some functionality they have prioritized (weighed) as showstoppers.
- Leaf requirements include the following:
- Description - WHAT the software must deliver to create value for the client.
- Example - puts the requirement into context and reduces ambiguities.
- Reasons for the requirement - describes the business value created by the software meeting the requirement.
- Note - anything else
- Weight - client priority
- Client-specific reasons - the names of the client people who are interested in the requirement. These are the people to reach out to when you have questions.
- How met - describes how your software meets the requirement. Requirements that are set to:
- Base product - don't need any work to configure. They are met "out of the box" by your software.
- Base product (system config) - will need work by your team to be configured.
- With code - will require writing event-triggered scripts etc.
- ... and so on - will explain at our meeting.
Untitled