Guided Reading
- Sivan Arar Reuven
- Sep 1, 2006
- 2 min read
"If you want things to happen - make them happen" (Diogenes)
One of the major challenges in writing technical specifications is their implementation... A system specification, written with sweat and tears, is often improperly implemented. Although most of us score well in "reading comprehension," we discover that sometimes multiple interpretations can be given to what is written. The specification process is long and not simple. Many hours are invested in user interviews, information and knowledge provider interviews, and detailed specifications writing. Similarly, developing or implementing a system is expensive and takes a long time. To ensure that the author's intention in the specification is understood and that the product we receive after development will match what we requested, we recommend a "guided reading" of the specification.
What is meant by guided reading?
After writing the specification and before submitting its final version to the information systems people, it is recommended that a series of meetings (or one long meeting, depending on the length and complexity of the specification) be held between the client, the specification writer, the information systems project manager, and the developer and/or implementer.
During these meetings, the different sections of the specification are reviewed, clarification questions are asked, corrections are made, and comments are noted.
There are several objectives for guided reading:
Ensure that what is written in the specification is properly understood—this will save development time and resources.
Ensure that what is written in the specification is technologically feasible. If not, this is the place to request alternative solutions from information systems experts!
To obtain a cost-benefit assessment - is expensive development required that may not be worth investing in? (It's important to note that, in any case, we will see this in the price quote we receive. However, some development requirements can still be changed at this stage, saving valuable time).
This is the place to ask questions and "tie up loose ends": Information systems people can direct clarification questions to the client and the specification writer, the specification writer can direct questions to the client and information systems people, and of course, the client can direct questions to information systems people and the specification writer, thus ensuring that what they wanted is what they will get.
After completing the guided reading stage, a corrected and finalized specification can be issued. The guided reading process may require many working hours from all participants. However, it will save many unnecessary development hours.
Additional recommendation in this context: After development is complete, review the system alongside the specification and verify that what you requested appears as defined in the specification.
Comments