1 / 9

FY2009 Metrics Reporting Review Greg Hunolt, SGT ES-DSWG / MPAR-WG October 20, 2009

FY2009 Metrics Reporting Review Greg Hunolt, SGT ES-DSWG / MPAR-WG October 20, 2009. Agenda FY2009 Metrics Reporting Status Impact Metrics Observations Outlook for FY2010. FY2009 Metrics Reporting Status: Products & Services Metrics. 1. MEaSUREs Projects:

dorit
Download Presentation

FY2009 Metrics Reporting Review Greg Hunolt, SGT ES-DSWG / MPAR-WG October 20, 2009

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FY2009 Metrics Reporting Review Greg Hunolt, SGTES-DSWG / MPAR-WGOctober 20, 2009

  2. Agenda FY2009 Metrics Reporting StatusImpact MetricsObservationsOutlook for FY2010

  3. FY2009 Metrics Reporting Status:Products & Services Metrics 1. MEaSUREs Projects: • 30 MEaSUREs at program start (1 project has two reporting elements); • 8 MEaSUREs projects began reporting metrics during FY2009; • 7 of these were REASoNs that transitioned to MEaSUREs, so 1 brand new project began reporting in FY2009. • The remaining 22 MEaSUREs projects are expected to begin reporting metrics when they begin distribution: • 10 MEaSUREs have indicated FY2010 distribution start dates. • 5 MEaSUREs have indicated FY2011 distribution start dates. • 7 MEaSUREs have uncertain distribution start dates.

  4. FY2009 Metrics Reporting Status:Products & Services Metrics, Cont. 2. REASoN Projects: • 42 REASoNs at program start; • 20 REASoNs were completed by end of FY2008, • So 22 REASoNs were active during FY2009. • Of those 22 active projects, all reported metrics. • 13 REASoNs completed and stopped reporting during FY2009. • 7 REASoNs (of the 13) transitioned to MEaSUREs projects during FY2009. • 2 REASoNs were expected to complete at end of FY2009 • 7 REASoNs remain with nominal completion dates during FY2010 (a few on no cost extensions).

  5. FY2009 Metrics Reporting Status:Products & Services Metrics, Cont. 3. ACCESS Projects: • 16 ACCESS projects at start; • 1 ACCESS project completed before FY2009; • 15 ACCESS projects were active during FY2009, of those 10 reported metrics, 4 reported ‘development’, 1 hold-out; • 12 ACCESS Projects completed during FY2009; • 3 ACCESS Projects will continue and report metrics into FY2010. • Greg will be doing 4th quarter / end-of-year review, and contacting all projects next week.

  6. Impact Metrics Status FY2008 saw a sharp decline in Impact Metrics reported, after peak in FY2007, with a further decline in FY2009 as more projects completed their work. Examples follow…

  7. Metrics / MCT Problem Reporting Process used for handling problems with metrics reporting: 1. A project encounters a problem working with the website. 2. Project clicks on one of the "web administrator" mailto links and sends an email to Jody Garner, the GSFC website administrator, describing the problem.   3. Jody reads the email, and creates a trouble ticket from it. 4. Jody does a triage... • If it is an operational / admin problem, Jody resolves it with the Project. • If it is a software / database problem, Jody tasks Randy Barth to resolve and enters a trouble ticket, supports Randy as needed. • If it is a matter of interpretation / understanding of the metrics, Jody tasks Greg to resolve with the Project. 5. Randy or Greg resolves problem with Project, with confirmation from Project, and reports resolution to Jody. 6. Jody closes the trouble ticket. Meanwhile, Jody monitors open trouble tickets, pings for progress as needed.

  8. Observations • Metrics reporting has not been a major burden for the projects, and most projects are happy with the website. • Most projects have found the metrics to be of at least some use internally, beyond just meeting their NASA requirement. • The Service and Project-Defined Metrics continue to be successful (to the extent that they were used) in helping projects to portray their activity. Use by MEaSUREs could be encouraged. • Using Service metrics allows a project to distinguish its services from its products; • Using Project-Defined metrics allows a project to define metrics that make sense in the project’s own context;

  9. Outlook for FY2010 • 18 to 25 MEaSUREs Projects will continue or begin metrics reporting during FY2010 (i.e., 10 to 17 projects will begin in FY2010); • The last active REASoN and ACCESS Projects will phase out during FY2010. • A major priority will be to support the MEaSUREs projects as they begin their metrics reporting, while continuing to support the remaining REASoN and ACCESS projects, and accommodating new ACCESS projects. • Greg will contact MEaSUREs projects to ask for their preferred point of contact for metrics and to provide background / offer assistance with the metrics. • Jody Garner will help MEaSUREs with passwords, etc., and making sure they can access the reporting tool. • Tomorrow the metrics baseline and the longer term plans for MEaSUREs metrics reporting will be discussed, including the transition of metrics reporting from the current MCT to “MCT-2”.

More Related