Requirements collection is a vital element in getting projects delivered in an efficient fashion. In this video, Bob McGannon takes you through the "what” factor, as a means of defining business needs. In addition, learn best practices for writing your requirements including describing steps, decisions, defining users and acceptable deviations for each deliverable.
- Clearly defining your project requirements…is vital to getting things done in an efficient fashion.…Let's say you need to buy a lawnmower.…State your requirements correctly,…and you can end up with a sleek machine…that cuts your grass and collects the clippings,…and maybe you can ride it.…Do it incorrectly and you can end up with a goat.…You may get your grass cut,…but you'll have care and feeding needs…you didn't anticipate.…For technology project requirements,…it's essential to define the business need.…
I refer to this as the what as in what you need.…As this stage you'll want to avoid defining…the actual technological solution, which is the how.…It's very tempting to describe the requirement…with how terminology, but ultimately this is restrictive…and may not provide you the best solution…based on your actual needs.…It's best practice to work with your stakeholders…and help them describe their needs…in what versus how language.…
For example, let's say you need to use your solution…at a hot, dusty mining location,…
- Identify three characteristics of the ideal To Be process map.
- Summarize the steps to manage organizational change.
- Recognize three details to consider when evaluating a cloud solution.
- Recall the consequence of failing to address functionality gaps in a technical solution.
- Determine which facts to collect before discussing resource availability with sponsors.
- Identify the questions to ask when asking team members for feedback on milestone development.