Hendershott Consulting Inc

Slides:



Advertisements
Similar presentations
Roadmap for Sourcing Decision Review Board (DRB)
Advertisements

Requirements Specification and Management
1 Information Systems Development (ISD) Systems Development Life Cycle Overview of Analysis Phase Overview of Design Phase CP2236: Information Systems.
ITIL: Service Transition
Service Design / SLA Architecture “Services are a means of delivering value to customers by facilitating outcomes customers want to achieve without the.
Principles and Learning Objectives
The Transforming Power of the ITIL Framework for the Project Manager Patrick von Schlag Deep Creek Center November 10, 2010.
1 Samples The following slides are provided as samples and references for the Quarterly Reviews Additional slides will be added.
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
7.2 System Development Life Cycle (SDLC)
Adaptive Processes Comparing CMMI 1.2 vs. CMMI 1.1 LN Mishra Adaptive Processes Consulting.
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
Service Design / Figure 3.6 The Service Portfolio – a Central Repository.
The Agile vs. Waterfall Methodologies Systems Development:  the activity of creating new or modifying / enhancing existing business systems.  Objectives.
Introduction to Computer Technology
Release & Deployment ITIL Version 3
Developing Enterprise Architecture
Web Development Process Description
Foundation Degree IT Project Methodologies (for reference)
Chapter 15 Systems Development
Introduction to Software Quality Assurance (SQA)
Continual Service Improvement Process
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Unified Software Development Process (UP) Also known as software engineering process SEP describes how requirements are turned into software Defines who,
Software Project Management Introduction to Project Management.
LECTURE 1 What does a Business Analyst do? IFS 231 Business Analysis.
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Roles and Responsibilities
Topic (1)Software Engineering (601321)1 Introduction Complex and large SW. SW crises Expensive HW. Custom SW. Batch execution.
Continual Service Improvement & ITIL V3
Systems Development AIMS 2710 R. Nakatsu. Overview Why do IT projects succeed and fail? Two philosophies of systems development –Systems Development Life.
Service Transition & Planning Service Validation & Testing
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Chapter 10 Information Systems Analysis and Design
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
IT Requirements Management Balancing Needs and Expectations.
Rapid Application Development. What is RAD……..?  Rapid Application Development (RAD) is a software development process.  first developed during the.
Fundamentals of Information Systems, Third Edition1 Systems Design Answers the question “How will the information system do what it must do to solve a.
Lecture 7: Requirements Engineering
IS Methodologies. Systems Development Life Cycle - SDLC Planning Planning define the system to be developed define the system to be developed Set the.
Systems Analysis and Design
Foundations of Geospatial System Development II Todd S. Bacastow Professor of Practice for Geospatial Intelligence John A. Dutton e-Education Institute.
IS Analysis and Design. SDLC Systems Development Life Cycle Break problems into management review stages Control cost and time Works best with well understood.
Chapter 6: THE EIGHT STEP PROCESS FOCUS: This chapter provides a description of the application of customer-driven project management.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Anjanae Brueland & Janet Wingard.  What is Network Design, Planning & Management?  System Development Life Cycle (SDLC)  The phases of an information.
Systems Development AIMS 2710 R. Nakatsu. Overview Two philosophies of systems development –Systems Development Life Cycle (SDLC) –Prototyping Alternative.
Software Development Life Cycle (SDLC)
August, 2013 Accounting for Agile Projects Disclaimer: This document does not offer specific accounting advice, but represents a practical and viable Agile.
An organizational structure is a mostly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim... Organizational.
SE513 Software Quality Assurance Lecture10: Documentation and Quality Records Control Galin, SQA from Theory to Education Limited.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
Fundamentals of Information Systems, Third Edition2 Principles and Learning Objectives Effective systems development requires a team effort of stakeholders,
CMMI for Services, Version 1.3 Speaker: Business Excellence Date:
Process 4 Hours.
ITIL: Service Transition
Fundamentals of Information Systems, Sixth Edition
Systems Analysis and Design
Software Requirements
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Engineering Processes
Guidance notes for Project Manager
(System Development Life Cycle)
Engineering Processes
SDLC (Software Development Life Cycle)
System Analysis and Design:
Presentation transcript:

