1 The Discovery Phase Why it’s the most important phase of any project A TUSC PMO Presentation.

Slides:



Advertisements
Similar presentations
Modern Systems Analyst and as a Project Manager
Advertisements

CATIA V4 Software Deployment Project Proposal
Course: e-Governance Project Lifecycle Day 1
Copyright © 2012 Certification Partners, LLC -- All Rights Reserved Lesson 10: IT Project and Program Management.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Copyright 2004 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Second Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
Project Management.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
Panorama Consulting Group LLC ERP Assessment, Selection, and Planning SAMPLE APPROACH.
Introduction to Project Management Avneet Mathur
1 June 15 / Slide 1 / Title of Document Top 10 Things Your Project Manager Should Be Telling You A TUSC PMO Presentation.
Creating a Secured and Trusted Information Sphere in Different Markets Giuseppe Contino.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Oracle Database Administration. Rana Almurshed 2 course objective After completing this course you should be able to: install, create and administrate.
Framework Project Concept Source – PMBOK®– 2008 Edition Project Management Professional Project Management Professional (P M P)
Lesson 10: IT Project and Program Management. Lesson 10 Objectives  Identify resources for technical data  Identify project management fundamentals.
Project Management Body of Knowledge PMBOK
PRESENTED BY TRUST THOMAS EROMOSELE STUDENT NO:
Basel Accord IITRANSITIONSERVICES Business Integration Support FCM Management Limited Paris New York Toronto.
Outcome Plans 11-Feb-09. Purpose of an Outcome Plan An outcome plan is a tool that helps in the definition, communication and scoping of a project. –ensures.
Miguel Nunes Information Systems Project Management IS Project Resources.
Degree and Graduation Seminar Project Management Processes
Copyright 2002 Prentice-Hall, Inc. Managing the Information Systems Project 3.1 Chapter 3.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project Modern Systems Analysis and Design Third Edition Jeffrey A. Hoffer.
Computer System Analysis
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Copyright © 2013 Pearson Education, Inc. Publishing as Prentice Hall Essentials of Systems Analysis and Design Fourth Edition Joseph S. Valacich Joey F.
Project Management: Madness or Mayhem
Roles and Responsibilities
Server Virtualization: Navy Network Operations Centers
Project Management Donald Hsu, Ph.D. Dominican College
© 2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
IS 460 Notes IS Strategic Planning By Thomas Hilton.
Module CC3002 Post Implementation Issues Lecture for Week 1 AY 2013 Spring.
Resources Performance time. resources Performance time 2.
Internet Business Foundations © 2004 ProsoftTraining All rights reserved.
Copyright 2006 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Third Edition Joseph S. Valacich Joey F. George Jeffrey A. Hoffer Chapter.
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.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
1 Outsourcing and OffShoring January 2004 Sandy Senti.
SacProNet An Overview of Project Management Techniques.
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.
Quality Activity Matrix Presented by Sandra Toalston President, SanSeek 1.
DEV234 Project Management For.NET Developers Marc Gusmano Director of Emerging Technologies The Information Management Group.
The Minnesota State Colleges and Universities system is an Equal Opportunity employer and educator. Information Technology Enterprise Strategic Investment.
普 华 永 道 Phase 1: Project Preparation Phase 1: Project Preparation Phase Overview Phase Overview.
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
Page 1 TEST in the large RELEASE REWORK ASSESS packaged application documentation models and source code management documents requirement alloc. matrix.
Lecture 2 –Approaches to Systems Development Method 10/9/15 1.
Copyright 2002 Prentice-Hall, Inc. Chapter 3 Managing the Information Systems Project 3.1 Modern Systems Analysis and Design.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
Copyright © 2009 Pearson Education, Inc. Publishing as Prentice Hall Chapter 3 Managing the Information Systems Project 3.1.
What is project management?
The Project Plan Plan Your Work, then Work Your Plan
Copyright 2001 Prentice-Hall, Inc. Essentials of Systems Analysis and Design Chapter 2 Managing the Information Systems Project 2.1.
IEEE Std 1074: Standard for Software Lifecycle
Chapter 3 Managing the Information Systems Project
Chapter 3 Managing the Information Systems Project
Description of Revision
Lesson 10: IT Project and Program Management
Getting Started with Project Management
{Project Name} Organizational Chart, Roles and Responsibilities
Chapter 2 Managing the Information Systems Project
Project Management and the Organization
Chapter 3 Managing the Information Systems Project
WORK STREAM TEAM DELIVERABLES
Working with Project Management Processes
Presentation transcript:

1 The Discovery Phase Why it’s the most important phase of any project A TUSC PMO Presentation

2 Discovery Phase  What is it?  When does it occur?  How does it compare with PMI’s Project Initiation and Planning phases?  What are the deliverables from this phase?

3 What does the Discovery Phase Focus on? 1. Project Objective 2. Critical Success Factors 3. Scope Definition 4. Risk Definition 5. Assumptions 6. Compliance Evaluation 7. Best Practices Process Validation 8. Deployment Requirements 9. Organizational Readiness 10. Project Plans

