Business Systems Project Feasibility Why Is the

Business Systems Project Feasibility Why is the process of assessing project feasibility so important? What are the various methods for assessing project feasibility? Which factor is the most important? Why? Can there be a situation when one assessment factor is more important than another factor? Project feasibility is critically important because its series of techniques takes into account constraints vs. costs and the strategic value of the project overall.

Optimizing for these constraints is essential for keeping the strategic direction and foundation of a given project consistent and streamlined, so it can be achieved (Tao, Kung, 1991). The approaches used for completing project feasibility include SWOT analysis, cost effectiveness and cost-benefit analysis, and the use of distributed cash flow analysis to determine the Net Present Value (NPV) of a given project or initiative as well (Tao, Kung, 1991).

Often project planning and managers will sue a series of these tools in conjunction with another to understand all the facets of a given proposed project. Of the resources taken into account in completing project feasibility study, the most constrained resource is often time. Given the low interest rates and for many companies their low cost of capital as a result, time becomes the most crucial resource there is.

Quantifying the trade-offs of time relative to cost is essential if an organization is going to continually improve and choose the best possible initiatives and projects to invest in (Tao, Kung, 1991). Project feasibility is also essential to understand how each potential initiative contributes to the strengths and direction of the organization and which have the potential to detract from it. SWOT analysis and strategic scoping of initiatives from a financial standpoint provide these insights and mitigate risk (Tao, Kung, 1991). 2.

Process Modeling Data flow diagrams can be hard to develop and understand. In simple system design, data flow diagrams and process models may not be necessary. What do you think about not using data flow diagrams in some cases? Data flow diagrams and process models define the dependencies and decision points through a project, including how a given project plan will manage risk mitigation and trade-offs.

For the most simplistic of projects, data flow diagrams and process models are not necessary as their workflows are linear with little or no dependencies and trade-offs. For any project that is dependent on ancillary services, subprocesses or a significant amount of resources that need to be allocated across limited options, a process flow diagram is necessary. Process flow diagrams can assist in defining the optimal use of resources and serve to also reduce risk overall (Tao, Kung, 1991).

Process flow models' ability to optimize the performance of a given project and its subsystems make them essential for any project that has dependencies and reliance on constrained resources. A process flow diagram.