Components of a Good Software Needs Analysis
Solution Explorers on November 23rd, 2009. Under Discovery: Needs Analysis
What is a Needs Analysis? In its simplest form, this is a process of identifying and evaluating problems (issues, pains, frustrations) and solutions to these problems. Stated differently, you are most likely looking at the variance between actual vs. expected results. Also, the process predominantly focuses on needs and not wants (wish list items are ok too though) and is forward-looking.
When your business or organization decides to purchase new software or upgrade an existing software application, take some time to create (or hire someone to create) a system requirements document BEFORE initiating direct contact with software providers. The requirements list is an inherent by-product of a good Needs Analysis. Just as important, don’t forget to consider opportunities that may be created via improved and additional product functionality. In doing so, you will have a wholesome view in place that will serve as the foundation for evaluating viable solutions.
A good Needs Analysis will often produce the following:
- List of current functional and reporting issues, deficiencies.
- List of current functional and reporting “must haves” to retain in the next system.
- Groups/Categories – Security, Core functions, Reporting/Analytical, Technical environment, etc.
- “Blue sky” wish list items – dream, shoot for the stars here, but be realistic.
- List of goals (purchase, configuration, Go Live) and resources (reviewers, decision makers, and financial capabilities).
Finally, don’t forget to prioritize your itemized lists because this step will guide you later in the process.
Now, help expand the definition and listed items above by sharing your thoughts. Together, we can “transform the software technology buying and selling experience.” As a result, your next software evaluation and purchase experience will surely be rewarding!
