http://unpan1.un.org/intradoc/groups/public/documents/NISPAcee/UNPAN015482.pdf

~~~~~~~~~~~~~~~

http://www.ub.rug.nl/eldoc/dis/management/a.w.v.breukel/summary.pdf http://www.ub.rug.nl/eldoc/dis/management/a.w.v.breukel Strategic IT, but not by ITself? [Online Resource]? : on the relevance of the organizational context for strategic success with IT / Adriaan Willem Vincent Breukel. - Capelle a/d IJssel? : Labyrint ; [Groningen]? : [University Library Groningen]? [Host]?, 1996.

~~~~~~~~~~~~~~~~~~

Strategic information systems planning: the IT strategy implementation matrix Author: Gottschalk P.1 Source: European Journal of Information Systems, 1 June 1999, vol. 8, no. 2, pp. 107-118(12) Publisher: Palgrave Macmillan < previous article | next article > View Table of Contents

full text options

Abstract: The need for improved implementation of information technology (IT) strategy has been emphasised in both empirical and prescriptive research studies. In this study, ten content characteristics of formal information technology strategy are identified from the research literature as potential implementation predictors. These are descriptions of: (i) resources needed for the implementation; (ii) user involvement during the implementation; (iii) analyses of the organization; (iv) anticipated changes in the environment; (v) solutions to potential resistance during the implementation; (vi) information technology to be implemented; (vii) projects’ relevance to the business plan; (viii) responsibility for the implementation; (ix) management support for the implementation; and (x) clarity of the documentation. An IT strategy implementation matrix is introduced to illustrate the relationship between the expired time horizon and the IT strategy implementation extent. The matrix can be used by organizations to monitor their IT strategy implementation performance over time. A survey was conducted in Norway whereupon the return of 471 completed questionnaires resulted in a satisfactory response rate of 43%. Formal IT strategy was reported in 40% of these organizations. The two significant predictors in the testing of hypotheses proved to be the description of responsibility for the implementation and the description of user involvement during the implementation.

From http://www.maxwell.syr.edu/gpp/pdfs/Strategic_Info_Systems.pdf Question 10: Please answer the following questions about information technology planning: a. Does your state have a statewide information technology strategic plan? If yes: How many years does it cover? (fill in blank) When was it last formally revised? (fill in blank, MM/YY) How frequently is the plan reviewed? (multiple choice: 6 months to 10 years) Which of the following components does it include? (Check all that apply.) • A vision statement • A mission statement • Specific core values • Specific long-term goals (beyond 1 year) • Specific short-term objectives (1 year or less) • Specific performance measures for each goal • Specific performance measures for each objective • Specific benchmarks for each goal • Specific benchmarks for each objective • Clear assignment of responsibility for achievement of each objective • Discussion of action plans designed to achieve each objective • Discussion of key external factors that may affect achievement of each objective • Discussion of resources required to achieve each objective • Discussion of how input from external stakeholders was included in the plan • Other components (Please specify.) b. Is there an information technology component to your state’s overall strategic plan? (No, Yes, or In progress) c. What proportion of individual state agencies have information technology strategic plans in place? (All, Most, About half, Less than half, None) d. If individual state agencies have overall strategic plans, is there an information technology component to them? (No, Yes, In progress) e. Please describe the information technology planning process in your state. (Openended request.) f. Please explain how feedback from front-line managers and end-users is incorporated into information technology plans. (Open-ended request.)

http://www.comp.glam.ac.uk/pages/staff/tdhutchings/chapter1.html

Strategic information systems planning

http://bizplan.com/sisplanning/

http://www.cse.dmu.ac.uk/~nkm/sisp/SISP1.html

From: http://www.defenselink.mil/nii/bpr/bprcd/policy/fr_apxh.html

H. Methodology Work Breakdown Structure PHASE 1: STRATEGIC AND BUSINESS PLANNING