4 Focus Area 1: Project Objective  Defines business need and organizational goals  Indicates controlling factor(s) Time factor – meeting critical date Budget – cannot exceed $$ Corporate goal – streamline manufacturing by 10%  Indicates criticality factor mission critical to  Sales Force  HR & Payroll  Entire organization

5 Focus Area 2: Critical Success Factors Explore and Document key project Critical Success Factors (CSFs) in the following areas:  Business Process Level CSFs  Reduce cycle time  Increase customer base  Reduce service-call duration  Streamline order processing  Application / End User CSFs  Types of browsers supported  Types of interfaces supported  Standards that must be met  Security and user access levels  Performance Metrics that must be met

6 Focus Area 2: Critical Success Factors Success factors must be stated in a manner that is measurable! Not measurable if stated: “Must be able to collect / store customer data” It IS measurable if stated: “Must be able to collect customer data via: single intranet screen within order process two screens within customer maintenance data loader, within 1 sec per record speed

7 Focus Area 3: Scope Definition  What is in scope  What is NOT in scope  How will scope be managed  How will scope be measured

8 Focus Area 4: Risk Definition  Evaluate all areas: Hardware  Dev/Test/Prod Environments  New or Existing?  Performance? Technology  Bleeding Edge or Stable  Support / Maintenance  Knowledge base Resources  Turn over, Availability, Travel Business Processes  Change Aware  Qualify How likely is this risk?  Quantify What’s the cost if risk is realized?

9 Focus Area 5: Assumptions Communication Validation Identification

10 Focus Area 5: Assumptions - Infrastructure  Technology upgrades Infrastructure Networks Scanning Equipment  Hardware Development Test (QA/Stress) Production End User / Workstations Printers Disk Storage  Software Development tools Migration Tools Version Control Performance Monitoring

11 Focus Area 5: Assumptions - Change  Business Process Changes Will the project include business process re-engineering?  Validate timelines for “As is” vs “To be”  Define guide lines for BPR Inclusion and the “buy in” approach Acceptance of the “new world” How will process changes be communicated Consider using a BPR Marketing team  Town Hall Meetings  News Letters  blasts  Posters  T-shirts, Mugs, Stress Balls  Build Excitement

12 Focus Area 5: Assumptions - Project Team  Team Members, Roles and Authority Resource Availability Business Users Management Team Decision Making Authority Technical Team  Team Housing Where will the team work Is there Teaming space Dynamics of location  Team Building Create Trust Define Roles Find Common Thread to Unite

13 Focus Area 6: Compliance  Government Compliance Areas Sarbanes Oxley ACT  Separation of Duties  Data Access Levels  Business Process Analysis HIPAA Act  Data Security  Customer Data Security  Process Validations PCI Compliance  Data Encryption  Document Controls FDA Validation Requirements  Process definitions  Design, Dev, Test  Operational Support

14 Focus Area 6: Compliance  Application Security Requirements Document the type of security that will be needed.  Application Level Security Rqmnts  User Level Security Rqmnts  Screen Level Security Rqmnts  Field Level Security Rqmnts

15 Focus Area 7: Best Practices  Conflict Resolution Process  Risk Management Process  Scope Management Process  Escalation Processes defined and effective

16 Focus Area 8: Deployment Factors  Definition of user community Quantity of users or  Access levels Intranet Internet Dedicated or Leased Lines  User Access Plan User ID creation Access Approval process Phased roll-0ut Plan  Deployment Plan

17 Focus Area 9: Organizational Readiness  Infrastructure  Clear Understanding of Business Needs  Strong Upper Management Support  Project Team Strength & Weaknesses

18 Focus Area 10: Project Plans  Resource Plan  Communication Plan  Scope Management Plan  Change Management Plan  Risk Management Plan  Issue Management Plan  Quality Management Plan  Training Plan  Deployment Plan  Support Plan

19 Discovery Team Members  Executive Management Government compliance, Corporate Infrastructure, Budget  IT Management Validation of infrastructure, IT governance and compliance, resource availability, organizational readiness  Project Manager Plans: scope, risk, communication, resource  Business Managers Business objectives, critical success factors, deployment requirements, compliance, security, resource availability  IT Support Staff Standards, interfaces, resources, design review  Business Representatives / End-User Committee Validation of design and business objectives, data accessibility, organizational readiness for business level, application success factors  Business Systems Analyst Process analysis

20 Recap 1. Project Objective 2. Critical Success Factors 3. Scope Definition 4. Risk Definition 5. Assumptions 6. Compliance Evaluation 7. Best Practices & Process Validation 8. Deployment Requirements 9. Organizational Readiness 10. Project Plans

21 The Discovery Phase Why it’s the most important phase of any project A TUSC PMO Presentation References: Project Management Institute, A Guide to the Project Management Body of Knowledge, (PMBOK Guide). 3rd Edition, Project Management Institute, Pennsylvania, USA, Nov 2004 Neal Whitten, Neal Whitten’s No-Nonsense Advise for Successful Projects. USA, Management Concepts, Sept 2004.

22 Thank You