1. Project Initiation Phase

1. 1. Project Initiation Phase 5. Development Phase and Testing Project Definition Validation Master Plan (VP) Traceability Matrix (update test column) Test Report (TR) User and System manuals, training, guidelines System and software IQ’s (Production) 2. Requirement Phase Validation Report (VR) Testing System/OQ, Integration, User Acceptance Test cases (TC) (pre-approved and executed) Requirements (System and Functional) Traceability Matrix 3. Analysis Phase PhaseitionPhase Updated or created IT SOPs Traceability Matrix (update solution column) System Design Specification (SDS) Technology Architecture System and software IQ’s 6. Implementation Phase PPQ Transition Plan 4. Design Phase Site SOPs Technical System Design Test Plan (TP) Traceability Matrix (update solution column) Post Live Change Control procedure Planned Site Q review of each deliverable will occur as a consequence of project milestones. Deliverable archiving Delivered System Retirement Strategy

2. Validation Packet  How is it done? • Each packet is organized based on the uniqueness of the project. The basic deliverables really don’t change that much. Remember – Validation packet is based on a proven model based on an evolving IO/IA viewpoint  years of expertise has gone into this. . . • The basic 6-phase SDLC approach is the structure. Makes little difference if SDLC or something else is the structure – project methodologies are basically the same . . . • E-room and/or any team-accessed file structure solution is the working repository of documentation activity – that occur as a function of milestone project. A key element of validation packet is the fact that quality review is an active function - “Green Light”. • Project team members are assigned key deliverables and off we go . . . • The tracking of deliverables becomes a self-fulfilling prophecy of validated deliverables. No duplication of documentation effort – no waste of time in determining what is needed and how to document it.

3. What is Milestone Tracking? • Integrates Validation Packet deliverables into normal project tracking. Positions key Validation Packet deliverables as milestone events – which they are. • Microsoft Project should serve the project team not the other way around . . . Meaning often, the administration of detailed project plans via Microsoft Project, requires unnecessary overhead and provides little value. • Key characteristics of Milestone Tracking • It assumes accountability by the professional project team. The details of how to meet a milestone is the responsibly for those that receive the assignment. • It is brief . . . • Resource balancing is de-emphasized. For example, milestone tracking is not interested in the fact that project team members have 20% of their time allocated towards meetings or other projects. So – start dates and durations are not intended to be accurate or tracked • But due dates and assignments are tracked. Weekly tracking is the critical element.

4. What is Milestone Tracking? • Milestone tracking uses a rolling 2-4 week cycle. • Changes in dates and even changes within the milestones themselves are allowed outside the rolling 4 week cycle • However, changes in deliverables and due dates within the rolling 2-3 week cycle should be avoided.

5. Why Is It Successful? • Is simple with little administrative overhead. • Is flexible assuming it is tracked • Is empowering to team members which is a key component • Is a communication tool to management and other teams • Is proven but requires a strong and credible leader