OED ProPath ProPath - Performa.US
Transcript of OED ProPath ProPath - Performa.US
ProPath R05-U00 September 2010
OED ProPath
Product Design (DES)
Design Evaluation (DEV)
Start Subsequent Increment (SSI)
Restart Paused Projects (RES)
Project Shut Down (PSD)
Release Notes Change RequestLife Cycle Integration
Requirements Elaboration (RQE)
Project Launch (PRL)
Project Planning (PRP)
Project Life Cycle Processes
Project Monitoring and Control (PMC)
Architecture Evaluation (AEV)
Test Preparation (TST)
Product Build (BLD)
Product Documentation (DOC)
Release Management (REL)
Product Support (SUP)
Test and Certification (TAC)
Project Closure (PRC)
Product Development Life Cycle Processes
Product Architecture (ARC)
Release 5
Segment Architecture (SAM)
Getting Started Legend
ProPath
Business Analysis (BUS)
ProPath R05-U00 September 2010
Concept Definition Concept Planning Development Implementation Operations & Maintenance Closeout
Project Monitoring and Control
Project Planning Project Launch
Requirements Elaboration
Product Design
Product Support
Design Evaluation
Product Architecture
Architecture Evaluation
Product Build
Test Preparation Test and Certification
Project Closure
Release Management
back
ProPath Life Cycle Integration
Product Documentation
ProPath R05-U00 September 2010
Process Map End
Navigate to Go / No Go Review (Milestone) details
Process Map Start
Activity Wait/Merge
Navigate to process map
Click to launch artifact template
Click to launch standards/guides
Navigate within a process map
Navigate to next level/page
Navigate back one level/page
General Navigation
Reviews Specific Navigation
Navigate to Peer Review details
Navigate to Formal Review details
Navigate to Process Quality Gate Review details
Common Process Map Icons
Legend
OED ProPathhome
P
F
Q
M
ProPath
Navigate to activity details
ProPath R05-U00 September 2010
Release Notes
OED ProPath
Release 5 Overview:
The latest release of ProPath (Release 5) of ProPath expands the scope of the system development processes adding six new processes (below), provides for continued support of PMAS (including revision to support the latest release of the PMAS Guide Version 2.0) and provides significant revision to existing process maps and new process maps alike to promote greater usability and clarity to assist Project Teams with PMAS compliance.
Organizational Changes:
Numerous changes have been applied to ProPath to reflect recent organizational and positional changes. ProPath has removed the Office of Enterprise Development (OED) branding to reflect serving the larger OI&T organization, but continues to fully serve OED Program and Project Management. ProPath reflects the move of ESPPP to Architecture, Strategy and Design (ASD) and introduces the Enterprise Architecture (EA) group that is part of ASD.
home
more
ProPath
ProPath R05-U00 September 2010
Release Notes
OED ProPath
Home Page:
The ProPath Home Page file has been revised to include better navigation and pop-up information for its process maps to facilitate greater ease of use. Among the changes are:
• The addition of incorporating the entire process map name as an active link
A major improvement to the homepage has been the introduction of the System Development Life Cycle (SDLC) view for which the ProPath processes have been overlaid. This visual model attempts to dispel common misconceptions that ProPath supports only a ‘waterfall’ SDLC methodology. By asserting the ability to apply each process concurrently and illustrating how processes extend across multiple phases of the SDLC, ProPath establishes its full capability and flexibility to support Sequential, Incremental, Iterative and Agile methodologies.
A revised navigation bar that provides ease of access to the ProPath “Getting Started” presentation, the legend, the life cycle integration, release notes and ProPath change request.
�
�
home
back more
ProPath
ProPath R05-U00 September 2010
Release Notes
OED ProPath
Artifact & Process Reviews:
Activities associated with the Peer Review, Formal Review, Process Quality Gate Review, and Go No Go Reviews have been simplified through activity consolidation and introduction of the ProPath Reviews Guide to assist the Project Teams to in performing various artifact and process reviews. This significantly reduces the number of activities that must be navigated through to perform these reviews. You should review the new ProPath Reviews Guide to acquaint yourself with these changes. This change is reflected in the following process maps:
• Project Planning• Product Build• Test Preparation• Release Management• Product Documentation• Architecture Evaluation• Design Evaluation• Test & Certification
home
back more
ProPath
ProPath R05-U00 September 2010
Release Notes
OED ProPath
New Process Maps:
The following new process maps have been introduced into ProPath in Release 5:
Project Shut Down (PSD) – This new process ensures that the shutdown of a project is properly coordinated with all stakeholders, fully documented for future reference and audit traceability, and performed in a controlled environment through a documented process.
Segment Architecture (SAM) - This new process is an independent flow that is used only by the Architecture, Strategy and Design (ASD) group. By having a separate process it allows the ASD group to refine their flow and determine where parts of Segment Architecture will fit into existing processes.
Business Analysis (BUS) – This process, which consists of a singular activity to create the Business Requirements Document (new template as well) defines the activities that occur outside of OI&T involving the various business lines (VHA, VBA, Memorial, Corporate) that precede the actions of the Project Planning process. This process will be expanded in the future as more Business Analytical activities are defined and captured within ProPath.
Restart Paused Projects (RES) – This process expands on the guidance provided in the PMAS guide to provide clear plan of action and deliverables to enable project teams to restart IT projects that have been ‘paused’ for various reasons.
�
�
�
�
home
back more
ProPath
ProPath R05-U00 September 2010
Release Notes
OED ProPath
Start Subsequent Increment (SSI) - This process (similar to project start) defines the plan of action and deliverables needed to plan and obtain approval to commence subsequent increments in a multiple increment delivery project.
Modifications to Existing Process Maps:
Project Planning (PRP) - Updated to align with the new PMAS guide (v.2) to include:Modification of several artifact templates (including required signatories as defined by PMAS)New activity called “Create Budget Execution Performance Deliverables and new PMAS required artifact “Outcome Statement” added.New Integrated Project Team guide to assist project teams in standing up a Project IPT.Changed activity “Update Organizational Breakdown Structure (OBS) to “Update Enterprise Project Structure (EPS). The EPS artifact will now be updated in lieu of the OBS artifact. New activity called “Perform Requirements-Based Estimation” and Function Point Estimate Workbook artifact deliverable added for the benefit of those projects looking to implement Function Point analysis as a means for project estimation. The activity of “Formal Review of the System Design Document (SDD)” added to ensure Integrated Project Team approval of the SDD.The activity “Create System Design Document” has been enhanced to add greater visibility to VA IT architecture and design frameworks.
�
���
��
�
�
�
home
back more
ProPath
ProPath R05-U00 September 2010
Release Notes
OED ProPath
Project Monitoring & Control (PMC) - Project Monitoring and Control and Monthly Reporting have been merged into one process. Included in the process consolidation are:
Addition of the Red Flag Procedure (as identified by the PMAS guide) Addition of new monthly PMAS reporting requirements as defined in the OI&T Monthly Performance Reports
Release Management (REL)Updated the Deployment Plan artifact adding signature page to facilitate approval during Formal Review by the Project IPT. Reorganized the “Plan Release Deployment” sub-process part of Release Management to facilitate greater ease of use and greater clarity on responsible role for activities “Conduct Product Support Review” and “Conduct EIE Release Office Review” with the role of EIE Release Officer. Moved the Go No Go Testing and Release Checklist from Artifact Used to the Standards section of applicable activities and provided the link allowing users greater access and visibility to said artifact.Updated version of the Product Support Primavera (TeamPlay) Guide added.
Product Support (SUP) - Updated version of the Product Support Primavera (TeamPlay) Guide added.
�
��
��
�
�
�
�
home
back more
ProPath
ProPath R05-U00 September 2010
Release Notes
OED ProPath
Test and Certification (TAC) - “Perform OED Testing Service Testing” is now referred to as “Independent Testing” with associated artifacts and deliverables referred to as “Independent Test Plan” and “Independent Testing Findings Report” reflecting a broader range of service to be provided by the OED Testing Service.
Project Closure (PRC) - Additional information to support the final Function Point Count activity as part of Project Closure has been added.
Monthly Reporting Templates (RPM)Deprecated and consolidated with Project Monitoring and Control (PMC)The OI&T monthly performances reports as mandated by PMAS are now defined in PMC
Design Evaluation (DEV) - New activity added that defines the formal review of the following design documents:
Enterprise Data ModelExecutable Prototype
�
�
���
�
��
home
back
ProPath
ProPath R05-U00 September 2010
Description
Artifacts Used
Artifacts Created
Responsible Role
Tools
Standards
More Info....
Business Analysis: Create Business Requirements Document
Business Analyst
IBM Rational RequisitePro ®
The Business Analyst creates the Business Requirements Document (BRD) to capture and describe the business needs of the customer/business owner. The BRD provides insight into the current state and proposed business area or process, identifies stakeholders and profiles primary and secondary user communities. It identifies what capabilities the stakeholders and the target users need and why these needs exist, providing a focused overview of the request requirements, constraints, and Information Technology (IT) options considered. This document does not state the development methodology.
Business requirements contained within the BRD are documented at a maturity level of 2 (at a minimum). Level 2 requirements are sufficient to support IT Project Planning. Refer to the Requirement Level Guide below for information on requirements maturity levels.
Department Request
home
Business Requirements Document
Requirement Level Guide