What other questions should I be asking? (This is always a good one for yielding unexpected answers!).What device will the stakeholder be using when they use this feature?.What if….? Think of all the alternative scenarios and ask questions about what should happen if those scenarios are true.What do I know about this feature? Or, what assumptions am I making about this feature that I need to confirm?.Who can I ask to learn more about this?.Who will learn about the results of someone using this feature?.Who will receive the outputs of the feature?.Who will deliver the inputs for the feature?.When does this need to be completed by?.Where would the user be located physically when using this feature? Are they at home? In the office? Offsite?.Where would the user access this feature?.How will we know this is complete? Or, what are the success criteria?.How might we think about this feature a bit differently?.Is this feature a process and, if so, what are the steps? Or, what questions can I ask to ascertain the steps?.How will your stakeholders use this feature?. ![]() Here’s some generic questions you can use to spur your thinking. Think about the how, where, when, who, what, and why. Just like a good story, requirements will answer all the important questions. But sometimes I need to spur my thinking a bit. Most of the time, the questions evolve naturally as I think through the implications of a feature. I write down what I know about that feature (or what I assume to be true about that feature). When creating a requirements questionnaire, I work through each feature one at a time. You can also download a sample checklist absolutely free of charge.) What Requirements Questions Should I Ask? (By the way, we’ve pulled together a collection of feature-specific questions and made them available in our Requirements Discovery Checklist Pack. One of our course participants reported eliminating several follow-up meetings by using our requirements questionnaire checklists and active listening techniques. Investing time in a requirements questionnaire will help ensure you engage your stakeholders, and also that you truly discover and not merely “gather” the requirements.Īnd while it might seem like this would take a lot of time, the reality is that a well-thought-out questionnaire helps you run a more effective stakeholder meeting and save you time in the long run. Essentially each high-level requirement from your scope document should have a list of questions to further refine your understanding. Typically the questions are organized by feature (or business requirement or project objective). What is a Requirements Questionnaire?Ī requirements questionnaire is a list of questions about the project requirements. If the scope of your project is not yet defined, you might want to check out “ 5 questions to ask before starting any technology project ” for some generic elicitation questions that work on most any project. ![]() This article is about identifying targeted questions for a project that has already been scoped, called a requirements questionnaire.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |