You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

  • team members will continue on this project for Phase II (part of Phase II will be to scope charter and membership of Release Core and see who will stay on and who will join)
  • next series of meetings scheduled
  • sponsor meeting scheduled for 9/28
  • implementation plan for Phase I
    • status of socialization with Associate Directors
      • Barbara - positive response, some concern about feedback loop (post release - what went right, what did not)and would like us to consider auto notifications as part of process
        • others have concern about mandates and enforcement, so we need this process to be seen as a supportive tool as opposed to a way to measure success of a release (judgment) but also monitor, to some degree, if folks are using it and using it correctly
        • can we take some heavy processes (like QA) and make them lighter so they can fit into this process? (RT Upgrade is an example of how a very heavy process has a hard time integrating with our proposed release process)
      • Mark - likes the self directed approach
      • Steve B - need to clarify scope and reset expectations (Pat and Patrick) to re-enforce purpose of group
      • Mary - very positive, wants to volunteer RAFT and the Reporting Tool as pilots
      • Bart - Steve will meet with him 9/17
      • Eamon - likes the a la carte approach we have, would like to have us incorporate some SDLC check points (source control, tagging)
        • also like the idea of the Release Core team as a resource
    • status of pilots
      • Athena Fall release - lessons learned
        • need to add black out dates to checklist (IS&T: ISDA Tracking pipeline calendar can help with this)
          • need to know target and drop dead dates for release
        • need to pay more attention to who you need to communicate with (stakeholders)
          • need better engagement
        • need to add transition management to checklist
        • this was an example of where having an unclear owner made decision making difficult (people felt they could not stop the release even though there were good reasons to hold back as well as repercussions if we did not go forward)
          • owners need to know that when they make a go/no go decision that they have support
      • TSM client - in progress
      • BES 5 - about to start (Chris will reach out to Deb)
      • Outlook/Office for Mac - Oct/Nov (Patrick)
      • other VSLS product releases this fall - TBD (Chris)
      • RAFT - January, but Amon will begin to familiarize himself with checklists (Steve)
      • Reporting Tool - possibly November (Pat)
      • Identity Finder - in progress (Patrick will reach out to Mike)
    • LWG agenda item moved into November
      • possibly have members of Release Core walk through the process with groups at each table and solicit feedback
    • newsletter article should happen after LWG presentation
    • table Release Core charter and membership for 2-3 weeks to focus on Service portfolio
    • Service Portfolio
      • much larger than the Service Catalog Barbara and Christine are working on (theirs may be a subset)
        • Patrick is communicating with Allison and Pat with Barbara and Christine as to progress and direction and how we can leverage each others efforts
      • data model needs to be determined - application services will need serious clean up (many tools and components that may need to be separated out)
      • we have various sources to consider feeding this database
        • SWRT list of desktop tools (Patrick will send out)
        • IS&T Software Portfolio (Pat will send out excel version)
          • Pat will work with Allen to get group access to FileMaker version (hosted by DCAD)
        • IS&T Products and Services List from 2008 (Pat will send out)
        • Software Grid on IS&T Website (Allison and Patrick in communication)
          • ideally this would automatically update when there is a corresponding update to the Service Portfolio)
      • we need to determine what fields/information we want captured, for example
        • various types of owners (business, service, financial)
        • escalation paths
        • host names
        • what other services the application/service talks to
        • components involved
        • renewal dates
    • next steps
      • Pat will draft Phase II Project Plan (high level)
      • memebrs will send out various data sources as cited above
      • members will review the various data sources cited above
      • Chris will try to find the VSLS notes from last fall that delineated fields/information that would be useful to capture centrally
      • Pat will update senior staff every 4 weeks with progress/lessons learned

Agenda for Thursday September 23, 2010

  • review project plan
  • discuss data sources
  • better define what info/fields we want
  • determine data model
  • try and determine what type of repository/data base would work
  • determine if we need funding to accomplish this and resources (DCAD?)
  • decide who will update the checklists with lessons learned
  • No labels