Earlier this week I talked about the value of process. But what happens when the steps kill the project.
This is where experience is crucial. Being able to be comfortable and understanding the process you are working to follow allows you to be able to identify when a step can be modified and what the various downstream repurcussions are. An example from this week was:
Wanting to help a client automate a process, we looked to leverage a sandbox that was being created to replace a manual process. Easy-peasy.
The issue was the downstream issues based on not using a proper and pure production environment. Happily the team that was doing a Rapid Results approach to this had an understanding of the issues that this would create (back-up, change control, support,…) and be able to either shoot the solution or find the work-outs to address them.
This was an example where if we had had to go to a full big P production solution the cost of this simple automation would have exceeded the project budget for the bigger project. That would have meant that the business would not have been able to get their solution, the Enterprise Data Warehouse would be thought as too expensive and someone else would have found a work-around and no-one would win.
Powered by Qumana