What do you think is the relationship between Business and Information System plan? To further discuss let us know what does it mean.Business PlanBased on the Wikipedia,A business plan is a formal statement of a set of business goals, the reasons why they are believed attainable, and the plan for reaching those goals. It may also contain background information about the organization or team attempting to reach those goals.The business goals may be defined for for-profit or for non-profit organizations. For-profit business plans typically focus on financial goals, such as profit or creation of wealth. Non-profit and government agency business plans tend to focus on organizational mission which is the basis for their governmental status or their non-profit, tax-exempt status, respectively—although non-profits may also focus on optimizing revenue. In non-profit organizations, creative tensions may develop in the effort to balance mission with "margin" (or revenue). Business plans may also target changes in perception and branding by the customer, client, tax-payer, or larger community. A business plan having changes in perception and branding as its primary goals is called a marketing plan.Business plans may be internally or externally focused. Externally focused plans target goals that are important to external stakeholders, particularly financial stakeholders. They typically have detailed information about the organization or team attempting to reach the goals. With for-profit entities, external stakeholders include investors and customers. External stake-holders of non-profits include donors and the clients of the non-profit's services. For government agencies, external stakeholders include tax-payers, higher-level government agencies, and international lending bodies such as the IMF, the World Bank, various economic agencies of the UN, and development banks.Internally focused business plans target intermediate goals required to reach the external goals. They may cover the development of a new product, a new service, a new IT system, a restructuring of finance, the refurbishing of a factory or a restructuring of the organization. An internal business plan is often developed in conjunction with a balanced scorecard or a list of critical success factors. This allows success of the plan to be measured using non-financial measures. Business plans that identify and target internal goals, but provide only general guidance on how they will be met are called strategic plans.Operational plans describe the goals of an internal organization, working group or department. Project plans, sometimes known as project frameworks, describe the goals of a particular project. They may also address the project's place within the organization's larger strategic goals. Business plans are decision-making tools. There is no fixed content for a business plan. Rather the content and format of the business plan is determined by the goals and audience. A business plan should contain whatever information is needed to decide whether or not to pursue a goal.For example, a business plan for a non-profit might discuss the fit between the business plan and the organization’s mission. Banks are quite concerned about defaults, so a business plan for a bank loan will build a convincing case for the organization’s ability to repay the loan. Venture capitalists are primarily concerned about initial investment, feasibility, and exit valuation. A business plan for a project requiring equity financing will need to explain why current resources, upcoming growth opportunities, and sustainable competitive advantage will lead to a high exit valuation.Preparing a business plan draws on a wide range of knowledge from many different business disciplines: finance, human resource management, intellectual property management, supply chain management, operations management, and marketing, among others. It can be helpful to view the business plan as a collection of sub-plans, one for each of the main business disciplines. "... a good business plan can help to make a good business credible, understandable, and attractive to someone who is unfamiliar with the business. Writing a good business plan can’t guarantee success, but it can go a long way toward reducing the odds of failureIS PlanCharacteristic DescriptionTimely -The ISP must be timely. An ISP that is created long after it is needed isuseless. In almost all cases, it makes no sense to take longer to plan workthan to perform the work planned.Useable- The ISP must be useable. It must be so for all the projects as well as foreach project. The ISP should exist in sections that once adopted can beparceled out to project managers and immediately started.Maintainable -The ISP should be maintainable. New business opportunities, newcomputers, business mergers, etc. all affect the ISP. The ISP must supportquick changes to the estimates, technologies employed, and possibly evento the fundamental project sequences. Once these changes areaccomplished, the new ISP should be just a few computer programexecutions away.Quality- While the ISP must be a quality product, no ISP is ever perfect on the firsttry. As the ISP is executed, the metrics employed to derive the individualproject estimates become refined as a consequence of new hardwaretechnologies, code generators, techniques, or faster working staff. Asthese changes occur, their effects should be installable into the data thatsupports ISP computation. In short, the ISP is a living document. It shouldbe updated with every technology event, and certainly no less often thanquarterly.Reproducible- The ISP must be reproducible. That is, when its development activities areperformed by any other staff, the ISP produced should essentially be thesame. The ISP should not significantly vary by staff assigned.The ISP Steps The information systems plan project determines the sequence for implementing specific information systems. The goal of the strategy is to deliver the most valuable business information at the earliest time possible in the most cost-effective manner. The end product of the information systems project is an information systems plan (ISP). Once deployed, the information systems department can implement the plan with confidence that they are doing the correct information systems project at the right time and in the right sequence. The focus of the ISP is not one information system but the entire suite of information systems for the enterprise. Once developed, each identified information system is seen in context with all other information systems within the enterprise. Information Systems Plan Development Steps Step Name Description 1. Create the mission model -The mission model, generally shorter than 30 pages presents end-result characterizations of the essential raison d=etre of the enterprise. Missions are strategic, long range, and a-political because they are stripped of the Awho@ and the Ahow.@ 2. Develop a high-level data model -The high-level data model is an Entity Relationship diagram created to meet the data needs of the mission descriptions. No attributes or keys are created. 3. Create the resource life cycles (RLC) and their nodes -Resources are drawn from both the mission descriptions and the high level data model. Resources and their life cycles are the names, descriptions and life cycles of the critical assets of the enterprise, which, when exercised achieve one or more aspect of the missions. Each enterprise resource Alives@ through its resource life cycle. 4. Allocate precedence vectors among RLC nodes -Tied together into a enablement network, the resulting resource life cycle network forms a framework of enterprise=s assets that represent an order and set of inter-resource relationships. The enterprise Alives@ through its resource life cycle network. 5. Allocate existing information systems and databases to the RLC nodes -The resource life cycle network presents a Alattice-work@onto which the Aas is@ business information systems and databases can be Aattached.@ See for example, the meta model in Figure 2. The Ato-be@ databases and information systems are similarly attached. ADifference projects@ between the Aas-is@ and the Ato-be@ are then formulated. Achievement of all the difference projects is the achievement of the Information Systems Plan. 6. Allocate standard work break down structures (WBS) to each RLC node -Detailed planning of the Adifference projects@ entails allocating the appropriate canned work breakdown structures and metrics. Employing WBS and metrics from a comprehensive methodology supports project management standardization, repeatability, and self-learning. 7. Load resources into each WBS node -Once the resources are determined, these are loaded into the project management meta entities of the meta data repository, that is, metrics, project, work plan and deliverables. 8. Schedule the RLC nodes through a project management package facilities. -The entire suite of projects is then scheduled on an enterprise-wide basis. The PERT chart used by project management is the APERT@ chart represented by the Resource Life Cycle enablement network. 9. Produce and review of the ISP -The scheduled result is predicable: Too long, too costly, and too ambitious. At that point, the real work starts: paring down the suite of projects to a realistic set within time and budget. Because of the meta data environment (see Figure 1), the integrated project management meta data (see Figure 2), and because all projects are configured against fundamental business-rationale based designs, the results of the inevitable trade-offs can be set against business basics. Although the process is painful, the results can be justified and rationalized. 10. Execute and adjust the ISP through time. -As the ISP is set into execution, technology changes occur that affect resource loadings. In this case, only steps 6-9 need to be repeated. As work progresses, the underlying meta data built or used in steps 1-5 will also change. Because a quality ISP is Aautomated@ the recasting of the ISP should only take a week or less. Collectively, the first nine steps take about 5000 staff hours, or about $500,000. Compared to an IS budget $15-35 million, that's only about 3.0% to 1.0%. If the pundits are to be believed, that is, that the right information at the right time is the competitive edge, then paying for an information systems plan that is accurate, repeatable, and reliable is a small price indeed. Executive and Adjusting the ISP Through Time IT projects are accomplished within distinct development environments. The two most common are: discrete project and release. The discrete project environment is typified by completely encapsulated projects accomplished through a water-fall methodology. In release environments, there are a number of different projects underway by different organizations and staff of varying skill levels. Once a large number of projects are underway, the ability of the enterprise to know about and manage all the different projects degrades rapidly. That is because the project management environment has been transformed from discrete encapsulated projects into a continuous flow process of product or functionality improvements that are released on a set time schedule. Figure 3 illustrates the continuous flow process environment that supports releases. The continuous flow process environment is characterized by: •Multiple, concurrent, but differently scheduled projects against the same enterprise resource •Single projects that affect multiple enterprise resources •Projects that develop completely new capabilities, or changes to existing capabilities within enterprise resources In summary, any technique employed to achieve an ISP must be accomplishable with less than 3% of the IT budget. Additionally, it must be timely, useable, maintainable, able to be iterated into a quality product, and reproducible. IT organizations, once they have completed their initial set of should apply databases and business information systems will find themselves transformed from a project to a release environment. The continuous flow environment then becomes the only viable alternative for moving the enterprise forward. It is precisely because of the release environment that enterprise-wide information systems plans that can be created, evolved, and maintained are essential. RELATIONSHIP between the 2We know that both of them have a Deeper analization, it means each of them should follow steps but in the case of IS plan it is more detailed. when we say planning, it is in organizations and public policy is both the organizational process of creating and maintaining a plan; and the psychological process of thinking about the activities required to create a desired goal on some scale. As such, it is a fundamental property of intelligent behavior. This thought process is essential to the creation and refinement of a plan, or integration of it with other plans, that is, it combines forecasting of developments with the preparation of scenarios of how to react to them.
References:http://www.tdan.com/view-articles/5262
No comments:
Post a Comment