The 9 steps to successful project implementation From BD to Operations.

Slides:



Advertisements
Similar presentations
best practice project management methodology ©Platinum Services Group Limited What is XPRODi ?
Advertisements

Texas Department of Information Resources Presents
© 2007 AT&T Knowledge Ventures. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Knowledge Ventures. Interactive Solutions & Design Group.
Implementation: SLA & SOP Processes Purpose Strategy Foundation We Deliver Competitive Advantage to our Customer's Global Supply Chain.
Implementation I - demo. Schedule * Project status -achieving the goals of the iteration -project metrics * Used work practices * Work results -presenting.
GAI Proprietary Information
Stepan Potiyenko ISS Sr.SW Developer.
Managing the Information Technology Resource Jerry N. Luftman
Project Process Discussion Adam D. Martinez Mgr, Market Ops Divisional Projects Organization ERCOT RMS Meeting May 10, 2006.
Page 1 R Risk-Driven and Iterative Development. Page 2 R Copyright © 1997 by Rational Software Corporation What the Iterative Life Cycle Is Not It is.
Systems Development (SD) Presentation Michael Webb IT Director for Medicaid Utah Department of Health UDOH Informatics Brownbag August.
SAIC-F QA Internal Process (DRAFT ) Sudha Chudamani QA Team, Frederick National Lab Jan 2, 2013.
The Game Development Process. Typical Development Cycle Idea Proposal Design Evaluation Coding Testing Release.
Release & Deployment ITIL Version 3
DPW BD&C Employee Performance Evaluation Guideline Discussion
OSF/ISD Project Portfolio Management Framework January 17, 2011.
11 the best Customer satisfaction enhancement plan N. Jerry Simonoff Director, IT Investment & Enterprise Solutions CIO-CAO.
Agenda Teams Responsibilities Timeline Homework and next steps.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
1 ISA&D7‏/8‏/ ISA&D7‏/8‏/2013 Systems Development Life Cycle Phases and Activities in the SDLC Variations of the SDLC models.
Certificate IV in Project Management Introduction to Project Management Course Number Qualification Code BSB41507.
The objectives of Phase G are to Ensure conformance with the Target Architecture by implementation projects Perform appropriate Architecture Governance.
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.
BA 471 Management Information Systems Process Maturity and Quality.
Project Charters Module 3
INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.
T Project Review WellIT PP Iteration
Page 1 TEST in the large RELEASE REWORK ASSESS packaged application documentation models and source code management documents requirement alloc. matrix.
Project roles and responsibilities
Provided by Training, HR & OD Department Karen. Learning Management Systems January 2014.
Test status report Test status report is important to track the important project issues, accomplishments of the projects, pending work and milestone analysis(
An organizational structure is a mostly hierarchical concept of subordination of entities that collaborate and contribute to serve one common aim... Organizational.
Systems Analysis & Design AUTHOR: PROFESSOR SUSAN FUSCHETTO 10/24/
Sistemas de Información Agosto-Diciembre 2007 Sesión # 9.
T Iteration Demo Tikkaajat [PP] Iteration
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
The Software Engineering Process Discussion Slides.
A planned process to activate a community to use its own social structures and any available resources to accomplish community goals decided primarily.
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
V-Shaped Software Development Life Cycle Model. Introduction: Variation of water fall model. Same sequence structure as water fall model. Strong emphasis.
ISIS Project Status Report May 18, 2006 Prepared by MAXIMUS, Inc Education Systems Division for the ABT Committee.
Ondřej Přibyl L3: System Development Life Cycle page 1 Lecture 3: System Development Life Cycle Doc.Ing. Ondřej Přibyl, Ph.D. Department of applied mathematics.
Copyright 2015, Robert W. Hasker. Classic Model Gathering Requirements Specification Scenarios Sequences Design Architecture Class, state models Implementation.
Re-alignment of Responsibility Shift from Jan to Tony.
Internal developer tools and bug tracking Arabic / Hebrew Windows 3.1Win95 Japanese Word, OneNote, Outlook
ERA Project Team Meeting Project Management Plan April 23, 2002.
Interset Support Overview March 2017
Managing the Project Lifecycle
Project life span.
ITS Strategic Planning Guidelines
Class 7 – Inception Phase: Steps & techniques
Infrastructure Support
IEEE Std 1074: Standard for Software Lifecycle
Project Management 6e..
Description of Revision
Software Development Process
The 9 steps to successful project implementation
Student Administration and Support Programme and Project Timelines
CS101 Introduction to Computing Lecture 20 SW Development Methodology
The Software Engineering Process
ARB Schedule Locations
Student Administration and Support Programme and Project Timelines
WordPress Unit Web Coordinators
Project Management 6e..
Project Kick-off <Customer Name> <Project Name>
{Project Name} Organizational Chart, Roles and Responsibilities
System Analysis and Design:
Project Management 6e..
IT Next – Transformation Program
Presentation transcript:

The 9 steps to successful project implementation From BD to Operations

BD to Production Timeline Jan Tony

Timeline 1. Idea 2. Decision to go further 3. Decision with ROI 4. GO 5. Development 6. QA 7. Deployment 8. Production 9. Post Mortem

1.IDEA Phase where Business Development work out the ideas Identify ideas Work out some of the high level concepts Work towards a 20 Questions doc

2. Decision V1-Can Abort “To Look further” is decided Bring Operations and SW Mgr into the know on a high level Start working towards high level schedules Deliverables Business case ROI Identify contacts

3. Decision V2-Committed Tony, Rick, Lee are brought in More detailed doc with requirements Compliance Review Preliminary project plan Architecture fit analysis PM assignment Management team will decide priority All docs for Tony to run until completion will be created

4. Go Decided to go forward and implement Requirements to be delivered –Full Requirements Doc –Full Project Plan (schedule) –Complete Architecture implementation –PM assignment Jan is used for technology advice henceforth Tony is the main contact from here on in

5. Development Development manager tracks progress Publish progress in docs Publish progress on intranet 3 Documents need to be created –Software Design –Deployment Document –Users Guide

6. QA Work with outside entities for QA Work with inside entities for QA QA updates schedules on public docs/intranet 2 Documents need to be created –Testing procedures –??

7. Deployment Plan for deployment Deployment documentation is complete Deployment check-off list is done Operations accepts project Deployment implementation

8. Production This is where we make money!! Hand over to production staff We are done SPR fixes only Escalation by predefined procedures only

9. Post Mortem – How we did Evaluate metrics Perform analysis Revisit Process Enhance all steps and processes See if we could have done it better Job well done