Define with the Customer the Delivery Instructions of each one of the Deliverables specified in the Statement of Work. Identify the specific Tasks to be performed in order to produce the Deliverables and their Software Components identified in the Statement of Work. Include Tasks in the SI process along with verification, validation and reviews with Customer and Work Team Tasks to assure the quality of work products. Identify the Tasks to perform the Delivery Instructions. Document the Tasks. Review the Statement of Work Characteristics of the VSE • Application domain • Typical project size (e.g. person-months) • Design method • Programming language • Other characteristics ( e.g. country) Context of the VSE (i.e. readiness to conduct pilot project) • The pilot can be executed in a relatively short time frame with relatively limited resources. • The pilot should not be on a critical path, such that failure has a significant adverse impact on the VSE. • The pilot should have a reasonable chance to succeed • The owner/director is willing to commit resources • The pilot will be conducted during a low stress period • A problem/opportunity has been identified • Practitioners of the VSE see a need for the technology to be piloted • The VSE demonstrates a willingness to experiment Discuss, with the management of the VSE, the problem to be solved or the improvement desired. An assessment could be performed using the Self-Assessment Deployment Package, Discuss the goal(s) of the pilot project, Record the goal(s). Benefits e.g. contribution toward meeting the organization’s objectives e.g. reduce cycle time (actual), redundant work, rework Cost (e.g. effort) of pilot for the VSE The following elements should be identified: • Name of the Project Manager selected for the pilot project. • Approximate date of beginning and ending of the pilot project • Technology to be piloted • Roles and responsibilities of participants to the pilot project Define the questions to be answered by the execution of the pilot project e.g. additional effort required to adopt the technology to pilot e.g. suitability of the technology to certain type of projects e.g. technology adoption by project team Select, with the management of a VSE, the project which will pilot the technology, suited to answer the questions previously defined Identify when the pilot could be conducted Discuss what resources are needed Identify and evaluate the risks - projects with too low or too high risk levels may lead to wrong conclusions Select, with the management of a VSE, a technology (e.g. a deployment package) to pilot. It could be a subset of a deployment package if the VSE cannot implement the complete content of a deployment package. If requested by the Management of the VSE, sign the confidentiality agreement (see the Template section of this document) or an agreement provided by the management of the VSE. The purpose of the Project Management process is to establish and carry out in a systematic way the Tasks of the software implementation project, which allows complying with the project’s Objectives in the expected quality, time and costs. The purpose of the Software Implementation process is the systematic performance of the analysis, design, construction, integration and tests activities for new or modified software products according to the specified requirements. The pilot project coordinator and the management of the VSE assess the opportunity to conduct a pilot project. If the conclusion of the assessment is positive, the commitment of VSE’s management to conduct the pilot project is obtained. This task is performed to ensure that the pilot project coordinator and the management of the VSE understand what has to be done to conduct a successful pilot project. The management of the VSE understand the effort required and the roles of the participants to the pilot project. Goals for the pilot are finalized, evaluation guidelines are identified and a pilot project plan is developed. The commitments of VSE’s management and the participants to the pilot project to the plan are obtained. To ensure that the pilot project is linked to a problem to be solved or improvement needed. To conduct the pilot according to the plan and, if unexpected events happened, to manage risks and adjust the plan accordingly Pilot project execution main challenge is to achieve two eventually conflicting goals: project goal and pilot goal. Pilot project success requires achieving both goals and associated risks have to be managed. To evaluate the results of the pilot project and to improve future pilots and Deployment Packages. The pilot project is evaluated to provide to the management of the VSE information to proceed or not proceed (i.e. go/no-go decision) with the deployment of the technology, to improve future pilots and provide recommendations to improve the technology piloted. The primary objective of the Project Planning Process is to produce and communicate effective and workable project plans. This process determines the scope of the project management and technical activities, identifies process outputs, project tasks and deliverables, establishes schedules for project task conduct, including achievement criteria, and required resources to accomplish project tasks. Whatever the size of the project, good planning is essential if it is to succeed. Effective software project management depends on thoroughly planning the progress of a project. A plan formulated at the start of a project should act as a driver for the project. The initial plan should be the best possible plan given the available information. It should evolve as the project progresses and better information becomes available. To implement the actual work tasks of the project in accordance with the project plan. The purpose of the Project Assessment and Control is to determine the status of the project and ensure that the project performs according to plans and schedules, within projected budgets and it satisfies technical objectives. This process includes redirecting the project activities, as appropriate, to correct identified deviations and variations from other project management or technical processes. Redirection may include re-planning as appropriate. A project plan is a document that can be used to guide the execution of a project. Unless the actual performance of the execution of the project is tracked against the plan, the plan will have limited value beyond the initiation of the project. Project Closure typically involves releasing the final deliverables to the customer, handing over project documentation to the business, terminating supplier contracts, releasing project resources and communicating project closure to all stakeholders. Often a final step is to undertake a Post Implementation Review (post-mortem) to identify the level of project success and note any lessons learned for future projects. reviewed reviewed reviewed reviewed reviewed verified verified accepted initiated evaluated updated updated evaluated accepted updated updated recovered evaluated evaluated evaluated initiated accepted delivered updated accepted reviewed reviewed reviewed verified initiated verified validated preliminary validated preliminary, verified initiated validated validated, baselined preliminary, verified preliminary, verified, baselined validated, baselined validated, baselined verified initiated verified validated, baselined validated, baselined validated, baselined validated, baselined verified, baselined verified updated verified verified, baselined verified verified verified, baselined verified verified,baselined verified, baselined verified, baselined unit tested unit tested corrected corrected verified, baselined updated updated updated baselined corrected corrected baselined verified verified corrected, baselined updated, baselined tested tested corrected defects eliminated updated, baselined updated, baselined updated corrected tested verified tested preliminary tested tested verified baselined tested, baselined verified, baselined baselined verified, baselined updated, baselined verified verified, baselined delivered Baselined