Putting It All Together BOI (IKEA)

[Pick the date] Replace with Proposal Title [Type the abstract of the document here. The abstract is typically a short summary of the contents of the document. Type the abstract of the document here. The abstract is typically a short summary of the contents of the document.]

Executive Summary

The executive summary should approximately ¾ of a page, single spaced. It should also be the ONLY thing on this page. An executive summary is a high-level view of what is contained in the rest of the document. The executive should find NO surprises in the supporting pages. It is your sales summary.

Unless you can peak the executive’s interest, this page may be the only one he/she ever reads!

Students should be able to pull the company background information from the Business of Interest (BOI) submitted in Week 1. In addition to the company background information, students need to make their case for the proposed change(s). Also see IS for Competitive Advantage from the work submitted in Week 2.

Competitive Strategy

Identify the BOI’s competitive strategy.

· See Competitive Strategy from Week 2.

IS for Competitive Advantage

Does the proposed change involve, foster or promote competitive advantage? If it does, include the relative supporting information. If a competitive advantage is included it is likely part of a change defined in a separate section of this document.

· See Competitive Forces from Week 2.

· See IS For Competitive Advantage from Week 2.

Collaboration

Does proposed change involve, foster or promote collaboration? If it does, include the relative supporting information. Modify and edit the information as required to address and support your proposed change.

· Collaboration from Week 1.

Data Silos

Does the proposed project involve a change to eliminate or improve inefficiencies caused by data silos? If it does, include the relative supporting information. Modify and edit the information as required to address and support your proposed change.

· See Data Silos from Week 4.

Web 2.0 – The interactive Internet

Does the proposed project involve a change to or an implementation of social media? If it does, include the relative supporting information. This would include social media, e-commerce, blogs, etc.

· See Web 2.0 – The Interactive Web from Week 4.

·

Open Source

Does the proposed project involve using new open source software? If it does, include the relative supporting information.

· See Open Source from Week 2.

· See Software & Hardware Review from Week 2.

Business Process MANAGEMENT

Does the proposed project involve a change to or implement a new business process? If it does, include the relative supporting information. (If appropriate process diagrams should be included. One diagram should show the current process and the second diagram should show the proposed process.)

· See Business Process from Week 2.

· See IS for Competitive Advantage from Week 2.

· See Process Improvement from Week 4.

Business Intelligence

Does the proposed project involve a change to or an implementation of Business Intelligence? If it does, include the relative supporting information.

· See Business Intelligence from Week 5.

Cloud

Does the proposed project involve a move to the cloud for data, software or hardware? If it does, include the supporting information.

· See Cloud from Week 3.

Managing IS

IS Components

Notes about the IS and IS Components. If additions, deletions and/or modifications are required by the proposal, those should be explained in the text here as well as clearly identified in the chart below.

Hardware	Software	Data	Procedures	People
· Item · Item · Item · …	· Item · Item · Item · …	· Item · Item · Item · …	· Item · Item · …	· Person · Person · Person · …

Explain any IS Component that needs further explanation. This might include a diagram of the data.

· See IS Components (Finalized) from Week 6.

· See Data from Week 3.

Data Changes Required

If data changes are required as part of this proposal they should be fully explored and justified here.

Software and/or Hardware Changes Required

Does the proposed project involve a change or require new hardware or software? If it does, include the relative supporting information.

· See Software & Hardware Review from Week 2.

· See Cloud from Week 3.

IS Department

Include the relative supporting information.

· See IS Department from Week 6.

IS in the Business Organization

If a change in how the IS Department fits into the overall business organization is part of this proposal it should be fully explored and justified here.

Management Challenges

If there are any management challenges that need to be explored do so here.

· See IS Department from Week 5.

· Also think about how the proposed changes may create new management challenges.

Custom Software Development

If the proposal requires custom developed software to be created or modified address how the development process will be addressed.

Primary Resource

Who will be your primary go-to person or group of people for this custom development? Justify your selection.

Greatest Feasibility Challenge

Explore the greatest feasibility challenge to the proposed development of custom software.

· See Managing IS from Week 5 for all items in this section.

Security

How is security currently handled for IS within the organization? Does the proposed project involve a change that requires more security or that adds risks? If it does, include the relative supporting information.

· See Security from Week 6.

IS Disaster Preparedness

How is IS disaster preparedness currently addressed within the organization? Does the proposed project involve a change that requires changes to this plan? If it does, include the relative supporting information.

· See Security from Week 6.

· See Mid-Term Exam from Week 4.

Outsourcing

Is outsourcing recommended? Why or why not.

· See IT Department from Week 6.

Managing in a Global Context

Address the benefits and risks of managing IT in a global context. Take into consideration the way the business operates now and how it will operate after the proposed change is implemented.

· See Managing IS from Week 5.

Project Feasibility

· See Feasibility from Week 5.

Economic (Is it affordable? Is it worth it?)

The best way to support this is with a list of tangible and in-tangible benefits, net present value analysis, a return on investment calculation and a break-even analysis.

Technical (Is it possible?)

As long as there are no barriers preventing the project from being successfully implemented then it should be technically possible. Issues that might arise include technology that is not mature enough and/or no people with the skills needed for implementation available.

Operational (Is it possible?)

Will the project face so much resistance to change that it will fail?

Schedule (Can it be done in time?)

Is there enough time to complete the project in a manner such that the value of the project still exists when it is completed? Will the project be completed before the system it is to replace fails or becomes obsolete?

Legal (Are there any legal obstacles?)

What, if any legal issues are there with moving forward with the project?

Political (Is someone going to get in the way?)

If there are concerns that someone is going to get in the way that should be addressed here. Speculate on motivations and suggest how to gain their buy-in should the project move forward.

 

Summary

Re-state the case for the proposal. Address benefits and risks here. The summary should be no more than ½ of the page single spaced.

(Median design)

Page 2

Page 1

MGMT-220 Justifications

This report was prepared as a part of a college course. This page is required for the final assignment. However, should students push forward their proposals this section should be removed. Additionally, the proposal should be edited and heading titles re-considered so that the report is completely oriented to the business setting.

Students were tasked with reviewing all the course information and selecting the ONE change they wanted to see pushed forward based on the coursework for this course. Because of this, many sections of areas studied may not be appropriate for the final project draft. Students are to complete the following chart to indicate what materials were removed from the outline and very brief explanation of why or how that section did not apply to the final proposal. For items that were included in the final proposal it is sufficient to state that it was included because it supported the final proposal.

MGMT-220 MIS Areas of Study

Area of Study	Included?	Justification of Inclusion/Exclusion.
Competitive Strategy	Yes	-- Mandatory --
Competitive Strategy Identified	Yes	-- Mandatory --
IS for Competitive Advantage
Collaboration
Data Silos
Web 2.0 – The Interactive Web
Open Source
Business Process
Business Intelligence (BI)
Cloud
Managing IS	Yes	-- Mandatory --
IS Components	Yes	-- Mandatory --
Data Changes Required
Software & Hardware Changes Required
IS Department	Yes	-- Mandatory --
IS in the Business Organization
Management Challenges
Custom Software Development
Security	Yes	-- Mandatory --
IS Disaster Preparedness	Yes	-- Mandatory --
Outsourcing	Yes	-- Mandatory --
Managing IS in a Global Context	Yes	-- Mandatory --
Project Feasibility	Yes	-- Mandatory --