Laddawn.com : Launch planning meeting notes

7/1/14

Cathy, Jim, Owen, Susan, Tina

Cathy working with John to upgrade Google Analytics to "Universal" and get that implemented on the staging site; additional pieces of the plan (like event tracking) will wait for programming to wrap up.

Cathy worked with Tim to get Owen the user-specific logon data he was seeking. Susan agreed to mine Google Analytics for data on frequent users of Ladddawn.com who also use IE7.

Owen's product description work is going well, he is paring them down - but he has some questions for John that he needs to address in order to be able to finish up. Still on track for 7/15.

Cliff's work on YMAC was stalled due to prior rule data entry being overwritten by a programming update. This has hopefully been resolved, but Cathy will check into it to be sure programmer updates are being done in a manner that prevents this from happening. Still on track for 7/15.

Owen's work on content has not progressed. May not be on track for 7/15. Owen to work with Steve and Parke on this.

The CE training site has been reopened for testing and Tina is renewing her focus on vetting the site; Susan has developed a framework for systematically vetting the site using a checklist of specific tasks and questions that Tina will test out this week. Susan and Tina will jointly develop a more comprehensive checklist of basic, intermediate and advanced CE tasks to vet. Tina and any testers she enlists do not need to be concerned with reporting bugs (unless its something that stops them in their tracks). Susan will test the site for slowness and compare first-time v. repeat actions to see if the theory holds up that first-time actions are taking longer than a repeat of the same action.

Action item: Susan, Cathy to work w/John to determine how CE should close out of an 005-spawned web session:

  1. When done with a request, should CE log the user out and close the web browser completely?(Does closing the web browser log the user out, saving a click?)
  2. Or should CE just log the user out, close the tab, but keep the browser open (with one tab always open)?
  3. Is it possible for the act of closing the request in Avante to automatically handle whichever option above is the chosen method for closing the session, rather than relying on operators to do this consistently? 

Cathy shared the news that Janice has automated the process of updating the CE training site and gotten the time it takes to do these updates down to ~15-30 minutes; this will allow the updates to be done more frequently than  once per week.

6/17/14

Cathy, Jim, Owen, Susan, Tina

Reviewed status of WorkZone tasks and entered some revised dates.

Tina, Mark and Owen meeting Fri. am to strategize on how to communicate w/frequent website users to prepare them for the launch of the new site.Cathy will work with John to provide Owen and Tina with a list of customers who have logged in recently (ideally, if the data is there to support it - users who log in frequently).

Owen to produce a spreadsheet with product description data; developers to provide the "on ramp" for the data. Drop dead date for this is 7/15; sooner is appreciated in order to the make the testing experience more "real" for CE.

Wayne recently completed the programming necessary for higher/lower dimensions in YMAC match rules. Cliff should be able now to enter all YMAC rules. Cliff's drop dead date is 7/15, sooner is appreciated in order to the make the testing experience more "real" for CE.

Dates in WorkZone will reflect "sooner."

We discussed Steve's progress on design of fat footer and generic content pages. We will have a preview meeting 6/19, and hopefully a final handoff 6/26.  Owen needs to hand content to developers by July 15; IT has slated two days/16 hours for putting content into final web format.  Realistically, Owen should probably hand content "chunks" off as soon as they are completed.

We decided to suspend CE testing until we could resolve a) login issues and b) slowness issues and demonstrate some day-to-day stability. We need to isolate the cause of slowness - is it bug-driven or hardware/network-driven? Susan and Janice will troubleshoot.

I (Jim) touched on the fact that the programming needed to support out Google Analytics needs was manageable and that we would like be able to incorporate it all into the development schedule.    To better understand the depth of the work we will need to identify the key activities that should be tracked to support analysis goals.   I would like to see the Marketing group identify the list of needs here.