Phase/Activity Task/Subtasks Potential
Note: The feasibility study may be a project by itself. Its results provide the basis for determining
whether a project should be chartered to deliver the product or service solution. Exceptions to this rule
may occur when management has determined that the feasibility study will be a phase in a project to be
Note: The degree of detail required will vary from project to project. It should be decided upon when
the feasibility study project is chartered.
The following activities, tasks and deliverables should be reviewed for each project on a case-by-case
basis. Projects may utilize this model and adapt or tailor to the specific needs of the project. This means
that not all activities and tasks are necessary for every project, and that additional activities and tasks
may need to be included.
Note: The numbering starts at “3” to enable integration into the project management lifecycle
“Execution Phase” which is the third of five project phases.
3.1 Phase - Feasibility Study
3.1.1 Define Mission Review the projects product description and Product Description
Statement confirm the principal business objectives of
the proposed project.
Obtain agreement on the level of detail
required for study, expectations for
feasibility report format, formulas, and
criteria to be used.
Determine if the project must follow the
DAS requirements for cost benefit analysis
and reporting formats.
3.1.2 Define Study Boundary Identify the business area(s) that are to be Context Diagram
Identify critical business issues.
Critical Business Issues
Identify business functions.
Identify the data subjects that are relevant to Relationship Diagram
the business area.
Existing data dictionary
Identify sources and recipients of data.
3.1.3 Identify Key Identify users, sponsors, responsible List of participants
Participants application development managers,
managers from other technology areas (e.g.,
computer operations), and vendors.
3.1.4 Research & Analyze Evaluate the existing system(s) to determine Description of existing
Existing Systems strengths and weaknesses. system(s)
3.1.5.Determine the Impact Identify which existing development efforts Statement of impact on
on Existing Systems are affecting the area under study. existing efforts
Phase/Activity Task/Subtasks Potential
3.1.6.Define Hi-Level Define data requirements by extending the Data Dictionary (data
Business Requirements model started in Activity 3.1.2 to include element descriptions for
data element and data flow definitions. identified attributes, data
flow definitions, and
Define business functions (extend the data entity definitions)
definition of functions identified in Activity
3.1.2 above) and their inputs and outputs. Function hierarchy
diagram or an equivalent
Define constraints (delivery time/target representation of the
dates, volumes and frequency of use, budget business functions
restrictions, technological limitations, etc.).
Data Flow diagrams (if
Note: The results of this activity should be needed)
used in the development project(s) if they
are authorized. Function Descriptions
Statement of constraints
3.1.7 Recommend Systems Identify design alternatives; including Design alternative
Solution acquisition options (this requires high-level descriptions
designs and investigation of acquisition
options) with the major functional areas of Cost/Benefits Analysis
OIS, i.e. CRM, NDS, ISE, T&S, PMO.
Determine cost and benefit estimates for rationale (a section of the
each alternative. Feasibility Report)
Identify, justify and seek an agreement
decision with OIS cross-sections for a
3.1.8 Describe Development Identify product delivery phases. Development strategy
Strategy description (choice of
Describe the development approach (e.g., the lifecycle model(s) to
package acquisition, rapid application be used to implement the
development, traditional development, solution(s))
enhancement of existing systems, etc.).
Prepare an initial (high-level) project plan,
including an activity list, statement of
resource requirements, estimate, and
3.1.9 Prepare and submit Document findings in a report to the Feasibility Report
Feasibility Report Steering Committee and/or Executive Staff