1. Deploy Phase Tips for Success or It ain’t over ‘til it’s over

2. Bad Project End Scenarios “Can you just squeeze in this one fix?” –Lack of internal support at client “Hey! You missed this! We talked about it!” –Missed or misunderstood requirements “I thought we were done?” –Lack of follow-through internally / team commitment “Wasn’t this part of the contract?” –Lack of up-front thought

3. Bad Project End Scenarios “Nobody can bill the job anymore!” –Running out of money before deployment is finished “The production server doesn’t support this?” –Not understanding complete technical picture “I thought you folks were the pharma experts!” –Inadequate review / consideration of content “Med/Legal comments? Oh…any day now.” –Inadequate schedule discussions

4. Some Deploy Deliverables Final client-approved software Production release / transfer of files Documentation –Installation Guide –User Guide (following client sign-off) Client Training (technical knowledge transfer)

5. Deploy Tasks Implement deployment strategy Production environment configuration Parallel testing Final client review Help desk training Deliver documentation Installation Guide User Guide Correction of any installation problems Implement Launch/Promotion marketing strategy Technical knowledge transfer meeting Implement maintenance & support strategies

6. Deploy Tasks Install traffic analysis software Initiate ongoing support team Traffic analysis Web metrics analysis Visitor demographic analysis Measure effectiveness Technology (performance) Usability or User Experience (qualitative) Against Business Requirements (including traffic) Bench Marking (market) Conduct research Case Study

7. A successful project conclusion starts at the beginning of the project

8. Best Defense is a Good Offense! Set the stage early by talking about the importance of meeting approval deadlines [Analysis] Review the process & deliverables w/ client early [Analysis] Anticipate common client questions early, like: [Analysis] –“How are we going to measure this site?” –“Are you guys gonna register the site?” Set firm dates early [Analysis] try to find reasons for hard dates if none exist

9. Best Defense is a Good Offense! Document Site Requirements - (your "PRE-spec") Include as summary in your Functional Spec [Invent]

10. Best Defense is a Good Offense! Have a mid-project contract review with client [Invent] –Help mentally prepare your client for the project close Keep a communication link with your IT contacts Visualize the end of the project Remember, the client is expecting you to manage from beginning to end.

11. Keep your team focused Don't let your resources flake out! Galvanize your team –make sure they understand their role & the importance of their commitment establish at kick-off meeting [Analysis] Personal meetings; develop a repor team charter or similar with closeout criteria [Analysis] Issues Management Meet with them every week, regardless.

12. Keep your client focused Simple, easy to read calendars (Publisher, etc.)

13. Keep your client focused Send out clear expectations & follow-up with discussions via phone Document hosting group's tasks in Spec [Invent] –Insist on an IT point of contact in SOW Have weekly meetings, regardless. In person if possible.

14. Keep yourself focused Organization is key! Specs in binders [Invent] Keep a Master Copy with all edits Be good to yourself

15. Keep your project budget healthy Keep tight control over the resource “tide” See who’s hitting it each week –Expect work accomplished with time spent Issue friendly budget reminders to anyone who may hit the job FREEZE the project if things are dragging …but keep things well mothballed

16. Solutions Quiz 1.Lack of internal support at client 2.Missed or misunderstood requirements 3.Lack of follow-through internally/team commitment 4.Lack of up-front thought 5.Running out of money before deployment is finished 6.Not understanding complete technical picture 7.Inadequate review/consideration of content 8.Inadequate schedule understanding 1.Complete tech audit & communicate to team 2.Visualize the project end early with Tech Lead 3.Communicate hours left; keep firm control 4.Clear calendars 5.Weekly team meetings 6.Document requirements in clear, outline form 7.Review content with Pharm expert or QA experienced 8.Get an IT point of contact committed early (SOW)

17. Discussion