In this Chapter, I have suggested using a checklist of 28 steps that comprise a procedure for gathering requirements. This may seem like a lot of steps, perhaps suitable only for a large, mature project. Actually, projects of all sizes and all levels of maturity will need to address these steps! All projects will address these steps whether in an orderly or haphazard fashion. I have emphasized that when the requirements gathering approach is not effective, the stage is set for wasted technical effort during follow-on project activities (read: the rest of the project), creating the need for rework and jeopardizing the success of the project. I have another suggestion for you: read Wiegers's "Habits of Effective Analysts" [39]. In this article, another industry expert ^[11] shares his views. I think that you'll find a lot of correspondence between this chapter and Wiegers's advice. Visit his Web site and take advantage of his many suggestions, writings, ideas, prescriptions, and "goodies". Wiegers, Ian Alexander, Ivy Hooks, Jeff Grady (and I) provide effective requirements training and consulting.

Think broadly. Be flexible. Always foster teamwork and continuous improvement in everything that you do. Review Chapter 3 periodically (say over a weekend) and think about the things you should be doing or doing differently. Be a positive influence on others and the project. Ask your manager for feedback concerning how you are performing. Act on it. Have fun.