Draft 10/15/2010

Software Release Working Group (aka: Release Core)

Definition

Release Core is established to provide governance, direction and resources for product and service release and service portfolio maintenance efforts in IS&T.  This group will serve as the stewards of IS&T release and deployment methodology (aka “release ball”), and promote and support the effective use of those practices across the organization. Release Core has the responsibility to ensure that IS&T release and service delivery processes are repeatable, helpful, easy to use, and improved over time.

In addition, Release Core advises the Project and Process Improvement Manager and IS&T Senior Leadership on related work and issues within the department and submits recommendations when appropriate.

Purpose

In scope:

• Provide leadership in the area of release management and service delivery
• serve as "navigators" of the release and service deliver process
• Develop and maintain IS&T service delivery best practices that are practical and actionable (Release Ball)
• Adopt and disseminate Release Ball methodology
• Mentor and coach staff in the application of Release Ball
  • provide desk side support and service to release efforts as requested
• Develop tools for central portfolio maintenance, for example:
  • IS&T Service Portfolio
  • IS&T Product Release checklists
  • IS&T Pipeline Calendar (in conjunction with IS&T Pipeline)
• Provide recommendations and develop processes for central service portfolio maintenance, including:
  • Acquisition
  • Purchases
  • Release windows
  • Charge backs
  • Retirement
  • Orphan products and services
  • Ownership roles and responsibilities
• Work closely with IS&T Pipeline group to share information and escalate issues to senior leadership
• Encourage a collaborative, responsive work environment and foster trust across the organization

Out of scope:

• decisions on what products and services IS&T provides and supports for the community
• approval or gate keeping functions
• decisions regarding prioritizing projects or resources

Role of a Release Core Member

Release Core expects to leverage the experience, expertise, and insight of key individuals in the department committed to building standards and professionalism in service delivery and process improvement. Release Core members are directly responsible for managing various release activities in their respective areas, as well as provide support and guidance for others in the organization with similar roles and responsibilities.

Release Core members should:

• Understand the impact and desired outcomes of service delivery improvements
• Be genuinely interested in service delivery and be an advocate for broad support for the outcomes being pursued
• Have a broad understanding of release management issues and approach being adopted
• Provide guidance to release managers and team members and other players of Release Ball
• Consider ideas and issues raised by users and incorporate feedback (continuous improvement cycle)
• Encourage adherence to process standards (best practices) within the organization

Release Core Members

Release Core will be composed of volunteers throughout the organization who have incorporated the mission of Release Core into their goals for the upcoming year.

Meeting Schedule and Process

Release Core will meet weekly for the first 3-4 months, in order to establish the priority objectives, plan the work in order to meet those objectives, and assign resources to accomplish goals.  The meetings will then transition to monthly or as required to keep track of issues and progress.

Release Core requires an initial investment of time up front.  The estimated time commitment for each member is approximately 16 hours from August through December, and 8 hours/month going forward.

Reporting

The facilitator of Release Core will report to senior staff on a quarterly basis relevant activities, issues, and recommendations.  In addition, meeting agendas, minutes and supporting documents will be made available to staff across the department so that they can be aware of the work and recommendations of Release Core.