Process Consultant


How Much Process Do You Need?

How much process is enough? Too little process increases endeavor risk because inadequate process can lead to inadequate quality and the inability to handle the inherent complexity of a modern endeavor. Too much process can unnecessarily increase endeavor cost and schedule. Selecting the correct amount of process including the appropriate amount of rigor and formality can often be a difficult decision that is made even more difficult because of the subjective preferences of individual members of the development staff.

Please answer all of the following questions, which will enable our automated process consultant to help you objectively determine the appropriate size (completeness) and discipline (rigor) that your specific process will need based on the characteristics of your application, endeavor, and organization as well as any business constraints involving your endeavor’s process.

Application Characteristics

Application
Characteristics
Associated
Values
Application Size
(# of Requirements)
Huge
Large
Medium
Small
Trivial
Application Complexity Huge
Large
Medium
Small
Trivial
Requirements Stability Very Stable
Relatively Stable
Volatile
Very Volatile
Business Criticality Business Critical
Very Important
Moderately Important
Not Very Important
Irrelevant
Safety Criticality Safety Critical
Safety Related
Not Safety Related

Endeavor Characteristics

Endeavor
Characteristics
Associated
Values
Contracting Formally Specified and Legally Binding
Informally Specified
No Contract (Internal Development)
Endeavor Schedule Very Generous (> 150% estimated)
Generous (< 150% estimated)
Reasonable (< 125% estimated)
Short (< 100% estimated)
Very Short (< 75% estimated)
Extremely Short (< 50% estimated)
Endeavor Type Enterprise Wide Process
Program of Projects
Single Project
Process Scope Entire Life Cycle Process
Development Cycle Process
Single Phase (e.g., Initiation, Construction, or Usage)
Single Discipline Process (e.g., Requirements Engineering)
Single Team Process
Single Person Process

Organizational Characteristics

Organizational
Characteristics
Associated
Values
Developer Culture Laggard
Late Majority
Early Majority
Early Adopter
Innovator
Management Culture Laggard
Late Majority
Early Majority
Early Adopter
Innovator
Organizational Separation Separate Prime Contractor and Subcontractors
Separate Customer and Development Organizations
Customer and Development Organization Same
Staff Expertise and Skill Level High
Medium
Low
Staff Localization Geographically Distributed
Locally Distributed
Co-located

Process Constraints

Process
Constraints
Associated
Values
Required Cycle Must Use Waterfall Development Cycle
Must Use Long Iterative Increments
Must Use Short Iterative Increments
No Constraint
Required Process Must Use Waterfall Development Cycle
Must Use RUP
Must Be Agile
Must Use XP
No Constraint

Disclaimer

The goal of this process consultant is only to give very rough advice as to the general level of recommended discipline and size of a project-specific process based on answers provided to a set of questions. There is no warranty, neither expressed nor implied, that the resulting recommendation will be appropriate for any specific project. The recommendation is not proscriptive but informational. Users of this process consultant use its recommendations at their own risk.