Hendershott Consulting Inc Aligning New Services Hendershott Consulting Inc web Presence: www.hci-itil.com Emil: len.hendershott@rogers.com Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services New services (or Service Improvement Projects – SIPs) are initiated using the organization’s project management methodology. Investigation Go Stop Verify that a problem, opportunity or deficiency exists to assess the business worth of an undertaking. Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Requirements Statement Service Requirements Scalability Business processes and business units supported IT service and the agreed business functionality and requirements Service itself and its SLRs or SLAs Technology components used to deploy and deliver the service Internally supported services and components and their associated OLAs Externally supported services and components and their associated Ucs Performance measurements and metrics required Legislated or required security levels. Investigation Analysis Service Design must consider all elements of the service when determining requirements. Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Business Requirements Business Requirements Business Requirements Business Requirements Project Methodology: SDLC, RUP, PRINCE2, Agile The critical foundation of any successful project implementation is a thorough requirements analysis. This provides the groundwork for a solution to meet targeted business objectives. CMMI provides guidance: CMMI: Requirements Development Stakeholder needs, expectations, constraints, and interfaces are collected and translated into customer requirements Customer requirements are refined and elaborated to develop product and product-component requirements. The requirements are analyzed and validated, and a definition of required functionality is developed. Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Business Requirements Business Requirements Business Requirements Business Requirements Project Methodology: SDLC, RUP, PRINCE2, Agile The critical foundation of any successful project implementation is a thorough requirements analysis. This provides the groundwork for a solution to meet targeted business objectives. CMMI provides guidance: CMMI: Requirements Management Develop an understanding with the requirements providers on the meaning of the requirements. Obtain commitment to the requirements from the project participants. Manage changes to the requirements as they evolve during the project. Maintain bidirectional traceability among the requirements and the project plans and work products. Identify inconsistencies between the project plans and work products and the requirements. Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Business Requirements Business Requirements Business Requirements Business Requirements Project Methodology: SDLC, RUP, PRINCE2, Agile A formal and structured approach is required to produce the new service at the right cost, functionality, quality and within the right time frame. CMMI: Technical Solution Product or product-component solutions are selected from alternative solutions. Product or product-component designs are developed. Product components, and associated support documentation, are implemented from their designs. Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Investigation Analysis Design All design activities are triggered by changes in business needs or service improvements. Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Investigation Analysis Design Develop The Development phase is often split into two sections, that of Prototyping and Production Readiness. Examination and re-examination of the Requirements Definition Statement is needed to ensure that it is being followed to the letter. Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Investigation Analysis Design Develop Implementation Any hardware that has been purchased will be delivered and installed. Software, which was designed in the System Design Phase, and programmed in System development phase of the SDLC, will be installed on any PCs that require it. Any person that will be using the program will also be trained during this phase of the SDLC. Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Investigation Analysis Design Develop Maintenance Implementation Deal with any changes that need to be made to the service. Changes are sometimes the result of the service not completely fulfilling its original requirements, but they could also be the result of customer satisfaction. Ensure that service fulfills the Requirements Statement. Service Design / Figure 3.5 Aligning new services to business requirements

Project {Project Team} Aligning New Services Business Requirements Project {Project Team} Project Methodology: SDLC, RUP, PRINCE2, Agile Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Pilot or warrant period Live Operations (Steady State) Project Methodology: SDLC, RUP, PRINCE2, Agile Project {Project Team} The ITIL service lifecycle aligns with project management methodologies. Requirements Statement Design Service Solution Develop Service Solution Build Service Solution Test Service Solution Improvement Strategy Design Transition Operation Transition & Operations Involvement in the Design Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Pilot or warrant period Live Operations (Steady State) Project Methodology: SDLC, RUP, PRINCE2, Agile Project {Project Team} SAC Requirements Statement Design Service Solution Develop Service Solution Build Service Solution Test Service Solution Improvement Strategy Design Transition Operation Transition & Operations Involvement in the Design Service Acceptance Criteria are reviewed and revised, if necessary, at each stage to ensure that an IT Service meets defined functionality and quality requirements and that the IT Service Provider is ready to operate the new IT Service when it has been deployed. Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services SDP Pilot or warrant period Live Operations (Steady State) Project Methodology: SDLC, RUP, PRINCE2, Agile Project {Project Team} The Service Design Package (SDP) describes everything necessary for the subsequent testing, introduction and operation of the solution or service. SAC Requirements Statement Design Service Solution Develop Service Solution Build Service Solution Test Service Solution Improvement SDP Strategy Design Transition Operation Transition & Operations Involvement in the Design Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Pilot or warrant period Live Operations (Steady State) Project Methodology: SDLC, RUP, PRINCE2, Agile Project {Project Team} At each stage of the project the Service Level Requirements are reviewed and revised, if necessary. The expected outcomes from the operation of the new or changed service in measurable terms, generally expressed within new or existing Service Level Agreements (SLAs). SAC Strategy Design Transition Operation Improvement Requirements Statement Design Service Solution Develop Service Build Service Test Service Transition & Operations Involvement in the Design SDP SLA Pilot SLA SLM SLR SLR SLR SLR SLR Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Pilot or warrant period Live Operations (Steady State) Project Methodology: SDLC, RUP, PRINCE2, Agile Project {Project Team} SAC Strategy Design Transition Operation Improvement Requirements Statement Design Service Solution Develop Service Build Service Test Service Transition & Operations Involvement in the Design SDP Release and Deployment Management builds, tests and delivers the solution or services specified by SDP according to SAC and using a Release Plan to schedule introduction to the live environment. SLM SLA Pilot SLR Build, Test, Release and Deployment Management Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Pilot or warrant period Live Operations (Steady State) Project Methodology: SDLC, RUP, PRINCE2, Agile Project {Project Team} SAC The new or revised service offering implies changes to the live environment which is under Change Control. Representation and approval by Change Management authorities is required throughout the Design and implementation processes. Strategy Design Transition Operation Improvement Requirements Statement Design Service Solution Develop Service Build Service Test Service Transition & Operations Involvement in the Design SDP SLM SLA Pilot SLR Build, Test, Release and Deployment Management Change Management Development Approved Build Approved RFP Released Design Approved Test Approved Warranty Approved Release Approved Review & Close Service Design / Figure 3.5 Aligning new services to business requirements

Aligning New Services Pilot or warrant period Live Operations (Steady State) Project Methodology: SDLC, RUP, PRINCE2, Agile Project {Project Team} SAC Strategy Design Transition Operation Improvement Requirements Statement Design Service Solution Develop Service Build Service Test Service Transition & Operations Involvement in the Design As has been demonstrated, there are many activities that have to be completed within the Service Design stage for a new or changed service. A formal and structured approach is required to produce the new service at the right cost, functionality, quality and within the right time frame. SDP SLM SLA Pilot SLR Build, Test, Release and Deployment Management Change Management Development Approved Build Approved RFP Released Design Approved Test Approved Warranty Approved Release Approved Review & Close Service Design / Figure 3.5 Aligning new services to business requirements

Hendershott Consulting Inc Email: len.hendershott@rogers.com ITIL process site: hci-itil.com