Step 1: Develop/Validate the Strategic Plan T 1: Develop/validate the organizational articles of faith T 2: Identify major customer groupings and general customer requirements T 3: Conduct strategic benchmarking to establish performance targets T 4: Conduct SWOT analysis T 5: Identify core competencies T 6: Determine high-level customer service requirements T 7: Prepare breakthrough objectives T 8: Identify performance measures T 9: Document the strategic plan T 10: Review and approve the strategic plan.

Step 2: Develop/Validate the Business Systems Plan T 11: Review/validate the current business systems planning architectures T 12: Identify major business processes T 13: Develop the business process/organizational map T 14: Prepare/validate information systems architectures T 15: Review and approve the business systems plan.

Step 3: Develop/Validate the Business Plan T 16: Review strategic and business systems planning materials T 17: Develop preliminary process notebook T 18: Conduct detailed customer requirements analysis T 19: Categorize process improvement projects T 20: Develop the business plan report T 21: Review and approve business plans.

Step 4: Construct Performance Cells T 22: Select performance cell by process T 23: Assign responsibility for performance cell development T 24: Develop performance cells T 25: Review and approve the performance cell document.

Step 5: Establish Process Improvement Project T 26: Specify process improvement project T 27: Select and confirm a process manager and project manager T 28: Develop and/or validate the process deployment map T 29: Record functional management considerations T 30: Document the scope/mission/objectives of functional elements T 31: Select and train the cross-functional process improvement team T 32: Develop a preliminary process vision T 33: Develop the process improvement strategy T 34: Develop the project plan T 35: Review and approve the project plan. PHASE 2A: BUSINESS PROCESS REENGINEERING

Step 6: Conduct Baseline Analysis T 1: Develop or confirm the project scope T 2: Develop or review and revise AS-IS Activity Models T 3: Develop or review and revise AS-IS Data Models T 4: Perform activity based costing T 5: Perform time-line analysis (simulation) T 6: Document the baseline condition T 7: Revise performance cell descriptions T 8: Review and approve baseline documentation.

Step 7: Conduct Improvement Analysis T 9: Review process vision, objectives, and measures T 10: Conduct stakeholder requirements gap analysis T 11: Conduct best practices benchmarking analysis T 12: Select data gathering and analysis techniques T 13: Identify and document performance gaps in product quality T 14: Identity and document performance gaps in process cycle time T 15: Identify and document performance gaps in process cost T 16: Identify and document process-related issues T 17: Identity and document organizational issues T 18: Identify and document technology issues T 19: Develop process improvement opportunities T 20: Prepare process improvement analysis report T 21: Review and approve process improvement analysis report.

Step 8: Redesign/Reengineer Processes T 22: Review process improvement analysis report T 23: Refine process vision statement T 24: Develop initiatives for process improvement T 25: Redesign/redevelop business processes T 26: Refine/redevelop process deployment map T 27: Describe and quantify new stakeholder relationships T 28: Revise future state performance cell descriptions T 29: Validate initiatives and models against requirements T 30: Select alternatives for process improvement actions T 31: Perform economic analysis on alternatives T 32: Develop detailed TO-BE activity and data models T 33: Initiate/coordinate data administration activities T 34: Initiate/coordinate information systems activities T 35: Prepare final process design specifications T 36: Review and approve process design specifications.

Step 9: Prepare Functional Economic Analysis Decision Package T 37: Review process improvement recommendations T 38: Review organizational change management plan (from Section 6.3.5) T 39: Review technology change management plan (from Section 7.3.6) T 40: Develop preliminary Functional Economic Analysis (FEA) T 41: Develop preliminary data and technical management plan T 42: Perform technical review of FEA documents T 43: Validate/revise preliminary FEA report T 44: Prepare final Functional Economic Analysis report T 45: Review and approve FEA PHASE 2B: ORGANIZATIONAL CHANGE MANAGEMENT

Step 10: Assess Organizational Capability T 1: Review process improvement organizational implications T 2: Assess organizational status (strengths and weaknesses) T 3: Document current organizational status T 4: Review and approve organizational situation report.

Step 11: Identify Organizational Change Requirements T 5: Review and evaluate process improvement analysis report T 6: Document organizational best practices T 7: Evaluate organizational change requirements T 8: Develop time and cost estimates T 9: Develop organizational impact statement T 10: Review and approve organizational impact statement.

Step 12: Develop Organizational Change Management Plan T 11: Analyze organizational barriers to change T 12: Prepare strategies for overcoming barriers T 13: Identify process-related training requirements T 14: Develop organizational change management plan T 15: Review and approve organizational change management plan. PHASE 2C: TECHNOLOGY CHANGE MANAGEMENT

Step 13: Assess Technical Capability T 1: Review Process Improvement Plan Technical Implications T 2: Assess Current Technical Status (Strengths/Weaknesses) T 3: Assess Emerging Technologies v Process Requirements T 4: Document Technical Status T 5: Review and Approve Status Report.

Step 14: Identify Technical Change Requirements T 6: Review Process Improvement Recommendations T 7: Identify Technology Best Practices T 8: Evaluate Technical Change Requirements T 9 Develop Time and Cost Estimates T 10: Perform Technical Impact Statement T 11: Review and Approve Technical Impact Statement.

Step 15: Develop Technical Change Management Plan T 12: Design High-level Technical Models T 13: Identify Barriers to and Implications of Change T 14: Develop Strategies for Addressing Barriers T 15: Identify Technology-related Training Requirements T 16: Develop Technology Change Management Plan T 17: Review and Approve Technology Change Management Plan. PHASE 3: ENTERPRISE ENGINEERING

Step 16: Configure Technical Platform T 1: Review Approved FEA Package and Supporting Documents T 2: Review Technical Change Management Plan T 3: Assess Current Status and Capabilities T 4: Design Hardware Systems Support Requirements T 5: Design Communications Support Requirements T 6: Design Network Support Requirements T 7: Design Systems Software Requirements T 8: Document Technical Platform Requirements T 9: Review and Approve Platform Requirements.

Step 17: Develop Application Systems T 10: Review Approved FEA and Supporting Documentation T 11: Review Technical Change Management Plan T 12: Assess Current Capabilities T 13: Design Application Support Systems T 14: Develop Application Support Systems T 15: Unit-test Application Support Systems with Data Base T 16: Document Application Support Systems T 17: Review and Approve Application Systems.

Step 18: Develop Data Base Structures T 18: Review Approved FEA and Supporting Documentation T 19: Review Technical Change Management Plan T 20: Assess Current Capabilities T 21: Perform Data Base Administration Activities T 22: Design Data Base Structures T 23: Unit-test Data Base Structures with Application Software T 24: Document Data Base Structures T 25: Review and Approve Data Base Structures.

Step 19: Construct Information Systems T 26: Prepare Test/Pilot Site for Systems Assembly T 27: Load Test Files and Data Bases T 28: Assemble and Test Application Systems T 29: Develop Draft Information System Manuals T 30: Conduct Initial Training T 31: Conduct Acceptance Trials T 32: Develop Data Acquisition Plan T 33: Review/Revise Organizational Change Management Plan T 34: Develop Final Documentation Package T 35: Acquire/Develop Functional/Technical Training Systems T 36: Conduct Systems Audit and Acceptance Tests.

Step 20: Design Systems Integration Plan T 37: Design Platform Integration Plan T 38: Design Data Base Integration Plan T 39: Design Application Systems Integration Plan T 40: Review Information Systems for Conformity with DoD? Enterprise Model T 41: Identify and Resolve Cross-Functional Process Issues T 42: Identify and Resolve Interoperability Issues and Concerns T 43: Develop Revised (TO-BE) Architectures T 44: Update Defense Data Repository System T 45: Develop Transition/Migration Plan T 46: Conduct Pre-installation and Deployment Conference. PHASE 4: PROJECT EXECUTION

