professional documents
home
Profile
docsters
request
Blogs
Upload
about me
contact me
user photo
submit clear
Word Document

Business Case Template 4 center doc

State of Minnesota Information Technology Business Case 01/28/2008 Page 1 Business Case Template Feb 2006 Office of Enterprise Technology I. Project Identification 1. Agency 2. Project Name 3. Submittal Date Name Phone # E-mail Address 4. Project Sponsor (optional) 5. Project Manager (optional) 6. Business Need or Opportunity to be addressed by the project State of Minnesota Information Technology Business Case 01/28/2008 Page 2 Business Case Template Feb 2006 Office of Enterprise Technology II. Project Definition 1a. Business Objectives The project’s purpose; expected end results; in business terms, independent of solution 1b. Agency: Intentions, Values, or Services Impacted by this Project From the agency’s business strategy (optional) 2. Project Values Beliefs, guidelines, and anticipated tradeoffs for the project 3. Focus Boundaries of the project Breadth: Depth: Other: 4. Context Other factors that may affect project success Assumptions: Constraints: Definitions: Issues: Risks: Other: 5. Partners Other agencies participating in this project State of Minnesota Information Technology Business Case 01/28/2008 Page 3 Business Case Template Feb 2006 Office of Enterprise Technology III. Proposed Solution and Desirability 1. General Description of Proposed Solution 2. Benefits How the solution will improve the business Improved Service: Reduced cost: 3. Feasibility Positive or negative factors that could affect the project’s success, from project start until the solution is in place Explanation: Rating: 1 [ ] 2 [ ] 3 [ ] 4 [ ] 5 [ ] High Risk Low Risk 4. Sustainability Positive or negative factors that could affect the project’s success once the solution is in place; achieving the business benefits of the solution over time Explanation: Rating: 1 [ ] 2 [ ] 3 [ ] 4 [ ] 5 [ ] High Risk Low Risk 5. Alternate solutions considered, with assessment Other solutions to be considered or already ruled out. Including why solutions ruled out were eliminated. State of Minnesota Information Technology Business Case 01/28/2008 Page 4 Business Case Template Feb 2006 Office of Enterprise Technology IV. Return on Investment ($000) 2006-07 Biennium 2008-09 Biennium 2010-11 Biennium 1. Expenditures* FY 2006 FY 2007 FY 2008 FY 2009 FY 2010 FY 2011 Add Lines as Necessary Total: 2006-07 Biennium 2008-09 Biennium 2010-11 Biennium 2. Cost Savings* FY 2006 FY 2007 FY 2008 FY 2009 FY 2010 FY 2011 Total: 2006-07 Biennium 2008-09 Biennium 2010-11 Biennium 3. Other Tangible Benefits* FY 2006 FY 2007 FY 2008 FY 2009 FY 2010 FY 2011 Total: 2006-07 Biennium 2008-09 Biennium 2010-11 Biennium 4. Net Financial Impact FY 2006 FY 2007 FY 2008 FY 2009 FY 2010 FY 2011 Total: 5. Intangible Benefits Description *ROI Elements Description of Expenditures, Cost Savings and Intangible Benefits State of Minnesota Information Technology Business Case 01/28/2008 Page 5 Business Case Template Feb 2006 Office of Enterprise Technology V. Project Funding 1. Funding Distribution ($000) 2006-07 Biennium 2008-09 Biennium 2010-11 Biennium FY 2006 FY 2007 FY 2008 FY 2009 FY 2010 FY 2011 Comments Facilities Grants Hardware Personnel Services Software Supplies Training Total 2. Confidence Comments on costs; factors that would indicate cost estimates are stable, or could change. Estimates are accurate within: 10% [ ] 25% [ ] 50% [ ] 75% [ ] 100% [ ] Explanation: 3. Other costs Comments on other costs, e.g. staff time, or costs incurred by other organizations 4. Funding Source ($000) 2006-07 Biennium 2008-09 Biennium 2010-11 Biennium FY 2006 FY 2007 FY 2008 FY 2009 FY 2010 FY 2011 Comments General Special revenue Federal Trunk highway TEF Internal Other Total State of Minnesota Information Technology Business Case 01/28/2008 Page 6 Business Case Template Feb 2006 Office of Enterprise Technology VI. Architecture Fit Architecture fit How this solution is consistent or not consistent with the State technical architecture (www.ot.state.mn.us/architecture) Aligned Not aligned Not applicable a. Network b. Platform and Storage c. Data & Records Management d. Data Interchange e. Application f. Middleware g. Presentation & Accessibility h. Collaboration & Workflow i. Security & Authentication j. System Management & Reliability Explanation: Technology Use Major technology planned for this project [ ] Web [ ] Database [ ] GIS [ ] Imaging [ ] Workflow [ ] Other [ ] [ ] [ ] State of Minnesota Information Technology Business Case 01/28/2008 Page 7 Business Case Template Feb 2006 Office of Enterprise Technology VII. Project Characteristics 1a. Project Categories Enter an X for all that apply. [ ] EGS: Static information [ ] Business reengineering [ ] Small agency initiative [ ] EGS: Interactive response [ ] Agency collaboration [ ] CriMNet [ ] EGS: Financial transactions [ ] Mandate [ ] Other: specify { ] 1b. Business Functions Addressed [ ] License, permit, certify [ ] Provide information [ ] Provide oversight [ ] Collect revenue and fees [ ] Inspect [ ] Research, plan [ ] Provide services [ ] Enforce [ ] Other: specify [ ] 1c. Government Intentions Addressed [ ] Public safety [ ] Natural resources [ ] Community [ ] Public health [ ] Environment [ ] Security [ ] Education [ ] Transportation [ ] Drive to Excellence [ ] Economic well-being [ ] Law and justice [ ] Other: specify [ ] 2. Type of Development [ ] New [ ] Enhancement [ ] Maintenance/Continuation [ ] Other: specify [ ] 3. Breadth of Business Reengineering Who is affected by business process changes [ ] No change to business processes [ ] Single department within an agency [ ] Multiple departments within an agency [ ] Across multiple governmental organizations 4. Depth of Business Reengineering How much business processes will change [ ] No change to business processes [ ] Includes some changes to business processes [ ] Includes major restructuring of business processes 5. Description of Business Reengineering State of Minnesota Information Technology Business Case 01/28/2008 Page 8 Business Case Template Feb 2006 Office of Enterprise Technology 6. Technology Major technologies expected to be used in this project a. Network [ ] Microsoft [ ] Novell [ ] Unix Based b. Enterprise Database [ ] Oracle [ ] MS SQL [ ] Sybase [ ] IBM DB2 c. Desktop Database [ ] MS Access [ ] Dbase [ ] Lotus Approach d. Desktop Suite [ ] MS Office [ ] Corel Office [ ] Lotus SmartSuite [ ] WordPerfect Office Suite e. Web Server [ ] Microsoft IIS [ ] Netscape [ ] Apache f. Web Hosting [ ] InterTech [ ] Agency [ ] Other g. Web Applications Platform [ ] IBM Websphere [ ] BEA Weblogic [ ] iPlanet [ ] Broadvision h. Host Platform [ ] Microsoft/Intel [ ] Unix based [ ] IBM midrange [ ] IBM mainframe i. Development Language [ ] C or C++ [ ] Java [ ] Visual Basic [ ] Cobol [ ] Fortran [ ] Smalltalk [ ] Ada 7. Other Major Technologies expected to be used in this project # Technology Product or Vendor 1. 2. 3. 4. 5. 6. 7.
rate this doc
email this doc
embed this doc
add to folder
digg reddit stumble delicious
flag this doc
161
15
not rated
0
1/28/2008
English
search termpage on Googletimes searched
Preview

