Unknown Fact About Technical Feasibility For Projects
In my previous article, I have talked about all that you need to know about Cultural feasibility for projects. In this article, I want to talk about all that you should know about Technical feasibility for projects. Follow me as we are going to look at that together in this article.
Technical feasibility is a study to analyse the hardware, software, facilities, and databases needed for a proposed project. The technical feasibility of a project cannot be determined until the impact on existing systems is fully quantified.
A Subject Matter Expert should be brought in to assist in the quantification of the impact of the system when you encounter the following situation:
- The proposed IT project has never been done before.
- The proposed IT project will interact with any key business process or mission-critical systems.
- The project team for the proposed project does not contain personnel certified as experts on the platform in question
- The systems pact cannot be accurately recreated and tested in a simulation environment.
Let’s look at the example of a local deli that specialises in providing takeout services for a nearby set of large office buildings. The owners of the deli had one of their employees, Jim, who is a student at the local university, build a Microsoft Access database for the purpose of tracking information surrounding their growing takeout business.
Several successful marketing campaigns developed an awareness of the deli’s services, and the takeout business was not responsible for over 60 percent of revenue and 75 percent of profit.
Predictably, the information in the database grew dramatically, and within 18 months, the business had outgrown the original database. The owners want to upgrade the database but are unsure if they should bring in outside help or let Jim handle the situation.
Let us compare this situation to our definition :
- Neither the deli owners, not Jim have ever done anything like this before.
- The proposed IT project will interact with a vital revenue stream that contributed 75percent of the total profit.
- The project team does not contain anyone certified as an expert with the platform.
- The deli owners do not have the technical or financial resources required to construct a trusted environment that will allow for a test of any upgrade.
The deli owners decide to bring in an outside firm to help them with the situation because they met the conditions described as requiring a Subject Matter Expert. Within the first 15 minutes of the discussion, the owners are told that all the information in their database can be transferred to a more capable database platform, but they lacked the expertise to upgrade Access to SQL or Oracle.
A database designer is brought in and within a month the deli owners are up and running with a powerful new solution that Jim is bring trained to administer.
First time/First use penalty
Many IT projects suffer from what is called a first time/first use penalty, which means that a particular type of project has never been done before and nobody within the organisation has any experience with the operation of this new capability.
One of the more serious first time/first use penalties is the proper quantification of the impact that the change will make to existing systems.
Because nobody within the organisation has experience with the situation at hand. SMEs will be needed to provide a detailed look at the impact of the system that can be expected. It is exceedingly difficult to determine the technical achievability of any IT project until the effect on existing systems is fully quantified.
I know you might agree with some of the points that I have raised in this article. You might not agree with some of the issues raised. Let me know your views about the topic discussed. We will appreciate it if you can drop your comment. Thanks in anticipation.
Become Part Of our Fan Base on Facebook. Click Here.
Follow Us on Twitter. Click Here.
Have a deeper understanding of Google Search Console. Join SEOPOZ for free