The intention of writing this section is to make use of something which we call the brief requirement gathering. This is not to be confused with detailed requirement gathering, which we will be covering in the subsequent chapter.
We mentioned in the earlier chapter (Chapter 2, Preparing for the project) about the organizational hierarchy and the roles people play. We also mentioned that it's important to understand requirements at every stage of pyramid. This helps you achieve project success and also helps the adoption to go up substantially.
As you start meeting the stake holders at top layers of the pyramid, the amount of time they spend with you will go down as you go higher up the layers. The people on top of pyramids can help you drive adoption when they start using the software themselves.
The consultant must do this brief requirement gathering...
