Project driven organization require lifecycle management to successfully deliver value to those paying for the outcomes of the project effort. This involves processes and data for Executive processes, Enterprise Governance, Program Management Office activities, Applications that enable the delivery of value, and overarching processes and data.

1. +
Project Driven Organization Framework
Business project success means connecting the dots between strategy,
mission success, programmatic, and technical performance
management using units of measure meaningful to the decision makers,
to deliver Needed Value for planned budget on planned date.
Copyright, 2014, Niwot Ridge Consulting, L.L.C Performance-Based Management® is a Registered Trademark of Niwot Ridge Consulting L.L.C.

2. +
Strategic Portfolio Management
and Project Processes for Success†
!
† Strategic Portfolio Management, Glen B. Alleman and Steve Garfein, http://www.slideshare.net/galleman/strategic-portfolio-management

3. +
Project Driven Organizations Have
Many Moving Parts – All Needed

4. +
Connecting These Moving Parts
Starts With Their Business Function
Executive Enterprise
! Balanced
Scorecard
! Strategy
! Objectives
! Stakeholders
! Locations
! Hardware
! Servers
! Desktops
! Networks
Applications
! Databases
! Applications
All
! Business Org
! Activities
! Teams
! Responsibilities
! Roles
! Skills
! Techniques
! Data
! Networks
! Standards
! Tools
! Security
! Models
! Deliverables
! Milestones
! Earned Value
! Budget
! Risks
! Scope
! Requirements
PMO
! Governance
! Methods
! Processes
! Portfolios
! Resources
! Projects
! Costs

5. 1!
2!
3!
4!
5!
6 8
9
10
12
13
14
15
16
11
7
Managing Sustainment
These
Moving
Parts
Involves
Many
Activities.
Delivery and
Support
Development
Planning and
Organizing
Project Definition
User Capabilities
System
Requirements
Analysis and
Design
Build, Prototype,
Test, Pilot
Production
Sustainment
Each
activity
interacting
with each
other.
Performing
their
functions
and
producing
outcomes
in the
proper
order.

6. +
Project Definition
1!
Planning and Organizing
! Why is this project being initiated?
! Are those reasons defined in enough detail to
recognize they can be addressed by the
project’s deliverables?
! What problem are we trying to solve?
! Service gap
! Technical gap
! Performance gap
! New product or service demand

7. +
User Capabilities
2!
Planning and Organizing
! What capabilities do the users need to
possess to accomplish their mission or
fulfill the business case?
! What are the Measures of Effectiveness of
these capabilities to meet those goals?
! What are the units of measure of this
effectiveness?
! How is this measure connected with
project success?

8. +
System Requirements
3!
Planning and Organizing
! Eliciting requirements means bi-directional
traceability between
Capabilities and Requirements
! Establish Measures of Performance,
Technical Performance Measures, Key
Performance Parameters for the
Capabilities, traceable to requirements

9. +
User Capabilities
4!
Development
! Trace the business proposition to revenue
or other financial performance measures
! Cost estimate to achieve this financial
performance
! Statistical confidence in both value stream and
cost models
! Develop a Capabilities road map before
moving on to Requirements
! Value Stream map of Capabilities
! Cost versus Value plan to prioritize Capabilities
! Value traceable to strategy for Break Even target

10. +
System Requirements
5!
Development
! Formal Requirements Elicitation
! Bi-directional traceability to Capabilities
! Requirements Breakdown Structure
! Interdependencies define implementation
sequences
! Measures of Performance (MOP), Technical
Performance Measures (TPM), Key
Performance Parameters (KPP) defined
! Product outcomes assessed against each of
these for progress measures

11. +
Analysis and Design
6!
Development
! Trade Studies
! System architecture
! Data and Application architecture
! Security model
! Platform and Performance assessment
! Develop systems architecture model
before starting development

12. +
Build, Prototype, Test, Pilot
7!
Development
! Incremental development processes based
on architecture(s)
! Verification and validation of core
components
! Target reliability and defect assessment
! Prototype verification and validation
! Capabilities coverage
! Fit for Purpose / Fit for Use

13. +
Analysis and Design
Delivery and Support
! Verification and validation delivered
capabilities will fulfill mission or business
case
! Fit for purpose assessment
! Fit for use assessment
! Deployment plans defined to match Value
Stream Map
! Measures of Effectiveness and Performance at
each step in the VSM
8
8!

14. +
Build, Prototype, Test, and Pilot
Delivery and Support
! Early adopter support
! Feedback from use
9
9!

15. +
Production
10!
Delivery and Support
! Go Live business processes validation
! Customer support in place day one
! Monitoring of Critical Success Factors
! Stability
! Performance
! Functionality
! Rollback Strategy
! Data restoration
! Process restoration

16. +
Sustainment
11!
Delivery and Support
! Help desk
! Trained on current release
! Incident capture process traceable to code changes
! Performance monitoring
! SLA
! Security
! Incident support
! Disaster Recovery
! Incident support

17. +
User Capabilities
12!
Sustainment
! Continuous improvement of products and
services
! User groups
! Independent assessments
! Steering committee of users
! Validation of Value Stream assumptions for
Capabilities
! Updates to strategy in Capabilities Based
Planning process

18. +
Systems Requirements
13!
Sustainment
! Assessment of Fit for Use
! The ability to meet an agreed level of warranty.
! Requires suitable design, implementation, control
and maintenance.
! Assessment of Fit for Purpose
! The ability to meet an agreed level of performance
or utility.
! Capable of meeting its objectives or service levels.
! A suitable design, implementation, control and
maintenance.
! Utility + Warranty = Delivered Value

19. +
Analysis and Design
14!
Sustainment
! Assessment of architecture sustainability
! Assessment of data model for
! Security
! Maintainability
! Error recovery and restart
! Referential integrity
! Assessment of process mode for
! Scalability
! Performance stability

20. +
Build, Prototype, Test, Pilot
15!
Sustainment
! Release management for each promotion
path from Development to Pilot
! Configuration management for all
components for each promotion path from
Development to Pilot
! These controls needed to assure Pilot to
Production based on know baseline with
full traceability to all changes along the
way.

21. +
Production
16!
Sustainment
! Release to production
! Disaster recovery
! Rollback and recovery
! DR site startup
! Alternative system startup
! Performance Sustainment
! Scalability
! Demand