Represented: Systems Engineering (Rich Murphy, Mike Berger), Infrastructure and Operations (Garry Zacheiss), Data Management (Amon Horne, Paolo Fragomenti). Steve Landry facilitated.

Purpose: Rules of engagement for support wings of the organization to validate and approve RAFT releases; validate supportability; facilitate knowledge transfer.

Roles

• DM provides project implementation and Tier 3 support.
• DM provides references materials for support teams.
• OI will stage releases with approval privileges at the system and application-server architecture level.
• SE will review code and software architecture for supportability in terms of skill sets and complexity.
• SE could provide additional developer resources for projects or problem resolution, not on escalation communications chain.

Deliverables

• SE (Rich) requests DM prepare materials that fulfill the purpose of traceability matrix and technical specification. To be submitted before code-review resources can be secured from SE.
• SE (Rich) requests stress, unit, other tests. (JMeter? PHPUnit integration underway.)
• DM agrees to provide at least technical white-papers and a toolchain/troubleshooting guide (quoting Paolo).
• OI (Garry) requests a disaster-recovery review before go-live. Add security team, Tim McGovern for data security perspective. This can be accomplished in a meeting.
• Moving UXD documentation to Wikis--standard tool for internal UXD staff.

Risks

• Resource Problem: Define Skillsets; PHP, RESTful, and high Web 2.0 design factors. SE, other teams, lack deep knowledge to support the application.
• DM might need to staff internally for these specific skillsets (they are the ones with open positions right now).
• Support escalation to developers in SE: process ill-defined, fuzzy. Requests to Sr. Staff? "Process design" project working on support-escalation policy.