• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content


Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

ITSM Overview Presentation






Total Views
Views on SlideShare
Embed Views



1 Embed 1

http://www.slideshare.net 1



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

    ITSM Overview Presentation ITSM Overview Presentation Presentation Transcript

    • IT Service Management Academy Session 1 March 6, 2006; 8:30 a.m. – noon Melody Riley & Janet Gerling
    • Agenda
      • Welcome & Introductions
      • Academy Overview
      • Academy Framework & Tools
      • Academy Charter Development
      • Session Wrap-up
    • Welcome & Introductions
      • Name
      • Agency
      • Role in Agency
      • Expectations
    • Background
      • ITAM Project & IT Asset Mgmt. Policy
      • ITSM IRR
      • RFP Status
      • Scope of Work
    • Academy Overview
      • Purpose
      • Academy Approach
        • Project-based learning environment
        • Very participative/group activity
        • Focus on industry best practices
        • Homework
      • Outcomes
    • Academy Framework & Tools
      • Dynamic Systems Development Methodology (DSDM)
      • Project Management
      • Remedy ITSM Suite
      • ITSM Academy Repository
      • IT Infrastructure Library (ITIL)
    • DSDM
      • Iterative Process
      • Joint Application Design
      • Timeboxing and Priortization-MoSCoW Rules
    • DSDM-MoSCoW Rules
      • Must have
      • Should have
      • Could have
      • Want to have but Won’t have this time around
    • System Development Methodology
      • A Systems Development Methodology defines the manner in which an IT system will be built. A methodology prescribes a set of processes, deliverables, and decisions that need to be made at various points in the system development. Two major methodologies exist:
        • Waterfall Methodology
        • Spiral Methodology
    • Waterfall
    • DSDM
    • Key Differences Functionality Functionality Resources Time Resources Time DSDM Waterfall Fixed Variable
    • Benefits of DSDM
      • Users are more likely to take ownership
      • Risk of building the “wrong” system is greatly reduced
      • System is more likely to meet the “real” requirements
      • Users will be better trained
      • Implementation is more likely to go smoothly
    • Phases in DSDM
      • Feasibility Study
      • Business Study
      • Functional Model Iteration
      • Design & Build Iteration
      • Implementation
      • Notice: No Maintenance or Testing phase!
    • Feasibility Phase
      • Check for feasibility of project based on budget and human resources.
      • Establish and follow a portfolio management methodology
      • Ensure that there is agreement on and suitability for DSDM (or whatever methodology is to be followed)
    • Business Study Phase
      • High Level Scope
      • High Level requirements are baselined
      • Agree on System Architecture
      • Define Objectives, Challenges, and Success Measures
    • Functional Model Iteration
      • Focus is on refining high level business and information requirements. Iteration consists of:
        • Identify what is to be produced
        • Agree how and when to do it
        • Create the product
        • Check that the product has been produced correctly
    • Design & Build Iteration
      • Focus is on ensuring that the system is of sufficiently high quality to be placed in the hands of the users.
      • End product is a completely tested system to which non-essential requirements can be added over time
    • Implementation
      • Transfer from operational to production environment. Four possible outcomes:
        • Everything was delivered; no further development
        • New functional area was discovered (back to business study phase)
        • Non-essential functionality was not delivered (back to functional model iteration)
        • Non-functional requirements was not delivered (back to design & build iteration)
    • Project Management
      • Charter
      • Schedule
      • Resources (Staff & Funding)
    • Remedy ITSM
      • Currently being used by 4 agencies
      • Met technical requirements in previous IT Asset Management procurements
      • Uses ITIL framework
    • ITSM Academy Repository
      • Online
      • Updated Weekly
      • All Agendas posted
      • All session outcomes posted
    • IT Infrastructure Library
    • Project Charter Development Group Exercise
    • Session Wrap-Up
      • Individual Brainstorm Worksheet
      • Next Session
        • Academy Kick-Off
        • Monday, March 13, 2006
        • 8:30 a.m. – noon
        • P&D Large Conference Rm.