Upload
irving-fax
View
218
Download
1
Embed Size (px)
Citation preview
Domino.Doc Project Overview
Project Rollout/Schedule Preview
Eastman Kodak Health Imaging
Doug Smith
Project Goals
Corporate Deployment of Lotus Domino for DHF/21CFR11 Submissions
Phase One - Migration of Design History Files to Louts Notes
Phase Two – define next component to be rolled out, electronic signature
General Description
Identify the desired forms and workflow for sites.
Create migration path for existing DHF database.
Training and User Documentation
FOR MORE INFO...
Contact: Jeff B.
Core Technology Used
Identify new technology being used– Why existing system needs upgrade
Quality Standards supported– Connect to Quality Section Number
Other technology options evaluated– Microsoft Content Server
Team/Resources
Assumptions about resources allocated to this project:– 4 Allendale R&D resources – 1 Dallas R&D resources– 4 Regional site liaisons– Technical support & outside services
FOR MORE INFO...
Contact: Doug S.
Procedures
Highlight any procedural differences from regular projects of this type
Discuss how user training and documentation is provided
First and Second level technical support tiers
FOR MORE INFO...
Contact: Rolando S.
High Level Milestones
Review high-level milestones:
FOR MORE INFO...
Visit the Project Database on Notes
Current Status
Gate zero scheduled 3/18/03 ( firm )– Platform development proceeding– Site requirements not defined– CRD not yet started
Projecting about 1w late at Gate 0/LCA due to CRD.
FOR MORE INFO...
Contact: Doug S.
Project Metrics Collection Plan
There are standard project metrics for all EK projects as described in the SOP 1F2236 that will be collected: Software Development Cost and Effort Software Project Schedule Progress Software Product Quality Software Product Functionality Software Product Performance goals
FOR MORE INFO...
Contact: Jeff B.
Related Documents
Marketing plan waived in PDPBudget - small budget model appliesStaffing plan contained in PDPWAIS Development Process with
RUP phased rollout
FOR MORE INFO...
Contact: Tim L.
Cost and Time Summary
Direct Labor costs: $142,140.62Capital costs not in this scheduleProject Duration: 126 daysFinal delivery date: 5/22/03Feature count: TBD
Contact: Doug S.
FOR MORE INFO...
Rollout Schedule-Overview
• All development/testing is for Gate 1/LCA
• Gate 2/3 is documentation/PR.
Gate 0 - Planning Phase
Team is formed, gate 0 work 63% complete and on schedule for 3/11/03 gate zero.
Collection of site requirements is on schedule.
Gate Zero – Platform Definition
Platform definition due 3/5/03 Running in parallel with site requirements.
Gate Zero – Process Documents
Back loaded from 3/18/03 G0 date Runs in parallel with site requirements.
Gate One – Rapid Prototyping
Engineering prototype due by 3/25 Gate two documents planned back from 5/30. Developers allocated at only 60%
Gate One – Documents
Documents due 5/9 for 5/13 G1 Substantially all development/test complete
Gate Two – Documents
Documents only, combine G2 and G3 ? No development planned/test complete
Rollout Schedule-Gate Three
No development, just documentation Duration fixed primarily by resource constraints Schedule can be improved with TKM support
Rollout Schedule-Phases
Gate targets at the top for visibility Major start dates shown below
ID Task Name Duration Start Finish
0 HI DHF System Project Schedule 148 days? 12/11/02 7/4/031 Gate Dates 86 days 3/6/03 7/4/03
2 Gate 0 Target 0 days 3/6/03 3/6/03
3 Gate 1 Target 0 days 4/7/03 4/7/03
4 Gate 2 Target 0 days 5/12/03 5/12/03
5 Gate 3 Target 0 days 7/4/03 7/4/03
6 Quality Planning Phase 62 days? 12/11/02 3/6/03
40 Requirements/Design Phase 22 days? 3/7/03 4/7/03
64 Construct/Test Phase 26 days 4/7/03 5/12/03
86 Use Phase 39 days 5/13/03 7/4/03
Project Reporting Structure
Weekly schedule update on Fridays Weekly in-process task list to Jeff Schedule distributed within R&D team. Post schedule changes as responses to
the schedule itself in the Project Database.
Conclusions
Assumes all non-project activity does not exceed 40% - OK
Detail on the site rollout in Program Plan but not schedule
Assumes no scope creep G2+ since no development is scheduled