1 Business (Agency) Process Discovery and Documentation Workshop PeopleSoft Phase II Tuesday, October 23, 2007 9:00 AM to 12:00 Noon Concourse Theatre.

Slides:



Advertisements
Similar presentations
System Development Life Cycle (SDLC)
Advertisements

Project Scope Management (Day 2)
Software Quality Assurance Plan
ORGANIZATION. 2 Purchasing & Inventory Assessment Occurrence Management Information Management Process Improvement Customer Service Facilities & Safety.
Managing Project Scheduling. What is Project Scheduling? The process of: – defining project activities – determining their sequence – estimating their.
Introduction to Project Management Chapter 6 Managing Project Scheduling Information Systems Project Management: A Process and Team Approach, 1e Fuller/Valacich/George.
Project Scope Management
Project Cost Management Estimation Budget Cost Control
Project Integration Management Sections of this presentation were adapted from A Guide to the Project Management Body of Knowledge 4 th Edition, Project.
Hyperion EPM Overview & Case Study.
Computer Engineering 203 R Smith Requirements Management 6/ Requirements IEEE Standard Glossary A condition or capability needed by a user to solve.
Use Case Analysis Chapter 6.
SE 555 Software Requirements & Specification Requirements Validation.
Computers: Tools for an Information Age
Introduction to Software Engineering Dr. Basem Alkazemi
Chapter 5: Project Scope Management
Introduction to SAP R/3.
Procurement From the 20 th to the 21 st Century Copyright Byron Honoré This work is the intellectual property of the author. Permission is granted.
Business Process Management with Activiti João Silva (CERN, GS-AIS) 21st of October, 2014 BUSINESS PROCESS MANAGEMENT WITH ACTIVITI.
Project Scope Management
Statewide Financial System Program 1 AR 215 Creating and Maintaining Receivables AR 215 Creating and Maintaining Receivables Welcome.
System Implementation
Introduction to Computer Technology
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
Release & Deployment ITIL Version 3
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
What is Business Analysis Planning & Monitoring?
Systems Analysis and Design in a Changing World, 6th Edition
Topic 2- 1ICT 327 Management of IT Projects Semester 1, 2005 Topic 2 Project Planning & Initiation Schwalbe: Chapter 3 Compiled by Diana Adorno and contributions.
Software Testing Lifecycle Practice
1 BTEC HNC Systems Support Castle College 2007/8 Systems Analysis Lecture 9 Introduction to Design.
What is Project Management? How does it affect how you do your job?
Demystifying the Business Analysis Body of Knowledge Central Iowa IIBA Chapter December 7, 2005.
Roles and Responsibilities
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
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.
2010 W EST V IRGINIA GIS C ONFERENCE Wednesday, June 9, 2010.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
SacProNet An Overview of Project Management Techniques.
Lecture 6. Review of Lecture 5 Company strategic planning: mission and objective statements and competitive strategy. Planning Methods: Top-down, Bottom-up.
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.
Sunflower Project Data Conversion Workshop May 5, 2009.
Process Walk & SIPOC Define Kaizen Facilitation. Objectives Understand the process as a “system” Describe the concept of an entity and how it relates.
National Instrument Affects All Trade-Related Parties Jane Davis Executive Director, Canadian Capital Markets Association Institutional Trade Matching.
University of Southern California Center for Systems and Software Engineering Barry Boehm, USC CS 510 Software Planning Guidelines.
Microsoft Office Project 2003: Selling EPM in your Organization Matt Wilson Business Solutions Specialist LMR Solutions.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Project Scope Management 1. 2 Learning Objectives Understand the elements that make good project scope management important. Explain the scope planning.
 An Information System (IS) is a collection of interrelated components that collect, process, store, and provide as output the information needed to.
