Page 1 JUSTIFY define and validate REQUIRE- MENTS define initial management DOCUMENTS define INFRA- STRUCTURE allocated maintenance changes management documents initial requirement project infrastructure project funding project charter potential roles during this phase: project manager project manager analyst analyst subject matter expert subject matter expert quality assurance quality assurance engineer engineer estimator / planner estimator / planner process specialist process specialist standards specialist standards specialist tools specialist tools specialist project sponsor project sponsor JAD / meeting JAD / meeting facilitator facilitator technical writer technical writer infrastructure infrastructure engineer engineer from maintain & support phase INITIATE 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.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
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
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
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.
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
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