Project Business Case Template[1]

ocak 1/28/2008 | 203 | 36 | 0 | business
Preview

Business Case Template[3]

ocak 1/28/2008 | 93 | 11 | 0 | business
Preview

business case template

ocak 1/28/2008 | 108 | 8 | 0 | business
Preview

Project Business Case Template

banter 1/8/2008 | 657 | 120 | 0 | business
Preview

Project Charter Template 4

ocak 1/28/2008 | 740 | 117 | 0 | business
Preview

Project Plan Template[4]

ocak 1/28/2008 | 207 | 29 | 0 | business
Preview

Project Initiation Document Template

ocak 1/28/2008 | 999 | 316 | 0 | business
Preview

Project Proposal Document Template

ocak 1/28/2008 | 2389 | 479 | 0 | business
Preview

Use Case Template[1]

ocak 1/28/2008 | 159 | 40 | 0 | business
Preview

Use Case Specification and Template

ocak 1/28/2008 | 362 | 75 | 0 | business
Preview

Project Management Template Examples

ocak 1/28/2008 | 1899 | 430 | 0 | business
Preview

Project Defects Register Document Template

ocak 1/28/2008 | 384 | 32 | 0 | business
Preview

Business Case Guide

ocak 1/28/2008 | 114 | 10 | 0 | business
Preview

Business Case Guidelines

ocak 1/28/2008 | 116 | 7 | 0 | business
Preview

Document Management Plan Template[1]

ocak 1/28/2008 | 415 | 92 | 0 | business
Preview

Template Project Scale[1]

ocak 1/28/2008 | 1173 | 1501 | 2 | business
Preview

Strategic Asset Plans[1]

ocak 1/28/2008 | 703 | 247 | 2 | business
Preview

Steering Committee Charter template[1]

ocak 1/28/2008 | 1351 | 302 | 3 | business
Preview

Status Report Management Process Flow example[1]

ocak 1/28/2008 | 1495 | 488 | 1 | business
Preview

Status Report example[1]

ocak 1/28/2008 | 1645 | 645 | 2 | business
Preview

Software Requirement Specifications Document Template[1]

ocak 1/28/2008 | 1218 | 244 | 1 | business
Preview

Scope Statement Development Instructions[1]

ocak 1/28/2008 | 504 | 32 | 0 | business
Preview

Schedule Of Excess Risks[1]

ocak 1/28/2008 | 258 | 18 | 0 | business
Preview

Sample Performance Based Requirement Template for use with Task Orders[1]

ocak 1/28/2008 | 371 | 21 | 0 | business
Preview

Risk Value Assessment Tool

ocak 1/28/2008 | 428 | 54 | 1 | business
 
review this doc