Step 21: Develop Installation/Deployment Project Management Plan T 1: Review Approved Project-related Documents T 2: Construct Project Management Plan T 3: Secure Review/Approval of Project Management Plan T 4: Execute Project Management Plan.

Step 22: Install/Deploy Information Systems T 5: Select Initial Installation Site T 6: Install and Test Information Systems T 7: Implement Training Programs T 8: Conduct Parallel Test Program T 9: Secure Customer Acceptance T 10: Implement Transition (Cut-over) Plan T 11: Deploy Remaining Sites T 12: De-commission Obsolete Information Systems T 13: Conclude Information Systems Deployment Phase.

Step 23: Deploy Organization Change Management Plan T 14: Issue Policy and Guidance T 15: Implement Transition Plan T 16: Deploy Implementation Plan T 17: Complete Organizational Realignment T 18: Changeover to New Process and Information Systems T 19: Monitor Change Process T 20: Adjust Program as Required T 21: Prepare Final Implementation Report T 22: Conclude Installation/Deployment Program.

Step 24: Operate/Maintain Process and Information Systems T 23: Operate Process and Information Systems T 24: Monitor Performance T 25: Identity/Classify/Resolve Problems and Issues T 26: Maintain Process and System Documentation T 27: Conduct Continuous Training and Support Program T 28: Prepare Regular Operating Status Reports.

Step 25: Conduct Continuous Process Improvement Program T 29: Review Performance/Status/Problem Reports T 30: Conduct Surveys/Interviews/Questionnaires/Focus Groups T 31: Monitor Stakeholder Feedback T 32: Identify Incremental Improvement Opportunities T 33: Design Incremental Change Specifications T 34: Implement Incremental Change Program T 35: Prepare Regular Improvement Status Reports.

And: Data Modeling Review project mission.

