Background

The SRAO project launch (formerly SRDP) established a new structure for production and delivery of data products to the user community.  The new structure came with changes to practices and processes in the areas of Project Management, Systems Engineering, architectural design and modeling, requirements management, communications and reporting, and perhaps changes in other areas.  Recognizing the disruption this magnitude of attempted changes would incur, this Mid-Pilot Assessment was built into the plan to be deliberate about using what has been learned during the Pilot for improvements to the first full deployment in Wave 1.

Objectives of this Review

• To conduct a project level review; informational only, no review gates involved
• To provide an opportunity for the team to assess practices and processes to date
• To review  what went well and what did not
• To identify areas of opportunity for improvement
• To identify processes and practices that should either change or be discontinued
• To establish concrete steps to address each item reviewed
• To satisfy the Q1FY19 POP Milestone in the subsequent quarter Q1FY20

Review Logistics and Material

• A lessons learned list has been compiled throughout pilot development and operations, thanks to everyone that has provided input so far.
• The list has been structured using a "Roses and Thorns" approach

1. • Roses:              What is working?
   • Buds:                What opportunities can we explore?
   • Thorns:            What is not working?
   • Fertilizer:          Improvements on existing processes, support for new ideas

• Document to review:

SRAO Mid Pilot Assessment

• The document is on SharePoint with track changes enabled, version history enabled, ready to accept comments and edits
• Reviewers are asked to make edits directly to the file linked above
• The edited document will be discussed and reviewed in a group by the project office and team leads
  • Review Date (TBD, before Thanksgiving)

Outcome

This is not a review gate, so there is no pass/fail threshold.  An action plan will be appended to the document under review following the meeting and the Project Manager will follow up with document edits, process changes, Jira tickets, or whatever is called for in the action plan.