ProPath - Performa.US

ProPath
OED
ProPath
Getting Started
Legend
Project Life Cycle Processes
Life Cycle Integration
Release Notes
Change Request
Product Development Life Cycle Processes
Business Analysis (BUS)
Requirements Elaboration (RQE)
Project Planning (PRP)
Product Architecture (ARC)
Project Launch (PRL)
Architecture Evaluation (AEV)
Project Closure (PRC)
Product Design (DES)
Project Monitoring and Control (PMC)
Design Evaluation (DEV)
Restart Paused Projects (RES)
Test Preparation (TST)
Start Subsequent Increment (SSI)
Product Build (BLD)
Project Shut Down (PSD)
Product Documentation (DOC)
Test and Certification (TAC)
Release Management (REL)
Product Support (SUP)
Segment Architecture (SAM)
ProPath R05-U00
Release 5
September 2010
ProPath Life Cycle
Integration
Concept Definition Concept Planning
Development
Implementation
Operations &
Maintenance
Closeout
Product Support
Project Closure
Project Monitoring and Control
Project Planning
Project Launch
Requirements Elaboration
Product
Design
Design
Evaluation
Product
Architecture
Architecture Evaluation
Product Build
Test Preparation
Test and
Certification
Release Management
Product Documentation
back
ProPath R05-U00
September 2010
ProPath
OED
ProPath
Legend
home
General Navigation
Navigate to process map
Navigate to activity details
Navigate within a process map
Click to launch artifact template
Navigate back one level/page
Click to launch standards/guides
Navigate to next level/page
Reviews Specific Navigation
ProPath R05-U00
Common Process Map Icons
P
Navigate to Peer Review details
Process Map Start
F
Navigate to Formal Review details
Activity Wait/Merge
Q
Navigate to Process Quality Gate Review details
Process Map End
M
Navigate to Go / No Go Review (Milestone) details
September 2010
ProPath
OED
ProPath
Release Notes
home
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.
ProPath R05-U00
more
September 2010
ProPath
OED
ProPath
home
Release Notes
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.
back
ProPath R05-U00
more
September 2010
ProPath
OED
ProPath
home
Release Notes
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
back
ProPath R05-U00
more
September 2010
ProPath
OED
ProPath
home
Release Notes
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.
back
ProPath R05-U00
more
September 2010
ProPath
OED
ProPath
home
Release Notes
Ÿ 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.
back
ProPath R05-U00
more
September 2010
ProPath
OED
ProPath
home
Release Notes
Ÿ 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.
back
ProPath R05-U00
more
September 2010
ProPath
OED
ProPath
Release Notes
home
Ÿ 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 Model
Ÿ Executable Prototype
ProPath R05-U00
back
September 2010
Business Analysis: Create Business Requirements Document
home
Description
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.
Artifacts
Used
Artifacts
Created
Responsible
Role
Tools
Department Request
Business Requirements Document
Business Analyst
IBM Rational RequisitePro ®
Standards
Requirement Level Guide
More Info....
ProPath R05-U00
September 2010