INITIATE PHASE

1. quality assurance engineer tools specialist process specialist estimator / planner subject matter expert analyst standards specialist project sponsor JAD / meeting facilitator technical writer infrastructure engineer project manager allocated maintenance changes 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. JUSTIFY define and validateREQUIRE-MENTS management documentsinitial requirementproject infrastructureproject fundingproject charter define initialmanagementDOCUMENTS define INFRA-STRUCTURE potential roles during this phase:

2. This is determining what needs to be built. Initial requirements are a foundation from which modeling can begin. DEFINE AND VALIDATE INITIAL REQUIREMENTS DEFINESYSTEMFUNCTIONS DEFINESYSTEMSCENARIOS DRAWPROCESMAPS visioncommitmentreasibility studyexisting applicationsmaintenance changes requirement documentation(forms, tables, diagrams, ...)project scope HOLD SESSIONS CREATEMODELINGCARDS PRIORITIZEREQUIRE-MENTS INTERVIEWUSERS SIMULATESCENARIOS WALK THROUGHPROTOTYPES

3. 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. DEFINE INITIAL MANAGEMENT DOCUMENTS DEFINETASKS CREATEINITIALSCHEDULE DEFINEPROJECTSCOPE reasibility studyproject infrastructureinitial requirementsproject objectives project planrisk assessmentmaster testquality assurance plan CREATEINITIALESTIMATE CREATEINITIAL RISKASSESMENT CREATEINITIAL QUALITY ASSUR. PLAN

4. 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. JUSTIFY IDENTIFYIMPLEMEN-TATIONALTERNATIVES DETERMINEOPERATIONALFEASIBILITY IDENTIFYRISKS visionestimaterequirements documentationschedulerisk assessment feasibility studyrecommendationsproject fundingrisk assessment DETERMINEECONOMICFEASIBILITY DETERMINETECHNICALFEASIBILITY CHOOSEALTERNATIVE

5. 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. DEFINE INFRASTRUCTURE SELECTTOOLS DEFINE TEAM GREATEGROUPKNOWLEDGEBASE project planinitial requirementsfeasibility studyexisting infrastructure team definition(profile, skill database, ...)tools selectiontailored software processgroup knowledges SELECT METHODO-LOGY SELECT STANDARDSANDGUIDELINES NEGOTIATEDELIVE-RABLES

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

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

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

9. INITIATE PHASE define and validate initial requirements

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

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

12. INITIATE PHASE define the initial management documents

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

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

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

16. INITIATE PHASE justify

17. Justifyentrance 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

18. Justifyto 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

19. INITIATE PHASE define infrastructure

20. Define infrastructureentrance 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

21. Define infrastructureto 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

22. Define infrastructureexit 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