Special Report - "Five Resolvable Program Management Issues".

1. Five Resolvable Program
Management Issues
Jim Todd
Presenter
Central Solution(s)
Special Report Presentation
23 February, 2011
Applied: Knowledge and Thoroughness
(James R. Todd Consulting – jrtodd@pacbell.net)

2. Executive Summary
• The Title:
 “Five Resolvable Program Management Issues”
• The Sub Title:
 How You Can Use Systems Engineering Methods -
 To Resolve!!
• Requirements Management.
• Proposal Writing.
• Risk Mitigation.
• Verification & Validation.
• Management Tools.
 Besetting Cost / Schedule Drivers

3. What We’ll Cover Today
• Review Central Solution – “Special Report”.
• Overview of full report.
 “Five Resolvable Program Management Issues”.
• Illustration of all necessary report content.
• Statement of all five principles.
• Focus on first of the five principles.
• Elaborate the first principle with:
 PIQ – {Principle, Illustration, Question}.
 Highlight use of Illustration / Table.
• Questions and answers from the teams.

4. Besetting Aerospace & Defense
Industry Problems!
• Requirements • Verification &
Management. Validation.
• Proposal Writing. • Use of Appropriate
Tools.
• Risk Management.

5. Principles
• 1. Continuous diligent requirements
management activities:
 Reduces requirements change rate –
 On program customer approved
requirements:
 Resulting in:
• Reduced program costs.
• Higher award fees on
contracts.

6. Principles (Continued)
• 2. Incorporation of program oriented
process and cost improvements:
 Based on elements as -
 Change sensitive requirements
management:
 Resulting in:
 Compelling technical &
management claims -
• In competitive proposal responses to
requests for proposals.

7. Principles (Continued)
• 3. Establishment and utilization of risk
management boards:
 Reduces cost / schedule impacts -
 For emerging issues.

8. Principles (Continued)
• 4. Utilization of change sensitive
requirements management
methodologies:
 Reduces cost / schedule impacts –
• In conducting Verification & Validation
(V&V).
 On legacy and emerging technology
programs.

9. Principles (Continued)
• 5. Creation of best-practices –
 Oriented systems engineering tools
committees:
 Reduces the complexity of program
management –
• From concept development -
 Through -
• Verification and Validation (V&V) -
 Program phases.

10. Benefits Summary
• Reduced program costs.
• Higher award fees on contracts.
• Process Improvements.
• Cost / Schedule Improvements.
• Realized Proposal Competitive
Advantages – Auditable Claims.
• Reduces Complexity – During V&V.
• Ensures Best- Practices with Tools.

11. Benefits: Proven with Aerospace & Defense
Programs
• Major Organization Needs of Clients:
 Leadership.
 Management.
 Cost / Schedule.
 Facilities.
 Risk.

12. The Sea-Based X-Band
Radar Underway (SBX-1)
The Sea-Based X-Band Radar is
the integral system onboard the
SBX-1 Vessel.
“Sea-Based X-Band Radar (SBX)
is floating self-propelled, mobile
radar station designed to
operate in high winds and
heavy seas. It is part of the U.S.
Defense Department Ballistic
Missile Defense System.”
Text and photo credit:
http://en.wikipedia.org/wiki/SBX-1

13. Principle #1 – Details of {PIQ}
• Principle #1. Continuous diligent
requirements management
activities:
 Reduces requirements change rate –
 On program customer approved
requirements:
 Resulting in:
• Reduced program costs.
• Higher award fees on
contracts.

14. Illustration #1 – Details of {PIQ}
• Illustration #1.
 Writing Better Requirements.
 Writing Pitfalls to Avoid.

15. Illustration #1:
Writing Better
Requirements. • Characteristics of a Good
“Requirements can be a Requirement.
powerful instrument to make  Each individual requirement should
design decisions and manage
your product, but only if they are
be:
well written.” • Correct.
Adapted from QSS – Quality Systems & Software, 1999.
• Complete.
• Clear.
• Consistent.
• Verifiable.
• Traceable.
• Feasible.
• Modular.
• Design Independent.

16. Illustration #1
(continued):
Writing Pitfalls to Avoid. • Top Pitfalls in Writing
“Requirements can be a Requirements.
powerful instrument to make • Ambiguity.
design decisions and manage
your product, but only if they are • Multiple requirements.
well written.” • Let-out or escape clauses.
Adapted from QSS – Quality Systems & Software, 1999. • Rambling.
• Mixing different kinds of
requirement.
• Speculation.
• Vague terms.
• Suggestions or possibilities.
• Wishful thinking.

17. Illustration #1
(continued):
Cost / Schedule
Impacts.
Continuous
diligent
requirements
management
activities have a
positive impact on
cost / schedule.

18. Question #1 – Details of {PIQ}
• Question #1.

19. About the Author.
This graphic depicts the
Special Report – “About
the Author” section.
This has compelling
content:
-Brief biography.
-Appropriate
accomplishments.
-Call to action!!
-Contact information.
-Career theme.

20. Questions and Answers
Q&A :
Your questions answered:
 by the Central Solutions
Team Members.

21. For Continued Transition Support
Contact your Central
Solutions Experts –
Jim Todd
jrtodd@pacbell.net