Page 1

JUSTIFYJUSTIFY

define and validate

REQUIRE-MENTS

define and validate

REQUIRE-MENTS

define initial

managementDOCUMENTS

define initial

managementDOCUMENTS

define INFRA-

STRUCTURE

define INFRA-

STRUCTURE

allocated maintenance

changes

management documentsinitial requirementproject infrastructureproject fundingproject charter

potential roles during this phase:

project managerproject manager

analystanalyst

subject matter expertsubject matter expert

quality assurance quality assurance engineerengineerestimator / plannerestimator / planner

process specialistprocess specialist

standards specialiststandards specialist

tools specialisttools specialist

project sponsorproject sponsor

JAD / meeting facilitatorJAD / meeting facilitator

technical writertechnical writer

infrastructure engineerinfrastructure engineer

from maintain & support phaseINITIATE PHASE

The main goal is to lay the foundation for a successful project. This is hard due to pressures by senior management and developers to start “real work” as soon as possible.

Page 2

DEFINE AND VALIDATE INITIAL REQUIREMENTS DEFINE AND VALIDATE INITIAL REQUIREMENTS

DEFINESYSTEM

FUNCTIONS

DEFINESYSTEM

FUNCTIONS

visioncommitmentreasibility studyexisting applicationsmaintenance changes

DEFINESYSTEM

SCENARIOS

DEFINESYSTEM

SCENARIOS

CREATEMODELING

CARDS

CREATEMODELING

CARDS

HOLD SESSIONS

HOLD SESSIONS

INTERVIEWUSERS

INTERVIEWUSERS

PRIORITIZEREQUIRE-

MENTS

PRIORITIZEREQUIRE-

MENTS

WALK THROUGH

PROTOTYPES

WALK THROUGH

PROTOTYPES

SIMULATESCENARIOSSIMULATE

SCENARIOS

DRAWPROCES

MAPS

DRAWPROCES

MAPS

requirementdocumentation(forms, tables, diagrams, ...)project scope

This is determining what needs to be built. Initial requirements are a foundation from which modeling can begin.

Page 3

DEFINE INITIAL MANAGEMENT DOCUMENTS DEFINE INITIAL MANAGEMENT DOCUMENTS

DEFINETASKSDEFINETASKS

reasibility studyproject infrastructureinitial requirementsproject objectives

CREATEINITIAL

SCHEDULE

CREATEINITIAL

SCHEDULE

CREATEINITIAL RISKASSESMENT

CREATEINITIAL RISKASSESMENT

CREATEINITIAL

ESTIMATE

CREATEINITIAL

ESTIMATE

CREATEINITIAL

QUALITY ASSUR. PLAN

CREATEINITIAL

QUALITY ASSUR. PLAN

DEFINEPROJECT

SCOPE

DEFINEPROJECT

SCOPEproject planrisk assessmentmaster testquality assurance plan

Purpose of this process is to initiate documents such as the project plan and project risk assessment. They must be started at the beginning of the project and then maintained throughout its life.

Page 4

JUSTIFY JUSTIFY

IDENTIFYIMPLEMEN-

TATIONALTERNATIVES

IDENTIFYIMPLEMEN-

TATIONALTERNATIVESvision

estimaterequirements documentationschedulerisk assessment

DETERMINEOPERATIONAL

FEASIBILITY

DETERMINEOPERATIONAL

FEASIBILITY

DETERMINETECHNICALFEASIBILITY

DETERMINETECHNICALFEASIBILITY

DETERMINEECONOMIC

FEASIBILITY

DETERMINEECONOMIC

FEASIBILITY

CHOOSEALTERNATIVE

CHOOSEALTERNATIVE

IDENTIFYRISKS

IDENTIFYRISKS

feasibility studyrecommendationsproject fundingrisk assessment

The purpose is to determine whether or not an application should be built. It is a reality check to determine whether or not a project makes a sense.

Page 5

DEFINE INFRASTRUCTURE DEFINE INFRASTRUCTURE

SELECTTOOLS

SELECTTOOLS

project planinitial requirementsfeasibility studyexisting infrastructure

DEFINE TEAMDEFINE TEAM

SELECT STANDARDS

ANDGUIDELINES

SELECT STANDARDS

