Project Initiation
Transcript: Unit Test Approach Purpose Kick- Off meeting presentation Used during the Kick off Project plan – more datailed than the one included in the charter (reviewed following the definition of requirements) Milestone review memo – one page document (closing doc of phase – M1) Part of test and train Project Charter (Project Initiation Document) Business Case (Management Summary) Scope and objectives (functional scope; business objectives; out of scope) Infrastructure Interfaces Dependences, Assumption Project Organization – Roles and responsibilities Project approach – Project route Objectives 2 Test specification Test Plan (document define detailes of the testing process) Official project document signed by (accepted) by the project team Set the Test Scope and timeline Roles and responsibilities Type of test (positive, negative, performance, etc.) Test prerequisites (e.g. test environement, trained users) Issue management (type of issues, error handling) Acceptance criteria Transition (Go-Live) - M4 Tracability Matrix: Document connects the user requirement with system delivery spcification and user acceptance test. Acceptance Test complition report Summary report of the testing Any outstanding test issues – specify an action plan and a responsible person. To agree and document on Scope and success factors Project governance How to operate the project team Plan (timeline) Start up Kick - off meeting Deliverables 1 Deliverables 2 Objectives 1 Part of the testing process Unit testing – verify the functionality of each component Integration testing – units are succesfully integrated into one application (e.g. test of interface application) System testing UAT – by the users with support (specific test scripts) Users need to be trained to execute UAT User Acceptance Test DESIGN, BUILD and TEST (M3) To launch the project (inform users, team, affected employees) Introduce the members (to each other and to other team members etc.) Introduce the project scope Introduce the solution (vendor, supplier) Familiarize the paticipants with the methode, timeline deliverables Technical System design Systems Build Systems and Acceptance Testing Project Charter (Project Initiation Document) Operation standards of the Project team (meetings, minutes, meeting request, regular and ad-hoc meetings etc) Project communication standards Project schedule (Milestone plan) – with deliverables Risk assesment (can be a separate document as need to be maintened constantly) Integration Test Agenda (Activities ) Tartgets, Objectives Activities Deliverables Project Initiation User Acceptance Test (UAT) Gábor Németh Project Initiation (M1) Document for UAT – which describe each of the test procedure in detail: Description of the testes process Step by step instruction Detailed instruction for each step Expected results for each step Tester record the actual result and sign; mark if the step has passed. System Requirement Analysis System Delivery Specification Deliverables 3 Other deliverables (documents) Meetings to „agree” Vendor’s PM Client’s PM Representatives of the functional areas (dedicated to the project by the client) Kick - Off All project team members Subcontractors of the vendor Sponsors Representatives of other business areas possible be affected by the project (any other Stakeholder) To define (document) the „who”, „what” and „when” Specify roles, responsibilities Specify the scope, dependencies Specify the deliverables Governance, Control (how to manage, escalate) Specify the project communication, documentation Identify risks, their possibilities, impact and possible way to mitigate them (maintained through the whole project) Specify timeline (plan) User acceptance test – verifies that the system meets the previously defined user requirements Validation process where the users (end users) approve that the built solution is in line with their needs Important to reference it to the requirement (requirement doc and also system delivery spec) – tracebility matrix REQUIREMENTS ANALYSIS and SOLUTION DEFINITION - M2 Project Close (M5) Participants