The Project Plan Plan Your Work, then Work Your Plan
BGSU/PeopleSoft Introducing Financial Management Solutions & Enterprise Performance Management.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Internal Sales Policy and Procedure Updates. Agenda o Policy o Procedures o Roles & Responsibilities o Definitions o Questions & Answers anytime during.
Defining and Managing Project Scope. MOV Scope Phases Time Estimates Resources Tasks Schedule Budget Sequence Project Planning Framework.
The Project Management Process Groups
© 2008 Prentice Hall6-1 Introduction to Project Management Chapter 6 Managing Project Scheduling Information Systems Project Management: A Process and.
Introduction for the Implementation of Software Configuration Management I thought I knew it all !
Sample Fit-Gap Kick-off
Requirements & Process Review Report
Business (Agency) Process Discovery and Documentation Workshop
Auditing Information Technology
Software Planning Guidelines
Chapter 5: Project Scope Management
Create a project schedule
IT Governance Planning Overview
Company X Process Mapping Training
Project Integration Management
Software Testing Lifecycle Practice
Presentation transcript:

1 Business (Agency) Process Discovery and Documentation Workshop PeopleSoft Phase II Tuesday, October 23, :00 AM to 12:00 Noon Concourse Theatre Oklahoma City, OK

2 AGENDA Business (Agency) Process Discovery and Documentation Workshop 9:00am -9:15am -- Kickoff, Introductions and Housekeeping 9:15am to 10:30am – Workshop Presentation 10:30am to 10:45am – Break 10:45am to 12:00noon – Questions and Answers

3 Why? This workshop will provide a BASIC GUIDELINE to assist you in documenting your “AS-IS” business (Agency) processes, in a format that will be capable of providing an "apples to apples" comparison (fit gap analysis) to delivered PeopleSoft Financials v8.9 functionality for Oklahoma Phase II modules.

4 PS Phase II Modules Quick Review (1 of 2) Grants Management –Acquisition and tracking of Grant funding Project Costing –Project Accounting and Tracking Contracts Management (Revenue) –Establishes revenue contracts with external customers or sponsors. Billing (Invoicing) –Creating customer invoices and drawing grant funding. Receivables (AR)

5 PS Phase II Modules Quick Review (2 of 2) Assets Management –Tracking and depreciating capital assets. Inventory –Tracking and re-ordering of inventory stock.

6 How does PS display its delivered Business (Agency) Processes? Generally Generic in Nature –High Level Sequence of Functionality (or Features) designed to illustrate a generic business process. –And yet, very specific to PeopleSoft delivered Functionality. Extensive Use of Swim Lanes –Each Swim Lane consists of a Generic Organizational Role. Example: Financial Administrator, Approval Authority, Principle Investigator, Sponsoring Agency –Activities (Boxes of Tasks) within each swim lane. –Tasks are the lowest Level of Process Identified. Extensive Decision Points

7 PS FLOW CHART EXAMPLE (This is one of the apples)

8 Basics of Agency Processes AS-IS Discovery & Documentation Base Understanding –Discovery –Documentation

9 Basics of Agency Process Discovery – Base Understanding – Process Discovery starts by ASKING TWO QUESTIONS: 1.What’s First? 2.What’s Next? And closely followed by: 1.What goes in? (AKA, Predecessors) 2.What happens to it? (Elements and actions of the Process) 3.What comes out? (AKA, Deliverable) THROUGHOUT THE DISCOVERY, KEEP AN EYE OPEN FOR HOW “ERRORS” ARE HANDLED.

10 Basics of Agency Process Discovery – Base Understanding – How we deal with these questions is very important. While “discovering” the answers, there will be some Challenges.

11 Basics of Agency Process Discovery – Base Understanding – Some of the Challenges 1.Getting the Right People Involved. 2.Getting the Right Information. 3.Prioritizing the Information, correctly. 4.Documenting the “As-Is” Process. 5.Validation of Documentation.

12 Basics of Agency Process Discovery – Base Understanding – 5 Levels of Processes: 1.Function(al) – Identify the Functions within your Agency. Functions are groupings of Activities. 2.Activity(ies) – Identify the Activities within the Function. Activities are groupings of Tasks. 3.Task(s) – Identify the Tasks that are within the Activities. Tasks are work packages that when grouped together create a unique task. 4.Work Packages – Work Packages are groups of Work Unites. 5.Work Units – The base unit of work. NOTE: There are other Forms which are just as valid. Functions Activities Tasks Work Packages Work Units

