ServiceNow Special Interest Group Phased WorkTemplate Information & Educational Technology 1 DRAFT 04.11.2016.

Slides:



Advertisements
Similar presentations
Facilitated by Joanne Fraser RiverSystems
Advertisements

Roadmap for Sourcing Decision Review Board (DRB)
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Course: e-Governance Project Lifecycle Day 1
Software Quality Assurance Plan
<<Date>><<SDLC Phase>>
Project Proposal Project ? Project Sponsor Project Manager Version
Chapter 10 Schedule Your Schedule. Copyright 2004 by Pearson Education, Inc. Identifying And Scheduling Tasks The schedule from the Software Development.
The Business Analyst Role in Agile Projects
Chapter 3 Project Initiation
Centers for IBM e-Business Innovation :: Chicago © 2005 IBM Corporation IBM Project October 2005.
Pertemuan Matakuliah: A0214/Audit Sistem Informasi Tahun: 2007.
4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.
Chapter 3: The Project Management Process Groups
ECM Project Roles and Responsibilities
Chapter 3 Project Initiation. The stages of a project  Project concept  Project proposal request  Project proposal  Project green light  Project.
IS&T Project Management: How to Engage the Customer September 27, 2005.
Chapter 9. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Charting a course PROCESS.
EASTERN MICHIGAN UNIVERSITY Continuity of Operations Planning (COOP)
ENTERPRISE DATA INTEGRATION APPLICATION ARCHITECTURE COMMITTEE OCTOBER 8, Year Strategic Initiatives.
Project Management Process Overview
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Using IBM Rational Unified Process for software maintenance
Tuesday, June 8 th, Agile Development-Successful Delivery & Implementing Across the Enterprise.
-Nikhil Bhatia 28 th October What is RUP? Central Elements of RUP Project Lifecycle Phases Six Engineering Disciplines Three Supporting Disciplines.
Current Trends in Systems Develpment
Business Systems Development SDLC and introduction to the Microsoft Solutions Framework Team and Process Models.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
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.
Week 2 Seminar: Project Scope Management
Strong9 Consulting Services, LLC 1 PMI - SVC I-80 Breakfast Roundtable Monthly Meeting Thursday, October 12, :00 am – 9:00 am.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
Applying Business Process Re-engineering
Chapter 11. Intro  What is Project Management?  Project Manager  Project Failures & Successes Managing Projects  PMBOK  SDLC Core Process 1 – Project.
Object-oriented Analysis and Design Stages in a Software Project Requirements Writing Analysis Design Implementation System Integration and Testing Maintenance.
Project Plan. Project Plan Components Project Overview – Description and Strategy Business Case Summary Key Deliverables and Scope Critical Success Factors.
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
{ Phases of Project & life cycle Prepared by: Syed ShahRukh Haider.
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
Chapter © 2012 Pearson Education, Inc. Publishing as Prentice Hall.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Validate Scope What we have: Requirement Traceability Matrix Verified Deliverables What we do: Inspection What we get: Accepted Deliverables.
SOLUTION What kind of plan do we need? How will we know if the work is on track to be done? How quickly can we get this done? How long will this work take.
Project management Topic 4 Starting up a project.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
The Implementation of BPR Pertemuan 9 Matakuliah: M0734-Business Process Reenginering Tahun: 2010.
Overview of RUP Lunch and Learn. Overview of RUP © 2008 Cardinal Solutions Group 2 Welcome  Introductions  What is your experience with RUP  What is.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Development Project Management Jim Kowalkowski. Outline Planning and managing software development – Definitions – Organizing schedule and work (overall.
Irish Institute of Training & Development JOHN SMITH & TREVOR DAGG.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
> Blueprint Executive Summary >. Presentation Purpose; This Executive Summary captures the key details and outputs which merit stakeholder alignment to.
Process 4 Hours.
Systems Analysis and Design in a Changing World, 4th Edition
SAFe Workshop - Oct 17 Presenter: Ray Brederode
Chapter 3: The Project Management Process Groups: A Case Study
Description of Revision
Project Roles and Responsibilities
Guidance notes for Project Manager
Project Ideation Agile Down-to-Earth © 2016.
ATS Architecture Design Solution Intent
Portfolio, Programme and Project
Executive Project Kickoff
{Project Name} Organizational Chart, Roles and Responsibilities
(Insert Title of Project Here) Kickoff Meeting
Description of Change(s)
Presentation transcript:

ServiceNow Special Interest Group Phased WorkTemplate Information & Educational Technology 1 DRAFT

DRAFT 2 Allocated resources Develop work packages Service validation and testing Incremental reviews PLAN Vision for the system Desired features Resources needs/requirements INITIATION MANAGEMENT PLAN Clear purpose and scope Significant Risks HI Level Requirements HL Roadmap Team organization Risks Approach to work System architecture Build approach Detailed requirements / Sprint backlog ANALYSIS & DESIGN CONSTRUCTION BUILD RUN TRANSITION Release plan Product documentation User training plan Support training plan Communication plans Support documentation OPERATION SIG Phased Deliverables Note: Phase deliverables may vary depending on risk, complexity, size. Maintenance Plans Support Plans Improvements

DRAFT 3 Instructions Each sections should be filled in as the SIG team transitions through each phase. Do not complete all sections at once. Only complete the sections that pertain to the phase in which you are currently working (Plan, Build or Run). You will update the remaining sections as you enter each phase. For each section, enter bullet points to use as talking points when your team meets with the Oversight Group Committee. Attach any detailed documents that you would like the Oversight Group to review. Note: Delete the blue text instructions.

DRAFT 4 PLAN Phase INITIATION Stage Vision for the system [What will the solution look like when its done? What benefits will it provide? ] Desired features [ What are the key success factors, features or functionality that must be achieved to consider this a successful solution? ] Assumptions [ Enter conditions, technology, process, or other assumptions which may not have been verified and will need investigation. ] Resources needs/requirements [ What are the anticipated skills to support the technology or service? What kind of operational support will be needed? documentation? training? ] Anticipated Risks [ What risks you foresee which could seriously impact or stop the work? ] Primary Performer: Project Facilitator

DRAFT 5 PLAN Phase PLANNING Stage Scope [ Describe the boundaries of the work? Is it for local, departmental, organizational or campus use? Etc.] Development Objectives [ Enter 2 to 5 key objectives.] High Level Timeline of activities [ Provide a high level timeline or milestone plan. If you prefer, you can attach a document or project] Approach to work [ Describe how the method that will be used to perform the work. This is the approach to keep the work moving. Example: Scrum, or other project methodology]. Risks [ Enter any high impact risks that were identified in this Planning stage. Have any previously identified risks been mitigated? ] Primary Performer: Project Manager

DRAFT 6 PLAN Phase PLANNING Stage Notes and follow up actions from the Oversight Group Meeting [ Enter any follow-up actions from the meeting. Include notes to for historical purposes.] Primary Performer: Project Facilitator

DRAFT 7 BUILD Phase ANALYSIS & DESIGN Stage Solution Architecture Architectural goals and philosophy [Describe the philosophy of the architecture. Identify issues that drive design decisions such as out of box functionality choices versus customization and maintenance. Are there unique parts to the architecture such as data feeds? API integrations with other systems? Architecturally significant requirements [High level summary of architectural requirements that must be met to realize the architecture.] Assumptions and dependencies [List the assumptions and dependencies that drive architectural decisions. This could include sensitive or critical areas, dependencies on other systems, additional infrastructure, the skill and experience of the team, the availability of important resources, etc.] Primary Performer: Developer Additional Performers: Business Analyst

DRAFT 8 BUILD Phase CONSTRUCTION Stage Build Team [ Identify the team members and roles they will play in the SIG. A SIG representative must be identified.] Build Milestones [ Provide a high level milestone plan. If you prefer, you can attach a document, link to a project plan or scurm board] Stakeholder Review Plan [ Describe how you plan to review progress with stakeholders (not the Oversight Group). Example – sprint reviews bi-weekly] Primary Performer: Developer

DRAFT 9 Notes and follow up actions from the Oversight Group Meeting [ Enter any follow-up actions from the Oversight Group meeting. Include notes to for historical purposes.] BUILD Phase CONSTRUCTION Stage Primary Performer: Developer Additional Performers: Tester

DRAFT 10 RUN Phase TRANSITION Stage Release Plan [ How will the system be released into Production?] Product Documentation [ What product documents have been created?. Where are they accessed? Attach documents or links as appropriate.] Support Training [ How will support training will be provided to operational support personnel? ] User Training [ How are users of the system going to be trained? What materials will be made available to them? ] Communication Plan [ Briefly identify who is in the communication plan. You can attach a document or link to the information.] Target Deployment (Change Record) [ If a change record has been created, enter it here.] Change Number: Primary Performer: Project Facilitator Additional Performers: Business Analyst Support Analyst

DRAFT 11 RUN Phase OPERATION Stage Ongoing maintenance plan [ What is the plan for ongoing feature requests, changes, and improvements to the system?] Support plan(s) [ How will incidents, requests and customer support questions be handled? ] Feature and Improvement plan [ How will features and improvements be developed? Will the SIG team build them or IET Client Services? Will vendor resources be used? ] Primary Performer: Production Support Additional Performers: Process Manager

DRAFT 12 RUN Phase OPERATION Stage Notes and follow up actions from the Oversight Group Meeting [ Enter any follow-up actions from the meeting. Include notes to for historical purposes.] Primary Performer: Production Support Additional Performers: Process Manager