Summary
In this chapter, we covered elicitation planning. You learned about different tools and techniques of elicitation and that you have to use more than one tool and technique to bring forth requirements. Now you know that you need to take as many notes as possible so as not to lose any valuable information, and then take all this knowledge and write great requirements. You transform business users’ expressed and unexpressed intentions, thoughts, and ideas, and document clear, crisp formalized requirements that eventually add value to all your stakeholders.
In the next chapter, we will take these requirements and work on prioritizing them. We will cover techniques that you can use that help you prioritize your requirements so that the technical team can add value during solution design and development activities.
