Upload your Project Closure Report

chaitu9z00
LessonsLearned.docx

April 1, 2014

Lessons Learned – Website Redesign and Consolidation Project

1. Successes - what was learned that worked well and should continue.

0. Contract was at the level of detail that allowed us to manage within contract and meet customer expectations

0. Customer sponsor Randy Hampton was terrific in understanding that this was a two sided engagement – we both wanted a great product but also wanted it to be good financially for us the vendor and STATE AGENCY

0. Jeff Dalton provided good technical leadership to arrive at a solution

0. Pontus delivered good value during project in building the farms and trouble shooting issues and keeping track of actions

0. Having David as an advocate and technical lead from STATE AGENCY was very helpful

0. Initial kickoff of requirements gathering and design specifications provided good start to project

0. STATE AGENCY did what it took to migrate the content leveraging its internal staff - Doug did a great job in making sure the content got migrated

0. Custom applications were reviewed thoroughly along the way from a user perspective

0. Project manager communications between Tom and Nina helped keep the project on track without a lot of extra time spent

0. Escalations at the end of issues by Randy, Doug, Dave and Nina helped close out the project successfully

0. Weekly status and issue discussions seemed to keep project communication going and issue resolution progressing

0. MS Project schedule was used for the first 2/3 of the project and helped us understand impacts of delays

1. Challenges -. what was learned that did not work well and needs to change.

1. STATE AGENCY was not aware of the BING costs until application developed – application had to be significantly modified to work with the lower cost solution and better APP Dev solution using Google

1. IT was not in the loop enough and proactive enough in the project – they only responded to issues and problems - did not really leverage the Monrovia Industries architecture that was developed and documented

1. It took months longer for IT to stand up server farms

1. Monrovia Industries took longer than we would have liked to explore the automated migration solution – STATE AGENCY was ready to manually migrate but this was delayed in hopes of obtaining an automatic approach.

1. Seemed like DNR/IT wanted an Operations guide but wasn’t in the contract

1. David did not have enough power within IT organization to make things happen – Randy did not either.

1. There was some lack of clarity towards end on who was to migrate the content

1. Recommendations - suggestions going forward and the benefits.

2. When considering alternative 3rd party solutions like Bing or Google, make sure the client understands the tradeoff and as well as the developers

2. Hold biweekly reviews with DNR IT and particularly review design documentation review with them and get them to sign off on them early

2. I don’t know how to get IT to actually deliver on Server Farm earlier – we needed maybe a DNR IT sponsor that was on our team – executive or mid level with moxy to make things happen

2. Make earlier decisions on “manual” versus automated… institute an earlier drop dead date..

2. From DNR IT side, make sure operations guides are included in the contract if important.

2. Better clarity on the migration roles – contract tried to highlight them out.