Discussion Items with Bruce

Slides:



Advertisements
Similar presentations
MIGRATION MIGR-09. How to Run Your Next Implementation... Don't Let It Run You! Patricia Johnson Senior Systems Consultant Strategic Systems Group, Inc.
Advertisements

Program Management Office (PMO) Design
Roadmap for Sourcing Decision Review Board (DRB)
Global Congress Global Leadership Vision for Project Management.
State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Test Automation Success: Choosing the Right People & Process
Major Incident Process
Project Management 6e..
<<replace with Customer Logo>>
(Project) SIGN OFF PROCESS June 21, 2010
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Financial Systems Needs Assessment Project Update Monthly Research Administrators Meeting March 11, 2010.
Defining the Project CHAPTER FOUR Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Panorama Consulting Group LLC ERP Assessment, Selection, and Planning SAMPLE APPROACH.
Defining the Project Chapter 4.
University of Southern California Enterprise Wide Information Systems Instructor: Richard W. Vawter.
IS&T Project Management: Project Management 101 June, 2006.
Certified Business Process Professional (CBPP®) Exam Overview
Software Test Plan Why do you need a test plan? –Provides a road map –Provides a feasibility check of: Resources/Cost Schedule Goal What is a test plan?
Business Consulting Services Agenda Discussion: Management Reports Discussion: Project Reports Discussion: Engagement Proposal Upcoming Events Review Project.
IS&T Project Management: How to Engage the Customer September 27, 2005.
Software projects Management & Development Alireza Saebi
| 2012 Sheraton Dallas Hotel, Dallas, Texas | May 22-25, 2012 Are Good Proposal Managers Two Faced? Yes, and they have to be! Kristin Pennypacker, AM.APMP.
Business Acquisition Process Implementation & transition Closing Negotiation of the transaction Due Diligence Engagement TargetIdentification.
Charting a course PROCESS.
Chicagoland IASA Spring Conference
Managing a Training Program Why train? Who will attend the training? What are the learning objectives? Strategies? Coverage? How will the training program.
 A project is “a unique endeavor to produce a set of deliverables within clearly specified time, cost and quality constraints”
Financials – Phase II Kick-Off Meeting September 11, 2008 Brenda Bolander, State Comptroller Michael Grisser, Project Manager.
The Evergreen, Background, Methodology and IT Service Management Model
Chapter 4 Defining the Project.
Defining the Project CHAPTER FOUR PowerPoint Presentation by Charlie Cook Copyright © 2014 McGraw-Hill Education. All Rights Reserved.
OSF/ISD Project Portfolio Management Framework January 17, 2011.
Do it pro bono. Strategic Scorecard Service Grant The Strategy Management Practice is presented by Wells Fargo. The design of the Strategic Scorecard Service.
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Epiphany Partners Corporation HealthTechNet ClerePath TM Solution July 21, 2006.
GBA IT Project Management Final Project - Establishment of a Project Management Management Office 10 July, 2003.
Basic of Project and Project Management Presentation.
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.
1 10/14/2015ã 2007, Spencer Rugaber The Waterfall Process Software plans and requirements Validation System feasibility Validation Product design Verification.
Applying Business Process Re-engineering
普 华 永 道 Phase 1: Project Preparation Phase 1: Project Preparation Phase Overview Phase Overview.
Project Kick-off Meeting Presented By: > > > > Office of the Chief Information Officer.
Introduction to the Continual Service Improvement Toolkit Welcome.
 Project management is the organization and management of resources (i.e. people, information, tools and machines, materials, time, capital and energy)
