• Created by user-ecd72, last modified by user-d5409 on Oct 04, 2011

Hour by Hour agenda, including goals, topics, room locations and participants for the workshop. 

Workday technical integration workshop at Cornell

NOTE: Look at these context diagrams and notes from technical impact assessment for an introduction.

Attendees: Workday, Vivantech, CU
1. Core attendees: Lyman, Laurie Cecere, Seth Brahler, Kim Cassell, Vicky Mikula, Phil Robinson, Steve Lutter (facilitator), Graham Hall, Dustin Henson from Vivantech, and Workday reps Alexandra and Kalan.
2. Special guests for certain hours are listed below.

Day 1, Wednesday, October 5th, 2011

  1. 8-8:20: 
    1. Introductions
    2. Review end goals: complete an end to end integration and remediation estimates. End to end means Workday and Cornell stewarded software, complete means from spec through development, testing (unit, system, business process, fault tolerance) and support, and plan means dates, resources, dependencies, and estimates are figured out, if not formallized. Share the templates to filled out. This would be delivered to Workday and CU senior management as a comprehensive view of the technical work needed.
  2. 8:20-9:20: Review of Workday integration solutions and techniques, by Workday.
  3. 9:20 - 10:00: Review existing stuff (plans, context diagrams, Dustin’s proposal and standard architecture plan, Workday integration inventory list...) 
  4. BREAK
  5. 10:15 - 11:30: 
    1. Discuss Oracle SOA and standard interfaces in the future, including fault tolerance, troubleshooting, monitoring goals and expectations
    2. Discuss prototype goals in the end of October and resources and specs needed for that
    3. Discuss version management of both sides of integrations during and after the project and related requirements
    4. Discuss environments (dev/test/training/prod) required to support integration work and testing plans and requirements
  6. 11:30 - 12:00
    1. Define what ‘done’ means for an integration
    2. Work backwards on the steps required to be ‘done’, in general
  7.  LUNCH
  8. 12:30-2:00: Review Architecture concepts from the morning, and what ‘done’ is, steps deemed required to get there, and other highlights from the morning
    1. Special guests Bryan, Dennis,  Sameer
  9. 2:00-3:00: PART 1: INTRO Workday to/from Kronos
    1. Special guests Michele Riechert, Kim Cassell
  10. BREAK
  11. 3:20-4:30 PART 2: Workday to/from Kronos - tasks, assumptions, estimates
    1. Special guests Michele Riechert, Kim Cassell

Day 2, Thursday, October 6th:

  1. 8-9: PART 1: INTRO Workday to/from PeopleSoft Student and CR and Campus Community
    1. Special guest Dennis Frederick, Sameer
  2. 9-10: PART 1: INTRO Directory and Workday strategy
    1. Special guests: Pete Bosanko
  3. 10:30-12: PART 1: INTRO Workday to/from KFS
    1. Special guests: Bryan Hutchinson, and Kim Yeoh,  Davina.
  4. LUNCH
  5. 12:30-2:00 : PART 2: Workday to/from PeopleSoft Student and CR and Campus Community - tasks, assumptions, estimates
    1. Special guest Dennis Frederick, Sameer
  6. 2:00 to 3:00 : PART 2: Directory and Workday tasks, assumptions, estimates
    1. Special guests: Pete Bosanko
  7. BREAK
  8. 3:30-4:30: PART 2: KFS / Workday tasks, assumptions, estimates
    1. Special guests: Bryan Hutchinson, and Kim Yeoh

Day 3, Friday, October 7th:

  1. 8:00 - 12:00: Workday->BI extraction options, status, plans, estimates
    1. Special guest: Dave Wakoff and Chris Grippin
  2. LUNCH
  3. 12:30 - 4:00: Revisit loose ends/ backlog of questions, recap on assumptions, package up all findings and decisions. FINALIZE the Spreadsheet to deliver to Ted by the time we adjourn.
  • No labels