Web2Print Best Practices - Part II: Requirements Gathering
Jack Perry November 16 2009 08:37:09 AM
Program goals are defined through careful analysis of business requirements. Easier said than done. Like any project, it is easy to lose sight of boundaries; the place your program starts and the place it ends. An easy and effective way to maintain program boundaries is to use a modified Kano chart [kay-no]. Diagram 1.1 below is an example of the modified Kano chart we use in our professional service engagements.
Diagram 1.1
| Requirement: | Must Have | Nice to Have | Don't Need | Don't Know |
| Near Term | ||||
| Long Term | ||||
The Kano chart is an effective way to keep the team focused on business requirements that impact your web-to-print program. It's also an effective tool for helping the team to decide what considerations should be placed in the parking lot and which considerations should be dropped from further analysis.
For each business requirement being considered as part of the program, the facilitator can ask a serious of pointed questions, the results of which determine how the business requirement contributes to the overall program scope.
But first some definitions of the values within the Kano chart:
Requirement: the business need being analyzed by the team.
Near-term: focused on meeting requirements on day one the project goes live.
Long-term: a requirement that may be required at some time in the future in order for the program to be successful and sustainable, but is not required on day one.
Must have: this is a requirement that must be met either near-term or long-term in order to satisfy one or more constituents of the program. Not meeting the requirement will disappoint system users and may affect future program success.
Nice to have: the frosting on the cake. System users will be pleased to have this requirement met, but will not be disappointed if it is not.
Don't need: a requirement that is not needed on day one or anytime in the future based on current data.
Don't know: a program gap. A don't know answer while defining and documenting any business requirement leads to a gap assignment. A don't know must be moved to one of the other values (must have, nice to have, don't need) before the requirement is reconciled.
Practical Application of the Kano Chart Exercise: Example I
Business Requirement: Credit Card Payment Option
Question: Is end-user payment via credit card a near term or long-term requirement for the program?
Answer : Near-term. It's the only feasible way for our independent channel partners to purchase print.
Question: Is end-user payment via credit card a must have, nice-to-have, don't care, or don't know?
Answer: Must have. Our channel will be a primary user of the system on day one.
Result: Payment via credit card is a near-term must have. It should be documented appropriately in your business requirement documentation.
- Comments [0]