Request for Proposal (RFP)
J. Scott Hawker p. 1Some material © Rational Corp. Rational Unified Process Overview See and use the RUP Browser on lab machines.
Microsoft Corporation
Sage ERP X3 Standard Edition Methodology
Team-Based Development ISYS321 Managing the Information Systems Project.
1 Chapter 11 Planning. 2 Project Planning “establishing a predetermined course of action within a forecasted environment” “establishing a predetermined.
BizForceOne by MegaSolutionCenter (MSC), USA BIZFORCEONE OPERATING SYSTEM BEST FIT IMPLEMENTATION.
Info-Tech Research Group1 Info-Tech Research Group, Inc. Is a global leader in providing IT research and advice. Info-Tech’s products and services combine.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.
IS&T Project Reviews September 9, Project Review Overview Facilitative approach that actively engages a number of key project staff and senior IS&T.
SAP Methods Context PRM1_02.1 PwC Methods & Risk Management Lesson Objectives Participants will be able to: Understand how methods can mitigate project.
Project Management 6e..
Project Management 6e..
Project life span.
Description of Revision
Our Change Management Approach
Where We Are Now. Where We Are Now Defining the Project (100) Step 1: Defining the Project Scope Step 2: Establishing Project Priorities Step 3: Creating.
Guidance notes for Project Manager
IS&T Project Reviews September 9, 2004.
By Jeff Burklo, Director
Project Management Methodology Documentation Chart
Portfolio, Programme and Project
{Project Name} Organizational Chart, Roles and Responsibilities
Presentation transcript:

Discussion Items with Bruce December 13, 2011

Next items to tackle Build depth to Product Development Lifecycle. We have defined the framework and many of the tasks. The next step is to gather all of the tools, refine detailed approach, and scale to application. Build the inventory of “Consistent Disciplines” Decision making (where, who, how) Issue Resolution and escalation Testing Facilitate Future direction and roadmap and create graphical documentation

Operations Product Lifecycle Concept Phase Requirements Phase Design Phase Development (Execution) Phase Testing Phase Implementation Phase Post Sign-off from EMT to proceed Product Owner sign-off of Business Processes and Requirements Product Owner sign-off on Design Phase IT and Product Owner sign-off to proceed to Test Phase Go/No-Go decision Back-out or retain production Development of Business Case and Feasibility Study Design Project Charter Complete Accountability Charting Develop business requirements including functionality, interfaces and reporting Develop technical requirements Develop business process documentation Design detailed Project Plan Design Interface Criteria Plan Design Test and Acceptance Criteria Design Risk Management Matrix Agree upon Change Management Process Design Communication and Status Reporting Templates Develop Resource Plan Perform Vendor acquisition activities (RFP, Selection, etc.) Prepare Development Environment Develop Training Material Build Deliverables Perform Issue Resolution Perform Change Management Design User Test Scripts Design Integration Test Scripts Prepare Test Environment Perform Unit Testing Perform Integration Testing Refine Training Materials Develop Back-Out Plan Conduct Training Sessions Refine Back-Out Plan Confirm Issue Resolution Process for Production Perform Data Conversion Install Production System Perform Post Mortem Analysis Status, Communications and Monitoring Processes

Facilitated Session Approach 4 Define Current State Roadmap Define Future State 1 3 SWOT Drivers Headwinds Tailwinds Areas of Focus Key Outcomes Significant Changes Things we need Operations (processes) Financials Competencies Technology 2 Foundation Values Principles Purpose

90 Day Transition Plan Customer Expectations Sept October November December Week 1 Week 2 Week 3 Week 4 Week 5 Week 6 Week 7 Week 8 Week 9 Week 10 Week 11 Week 12 Customer Expectations Develop and document customer experience Determine service level measurements Determine immediate and sustainable communication Develop 1/1 priorities Execute 1/1 priority plans Determine quick wins Assign operations staffing Redundancy/ Cost Reductions Operational activity map by product Analyze map & develop targets and goals Develop transition plan and timings Develop & employ measurements to communicate to Business lines Operations Alignment Refine & educate competency map Align Operations Mgrs to each Business Line Develop common disciplines: Implementation, BA, Proj Mgmt, Reporting, Decision Making Realign based on Redundancy / Cost Reduction Plan