13 Basics of Agency Process Discovery – Base Understanding – Manual and Automated Processes

14 Basics of Agency Process Discovery – Base Understanding – Identification of “As-Is” Processes –Identify Apparent Processes: Existing Process Diagrams. Existing SOP (Standard Operation Policies) Existing Systems and Sub-Systems (Shadow systems) Key Personnel –Search for Hidden Processes: Excel spreadsheets User developed Access DB Ad hoc – Note, verbal communications, Phone call… Manual papers What stamps are used? – (Date, Approval, Denied, Posted, others) Existing manuals… – (how accurate, maintained, outdated, written in notes??) Helpful Hint: You should always be looking for Hidden Processes. 1. Many times manual portions of primarily automated processes are the hardest hidden processes to find.

15 Basics of Agency Process Discovery – Base Understanding – Identification of Decision Points (A.K.A Business Rules) Identify Apparent Decision Points: Existing Process Flow Diagrams SOP (Standard Operation Procedures) Systems and Sub-Systems Key Positions (Personnel) Search for Hidden Decision Points: Generally become visible during errors.

16 Basics of Agency Process Discovery – Base Understanding – Identification of the Bridges –How do processes interact with each other? –Identify Apparent and Hidden Bridges. Helpful Hint: You should always be looking for Hidden Bridges. Types (Basic Examples) Parallel Summing There are many others such as Timing, illustrated on the next slide.

17 Basics of Agency Process Discovery – Base Understanding – Identification of Timing items. This is a type of Bridge. Examples Delays Time to Acknowledge Time to Accept Time to Deny Time to Resolve Time to Process

18 Basics of Agency Process Discovery – Base Understanding – The Most Common Discovery Process is: –TOP DOWN and then BOTTOM UP Start with Top Down and work to the bottom. Then, turn around and work back to the top. Many times this will lead to hidden items not identified during the top down activity.

19 Basics of Agency Process Discovery – Base Understanding – Scope = What are the borders of this discovery process? Our goal is to provide process documentation that closely matches PeopleSoft delivered process documentation. The lowest level of PeopleSoft Documentation is the Task. So, for this project we need to elicit and document information to the Task level. Scope for this Discovery Project is the TASK Level within the 7 Phase II modules. SCOPE

20 Basics of Agency Process Discovery – Base Understanding – Review Functions Activities Tasks VERIFYVERIFY IDENTIFYIDENTIFY TOP Down Bottom Up Apparent Processes and Bridges Hidden Processes and Bridges SCOPE Of the 7 Phase II Modules

21 Basics of Agency Process Notation (Documentations) Documentation There are many ways to document Agency Processes. For this project we’ll closely match PS process flow by using: –PROCESS FLOW DIAGRAMS.

22 DEQ’s Spaghetti

23 TEMPLATE

24 Review Business Process Discovery & Mapping Task List 1.Identify areas of (Functions) business process that might be candidates for the Phase II deployment (Grants, External Billing, Project Tracking, Assets and Consumable Inventory). 2.Schedule discussions with those resources that are responsible for the business processes in question 1, to document details of the process. Try and uncover general execution or flow, impact to other areas of the agency, other resources involved or impacted, decision points and outputs or deliverables of the process. 3.Document any software that supports the business process. That should include any integration points with third party software (software not supported in-house). 4.Using the business process documentation developed in question 2, begin to “map out” the sequence of business process, responsible resources and decision points in a flow chart format. 5.Review the mapping done in question 4 with the resources that provided the business process details in question 2 for verification. Tweak the mapping as appropriate. This process is iterative.

25 Q&A

26 Additional Resources International Institute of Business Analysis – Google “Business Analyst Resources” –Over 173,000,000 hits…