You can produce a fabulous technological wonder, but if it cannot be easily applied to a business problem, it isn't going to be worth much. In this video, Bob McGannon gives you an overview of the techniques you can use for vital testing of your technical deliverables, including the testing of business processes, forms and reports and overall department impacts.
- A common phrase in the technology world…is a fool with a tool is still a fool.…You can produce a technological wonder,…but if it can't be easily applied to a business problem,…it isn't gonna be worth much.…To make sure your technology is worthwhile,…testing needs to be a significant part of your project.…The validity of business processes,…ensuring that forms and reports are suitable,…and the end-to-end impacts to departments…in your organization needs to be tested.…
Here's an overview of the techniques you can use…for these vital testing elements.…First are the business processes.…Hopefully you've produced to-be process maps.…If you've not, testing your business process…is very difficult as you won't know what to test.…If you haven't done so, consider creating at least…high level process maps.…For each process map, perform a walk-through…using a few business scenarios.…Representatives from the areas impacted by the process…should be part of this walk-through.…
Have the owner of the process describe…what they think should happen…
- 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.