ANDGUIDELINES

SELECT METHODO-

LOGY

SELECT METHODO-

LOGY

NEGOTIATEDELIVE-RABLES

NEGOTIATEDELIVE-RABLES

GREATEGROUP

KNOWLEDGEBASE

GREATEGROUP

KNOWLEDGEBASE team definition

(profile, skill database, ...)tools selectiontailored software processgroup knowledges

The project infrastructure is made up of the project team, the tools that they will use, and a tailored version of the software development process that the team will follow.

Page 6

INITIATEentrance conditions checklist

senior management support exists to initiate a new project

maintenance changes pertaining to previous version (if any) are identified

infrastructure is available

Page 7

INITIATEto be performed checklist

the initial requirements have been defined and validated

the initial management documents have been defined

the project has been technically, economically and operationally justified

required project infrastructure has been defined

potential reusable artifacts have been identified

project team has been identified and trained where appropriate

Page 8

INITIATEexit conditions checklist

project plan has been accepted by senior management project schedule has been accepted by senior mgmt initial risk assessment has been performed initial requirements have been accepted by senior management appropriate standards and guidelines have been identified software development process has been tailored to meet specific

needs for the project appropriate tools are prepared/installed project funding has been obtained project charter has been defined and accepted project team has been assembled lessons learned have been identified - team should take the time to

consider the processes that could be improved

INITIATE PHASE

define and validate initial requirements

Page 10

Define and validate initial req.to be performed checklist

business process models have been developed and validated user interface prototype has been developed and validated (if appropriate) technical requirements have been documented and validated operation and support requirements have been documented and validated requirements have been prioritized requests of appropriate stakeholders have been considered reusable artifacts have been identified risk assessment document has been updated decisions (both made and forgone) were documented into group memory metrics have been collected

Page 11

Define and validate initial req.exit conditions checklist

requirement documents have been validated and accepted by the user community

requirement documents have been validated and accepted by the senior management

the scope of the project has been defined and accepted - definition of the functionality that will, and will not, be implemented

INITIATE PHASE

define the initial management documents

Page 13

Define the initial mgmt documents entrance conditions checklist

the project infrastructure has been selected

the feasibility study has been at least started

the project objectives have been identified and agreed to

initial requirements have been defined

Page 14

Define the initial mgmt documents to be performed checklist

build-versus-buy decisions have been made application release schedule has been defined or updated project estimate has been developed and accepted metric plan has been developed and accepted project plan has been developed and accepted assumptions and constraints have been documented risk assessment has been started test plan has been developed and accepted reusable artifacts have been identified risk assessment document has been updated decisions (both made and forgone) were documented into group

memory metrics have been collected

Page 15

Define the initial mgmt documents exit conditions checklist

initial version of the project plan has been accepted by senior management

initial version of the project plan has been accepted by the development team

initial version of the risk assessment has been accepted by senior management

INITIATE PHASE

justify

Page 17

Justify entrance conditions checklist

development of the requirements documents has begun

development of the project plan has begun

development of the risk assessment has begun

definition of the project infrastructure has begun

access to key users, technical experts, and financial experts has been obtained

Page 18

Justify to be performed checklist

implementation alternatives were identified and considered economic feasibility of each alternative was determined cost/benefit analysis was performed technical feasibility of each alternative was determined operational feasibility of each alternative was determined alternatives were suggested to senior management for approval risk assessment document has been update decisions (both made and forgone) were documented into group memory metrics have been collected

INITIATE PHASE

define infrastructure

Page 20

Define infrastructure entrance conditions checklist

development of the initial requirements has begun

development of the project plan has begun

development of the feasibility study has begun

existing infrastructure is available

Page 21

Define infrastructure to be performed checklist

project team has been defined skill assessment for each team member has been defined required training for each member has been defined and performed project skill matrix was developed potential subcontractors have been contracted project deliverables have been negotiated with senior management and

agreed to group memory has been organized shared library of books etc. is available reusable artifacts have been identified risk assessment document has been updated decisions (both made and forgone) were documented into group memory metrics have been collected

Page 22

Define infrastructure exit conditions checklist

the team has been accepted by senior management

the tailored software process has been accepted by the team members

the tailored software process has been accepted by senior management

group memory has been initiated