Phase II, The Pilot Area Kick-off

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

State of Indiana Business One Stop (BOS) Program Roadmap Updated June 6, 2013 RFI ATTACHMENT D.
Beta Testing: The Contractor’s Perspective Trns·port User Group Meeting October 2005.
Software Quality Assurance Plan
Panorama Consulting Group LLC ERP Assessment, Selection, and Planning SAMPLE APPROACH.
APPLICATION DEVELOPMENT BY SYED ADNAN ALI.
Ashoka Indonesia Implementation Kick-off August 2014
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Project Execution.
Introduction to Information System Development.
 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.
Web Development Process Description
Introduction to RUP Spring Sharif Univ. of Tech.2 Outlines What is RUP? RUP Phases –Inception –Elaboration –Construction –Transition.
Software Configuration Management
SIUE Injury Tracking System Project Plan. Team Members: Robbie Marsh Robbie Marsh –Project Manager/Webmaster Ken Metcalf Ken Metcalf –Lead Programmer.
Bring Your Business into the 21 st Century : Part 1 WasteExpo 2011 Improving Your Financial Management System.
1 IMPAC II SW Development Life Cycle Requirements Analysis Preliminary Design Detailed Design PrototypeBuild - Test Documentation Conversion & Pilot Production.
Project Management Workshop Overview By Tarek Lahdhiri Region 4 PACE Chair IEEE Region 4 Meeting January 30/31, 2004.
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
CSI-MAXIMUS, Inc CSI Comprehensive Service & Support Implementing the CSI Way.
© Mahindra Satyam 2009 Configuration Management QMS Training.
Let Ascension take your business to new heights Tender Manager Scott Warnock Andrew Smillie.
Project Board Meeting. Agenda  Project Progress Update  TxPROS Demo  CPS Modernization Options  Call for Direction  Next Steps  Q & A.
Develop Project Charter
Implementing SiteManager in a non-P/L/C State Dawn E. Scheel, P.E. TxDOT.
PDS4 Project Report PDS MC F2F University of Maryland Dan Crichton March 27,
1 Single Entry Model (SEM) Go-Live Update TAC Update August 6, 2009.
Presenter: Igna Visser Date: Wednesday, 18 March 2015
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Routing Texas into the Future
Sample Fit-Gap Kick-off
SCT Project Management Issues
Project Board Meeting.
Software Project Configuration Management
Business (Agency) Process Discovery and Documentation Workshop
Systems Analysis and Design in a Changing World, 4th Edition
Software Configuration Management
Banner Project Student Team Update
Project Board Meeting.
Ian Bird GDB Meeting CERN 9 September 2003
Project Management Processes
Project Management Managing Project Execution
Project Management Lifecycle Phases
TechStambha PMP Certification Training
Implementation Strategy July 2002
Project Management.
Introduction to Tech Communication & Project Management Arthur C.M. Chen , Rm
Description of Revision
Project Initiatives Identified by the CIA Project
Engineering Processes
Proposed Software Development Process
[Work Order #] [ARB Date]
CIS12-3 IT Project Management
Project Management Processes
X-DIS/XBRL Phase 2 Kick-Off
Employee engagement Delivery guide
Ctclink executive leadership committee May 31, 2018
Manage Business Continuity Introductory Brief
Configuration Management
Joint Application Development (JAD)
Executive Project Kickoff
Project Kick-off <Customer Name> <Project Name>
{Project Name} Organizational Chart, Roles and Responsibilities
Implementation and Migrating to iModules
(Insert Title of Project Here) Kickoff Meeting
Project Name Here Kick-off Date
Presentation transcript:

Phase II, The Pilot Area Kick-off

Welcome & Introductions

Agenda Project Progress-to-Date Phase II Activities Overview Team Approach – R & R Testing Process Reporting and Change Control Next Steps Q & A Quick review of today’s agenda

Progress-to-Date Phase I Design & Planning Let’s take a minute to look at what’s been accomplished so far

Milestones (MS) MS 1 – Solidifying project approach Deliverables included: Project Approach Document High-level WBS, WBS Dictionary & RAM Web-based Project tracking tool Issue Defect & Resolution tracking tool Reporting Requirements Document MS 1 was delivered on-time and to specifications A quick recap of Milestone 1 that established our project approach between the vendor and the TxDOT team and established our on-line tracking tools

Milestones (cont.) MS 2 – Joint Application Design (JAD) Deliverables included: JAD schedule and assignments document JAD sessions themselves JAD Summaries Design Documents for application modules, databases (data models), data conversion, and external systems interfaces MS 2 deliverables were presented on-time and approved

Milestones (cont.) MS 2 – Activities Recap Design Documents included: System Overview Data Conversion Systems Interface User Interface/Mapping Restrictions Management Routing Re-Route Identification Report Generation Database Design documents for GIS, Bridge, Restrictions, Permits, Users, Saved Trips and Audit Administrative Trail As you can see, the list of detail design documents generated following the JAD sessions were extensive. These documents will, in fact, be “living documents, as we move forward into the prototype and the pilot area and will be revised as we further refine the approach.

Milestones (cont.) MS 3 – Project Planning Deliverables included Plans for: Data Acquisition, Conversion, and Integration Infrastructure Design/Development Application Development & Testing Security Considerations Documentation, Training & Marketing Implementation and Transition to Production MS 3 deliverables were presented on-time and approved

Milestones (cont.) MS 4 – WBS & Project Scheduling Deliverables included: Expanded WBS & WBS Dictionary Expanded Responsibility Assignment Matrix (RAM) Precedence Diagram & Critical Path document Detail Work Schedule MS 4 deliverables were presented on-time, reviewed, revised and are in final review for approval

Pilot Area Development Phase II Pilot Area Development Activities Overview

Phase II Milestones MS 5 – Data Acquisition & Integration Primary Deliverables include: PSDC’s Acquisition of Tele-Atlas & TxDOT data Data Conversion/Integration prototype Pilot Area GIS Map Testing/validation Primarily by PSDC and Permit’s Map Coordinators with assistance from the Districts, TPP, BRG, CST/PAV and TSD’s GIS

Phase II Milestones (cont.) MS 6 – Application Modules Primary Deliverables include: Restrictions Management Prototype Testing/Validation – Districts/Permits MC Routing Module Prototype Testing/Validation – Permits/Customers Reporting Module Prototype Testing/Validation – BRG, CST/PAV, Districts, Permits

Phase II Milestones (cont.) MS 7 – Map Data Maintenance Primary Deliverables include: Map Data Maintenance Pilot Program Updated Pilot Area GIS Map Testing/validation Primarily by PSDC and Permit’s Map Coordinators with assistance from the Districts, TPP, BRG, CST/PAV and TSD’s GIS

Phase II Milestones (cont.) MS 8 – Pilot Area Integration Testing Primary Deliverables include: Documented Test results of full system integrated testing which will entail a planned out, synchronized, test process to ensure all aspects work together and compliment each other Testing/validation Testing will involve PSDC, Permit’s Map Coordinators, Permit routing staff, Districts, BRG, CST/PAV, TPP, TSD’s GIS and possibly select customers. Basically, all of us here.

Team Approach R & R

Phase II - Players and their roles PSDC (Promiles) GIS Data integration/manipulation Application development of Prototype modules Unit Testing Defect repair and unit re-test Documentation

Phase II - Players and their roles (cont.) MCD Permits Staff Map validation Test scenarios development Restrictions, Routing & Reporting Testing Defects and recommendations recording

Phase II - Players and their roles Districts (ME and PC roles) Map validation assistance Restrictions test scenarios Restrictions & Reporting Testing Defects and recommendations recording

Phase II - Players and their roles Customers (Work Group members) Routing Testing Defects and recommendations recording

Phase II - Players and their roles TPP TRM/Roadway data source Map validation assistance TSD’s GIS Group GIS interface support (TPP, BRG & CST/PAV data to PSDC)

Phase II - Players and their roles BRG Bridge information data source (SME) Map validation assistance Reporting Testing Defects and recommendations recording

Phase II - Players and their roles CST/PAV PMIS/Load Zone data source (SME) Map validation assistance Reporting Testing Defects and recommendations recording

Phase II - Players and their roles MCD Tech Support CPS interface support In-house technical support Defects and recommendations recording

Phase II - Players and their roles PMT & Project Sponsor Project leadership/over sight Defects and recommendations recording/tracking ICCC for recommended changes

Reporting & Change Control Here we turn the session over to PSDC for them to demo the route testing prototype?

PSDC’s Defect and Issue Identification / Reporting Process

Change Control

Change Control Process

Change Control Process

Change Control Process

Next Steps What’s on the schedule next

Between Now & 9/30/08 Establish specific sub-teams for the various testing needs Teams develop testing scenarios, data/scripts, and schedules Assignments within Teams for specific Roles & Responsibilities Conduct testing & report results Repeat process to test prototype changes made in response to bug reports until done………………

Next Steps (Cont.) What will be left? Phase III – Statewide Application Basically Phase II over again but on a state wide basis Initial development of training material Phase IV – Performance/Acceptance Testing To establish scalability (performance/stress testing) and benchmark the capability Full blown acceptance testing against a rigorous criteria and external customer beta testing

Next Steps (Cont.) Phase V – Training, Marketing & Documentation Finalize materials Identify & schedule resources Conduct training (MCD, Districts/Divisions and external customers) Phase VI – Implementation & Acceptance Implementation and transition to full production mode Project close out

The Project management Team and the Sponsor stand ready to respond to any questions that you might have. Q & A