• Review project plan / resource assignments.
• Identify and understand the reason for (use) the data model.
• Detail the end-result (products) of the task.
• Obtain dates and location of sessions from sponsor.
• Select core team members and assign roles.(Appendix A)
• Resource requirements. (travel funds, facilities, location, dates, etc..)
• Obtain equipment and software. (PC's, Laptops, etc..)

Analyze Current Status: Mission Statement Past and Present Strategies (and Objectives) Past and Present Performance Examine Prospects for the Future: Environmental Analysis (usually dictates Opportunities and Threats) Industrial (five forces) Stakeholders Internal Analysis (usually dictates Strengths and Weaknesses) Functional Areas Leadership, Culture, Organizational Structure, Processes, Staff Resources, Organizational Climate, Communications, etc. Develop SWOT (Strengths, Weaknesses, Opportunities, and Threats) Analysis Clearly Define the Major Corporate Problem(s)/Opportunities Set the Future Course: Develop a List of 3-5 Feasible Alternatives (For Group Project, These Should Be Strategic Shifts) Compare Alternatives against Corporate Objectives Select One Alternative (Or Combinations of Alternatives) and a Contingency (For Group Project this is your strategic shift) Put the Strategy to Work: Develop Implementation Plans for Each Functional Area Affected Develop Implementation Plans for Other Organizational Attributes Evaluate and Control: Develop a Plan for Controlling/Measuring Success (Meeting Objectives)

Standard SWOT STRATEGIC BUSINESS PLAN OUTLINE

EXECUTIVE SUMMARY (a concise 1-2 page overview)

THE COMPANY: A. Mission Statement B. Corporate Culture (Guiding Principles) C. Historical Direction & Results D. Management

SITUATIONAL (SWOT) ANALYSIS: A. Strengths B. Weaknesses C. Opportunities D. Threats

MARKET RESEARCH: (Competition & Clients) A. Tax Preparation B. Tax School C. Accounting D. Other

MARKETING GOALS (must be measurable): A. Consumer Awareness B. Market Share C. Diversification D. Channels of distribution (for your services & products) E. Other

SERVICE (PRODUCT) DEVELOPMENT: A. Trade Names B. Descriptions of Services & Products to be Offered C. Pricing D. Delivery Systems: Policy & procedure manuals; Software (tax preparation, accounting); Networks; Information Systems & Technology E. Delivery Capability: Personnel; Facilities (offices, processing dept.); Equipment (computers, furnishings, fixtures, signs) F. Suppliers of Critical Elements (supply vendors, software & system licensors, service suppliers, government agencies e.g.: IRS)

MARKETING PLAN: A. Strategies & Tactics B. Client Segmentation C. Positioning D. Advertising E. Public Relations F. Cross-Selling to Clients G Test Marketing H. Other

FINANCIAL PLAN: A. Revenue Sources: Capital Requirements; Sources of Funds B. Financial Assumptions: Revenue; Expenses C. Proforma Financial Statements D. Financial Controls: Cash Flow Budget (monthly); Financial Statement Analysis (critical ratios); Budget Variance Analysis; Financial Reviews and Audits

RISK FACTORS (see SWOT analysis) & CONTINGENCIES: A. Revenue Shortfall B. Negative Legislation (e.g.: flat tax) C. Economic Recession D. Competition E. Technology F. Adverse Publicity

ASSESSMENT AND REVIEW: A. Tracking Systems B. Break-even Analysis of Each Campaign C. Client Satisfaction Survey D. Associate Input (Advisory Board) E. Market Share Analysis F. Market Survey (Aided Awareness, Taxpayer Perceptions)

APPENDICES: A. Market Research Study - Clients B. Market Research Study - Competition C. Market Research Study - Environment D. Key Sources of Information

-----------------------

Section No. Section Title 1 PURPOSE (rationale for the policy) 2 DEFINITIONS (defining the meaning of words and/or terms utilized within the context of the policy and/or procedures.) If no definitions are needed, Policy/Procedures will become Section 2. 3 POLICY/PROCEDURES (operating details 4 REVIEW AND RESPONSIBILITIES 2.1.2 The first section of each PS should provide a rationale for the policy or procedure outlined in the PS. The rationale may be a reference to a legal requirement, a statement of the goals which the PS is attempting to facilitate, or some other description of the reasons for the implementation of this policy or procedure. 2.1.3 The operating details of the PS should explain the WHAT, HOW, WHO, and WHEN of the subject of the PS.

Things Privacy Opportunities like blogs http://www.onphilanthropy.com/bestpract/bp2005-04-08.html http://gristmill.grist.org/

What about other web uses? How about an intranet? Portal? Where does the data go? Review and revision, lifecycle

GVHF Purpose Tools Keywords: Policy, procedures, Columbia University maintains certain policies with regard to the use and security of its computer systems, networks and information resources. All users of these facilities are expected to be familiar with these policies and the consequences of violation.

Computer and Acceptable Use Policy The University's underlying computing and network policy. The links below expand on particular facets of policy.

Personal Responsibility You are personally responsible for what you do on the network as a member of the Columbia community—from respecting copyright to securing your computer against viruses and worms.

Copyright Policy You must respect copyright. Copyright protection covers any original work of authorship. Even ordinary e-mail messages, in fact, just about any work you come across online is likely to be protected by copyright.

Network Bandwidth Quotas are imposed on network use to ensure proper functioning of the network for the entire University community.

Domain Names The policy and procedure governing the creation of domain names for Columbia University entities and affiliates.

Mass E-mail Procedures Policy and procedures for using University broadcast e-mail lists obtaining permission to send e-mail messages to persons in in more than one school or administrative unit.

Authentication Policy Creation of any program, Web form, or other mechanism that asks for a Columbia user identity and password, e.g. UNI, CUNIX ID, is prohibited except by using the methods documented here.

Information Security Any person or organization using or providing information resources has a responsibility to maintain and safeguard these assets.