- Business case vs. business plan
A business case is a set of reasons that describe how a business decision will improve a product, business, and how it will impact costs and profits.
Business case vs. business plan
A business case revolves around a single action or decision and its potential alternatives while a company plan revolves around the whole organization or enterprise. A business case predicts the results of a cash flow that follow a given action, while a business plan predicts the performance of a business, especially regarding the major categories of the income statement. The focus of the business case is on the objectives of the business actions while a business plan outlines the objectives of a business. A business case relies on cost models and benefits rationale particular to the case while a business plan relies on the business model of an organization and the desired trends and competitor actions. A business case measures financial business metrics like return on investment, internal rate of return, payback period, etc. based on the anticipated cash flows. A business plan, on the other hand, measures the performance of an enterprise in light of profits, margins, business health, and sales.
- The systems analysts and stakeholders relationship
System analysts work in liaison with stakeholders for the purpose of understanding the policies, structure and operations of a business and recommend the solutions that can help an organization to meet its objectives. The system analyst guides the production of a business case and he/she works with the stakeholders so as to get the necessary ideas and requirements that they want included in the business case. The stakeholders may note flaws in the organization and then it is upon the system analyst to devise the required business case that embodies the actions needed to address those problems in the organization. A system analyst comes up with a proposal, but it will not have an implementation without the support of the stakeholders. Stakeholders come up with ideas, but it is the system analyst to turn those ideas to a technical solution.
- Reasons why projects fail and use of a business case to mitigate them
The development team may begin the project without the understanding of the scope of the project. It may result from poor analysis and definition of project requirements.
Poor resource allocation
The resources allocate for the project may not be sufficient for it to move from initiation to completion. There can also be over the allocation of resources that developers have confusion of how much of the resources to use in each phase.
There may be poor communications between the project manager and the project team, or poor communication between the project team members, or developers and major stakeholders.
Poor stakeholder engagement
The project manager may fail to identify all the project stakeholders.
Poor project estimates
Project estimation may take place based on insufficient information and analysis, or those that will do the work may lack inclusion during the time of making estimates.
Lack of risk management
The developers may seek risk management as an independent activity and not an integral of the planning process. They may as well confuse risk, problems, and issues.
Control and monitoring issues
Project managers may come up with the project schedule but fail to update it, or they may just fill in insufficient data without entering the exact data.
There may be failure to discuss project quality requirements, and so many people may have a different expectation of the standards to have the achievement.
How a business case can help mitigate causes of project failure
The business case offers the justification for a project, stating why certain actions should take place in a certain way (Molisan & Graham, 2008). It justifies the actions taken during the project planning and development. The senior management and the project manager use the business case to assess the success of the project right from the start (Vincent, 2009). It includes the why a project is in the requirement, expected benefits, commercial aspects of the project, potential risks, and time sales for the project. So because it incorporates the justification for every action and decision, it will prevent a project from failing.
- Business driver and project planning, technology driver, and its impact on projects
A business driver is a detailed set of tools that help in managing a project and the business. It serves as a catalyst for facilitating communication among workgroups in a project. Its relation to project planning is that it sets out the guidelines to fro communication among the various project teams and between the developers and stakeholders. That communication guideline and tools will help the planning team to plan effectively regarding the collaboration of participants within the project.
Technology drivers are IT and communication services that support technology development, competition and emerging requirements (Mohiuddin, 2007). Technology drivers incorporate automation into projects, speeding up the development process. They improve communication between the project stakeholders, and this leads to quickened decision-making and timely mitigation of issues and risks in project development.
- Zachman Framework has had a significant impact on Enterprise Architecture. Discuss Enterprise Architecture as it relates to a project and how it impacts the role of the Analyst
Enterprise Architecture is a practice for conducting analysis, design, planning and implementation of an enterprise. It uses the architecture principles as well as practices to lead the organizations via the business, process, technology changes and information that are essential in executing their strategies. Those principles and practices use various enterprise aspects identify, drive and accomplish these changes. It resembles the process of project development as it entails the elements of a project such as requirements specification, planning, designing, implementing and change management (Alex, 2013). An enterprise offers guiding principles, requirements, conceptual models and specifications that entail a description of the next major phase of organizational evolution. Enterprise architecture analyzes the differences between the current state of an organization and the target state and offers a roadmap of how to bridge the gap that exists between the current state and the future state.
Enterprise architecture promotes dialog to create a shared insight and deliver the common goals (Greefhorst & Propper, 2009). It enables the senior management to make spearhead efficiency, effectiveness and responsiveness aimed at achieving the desired goals and objectives. It aims at improving the performance of a business and satisfies the needs of the stakeholders. It integrates project delivery process in ensuring the success and achievement of the targets of the organization executives. The business analyst is the one who has the mandate of analyzing the business needs of customers and propose solutions. His/her role overlaps with the role of the enterprise architecture. The analyst have the technical skills required for the modeling part and understands the way to go in solving problems to meet the needs of the clients and stakeholders. However, enterprise architecture takes up his/her role, or it impedes his/her role, causing major conflicts in an organization in light of the strategies required to achieve business goals.
Alex, D. (2013). The clash between enterprise architecture and project management.
Greefhorst, D. & Propper, E. (2009). Enterprise Engineering: Architecture Principles – The Cornerstones of Enterprise Architecture. In Jan L.G. Dietz, Erik Proper & José Tribolet (Eds.), Architecture Principles the Cornerstones of Enterprise Architecture. Heidelberg: Springer.
Mohiuddin, S. (2007). The business technology drivers and benefits of SOA.
Molisan, J. & Graham, B. (2008). How to build a business case.
Vincent, S. (2009). Business case made simple.