Top-level ideas

Increase visibility and clarity regarding facility's activities and funding. Clarify service offerings and scope. Express our work to confirm value and ensure proper direction of our efforts.

Outcomes might include:

• Project portfolio (with periodic review and prioritization?)
• Time tracking records over time (with periodic review and re-direction?)
• Annual budget (so "obvious" things are pre-approved through a ~annual review)
• Fair and balanced funding from Research and CCB Admin

For: April 2 2013 mtg

Collect this data for all four CRCF staff:

1) Record hours spent per group for ticket-type tasks which take more than 1 hour.

• If less than an hour, no need to record time. Just record ticket without time estimate, as we've been doing.

2) For non-ticketed work which takes more than 1 hour, record time and the associated "problem/ project" being worked on.

Method  (DRAFT!)

For ANY multi-day >1 hour work, create a ticket, even if not an "incident" so we have a unique number associate with this mult-day work. Record time either there, or elsewhere, referencing ticket number. Add up total time at close of project, or when snapshot requested.

Also

Share information of our considerations and actions related to systems we have authority to manage. These can represent a necessarily dynamic "Standard of Practice Bar", if you will.

Ex. Remove Java where possible, and why.

• Explain how to remove Java (Mac, Windows), and offer our assistance. Consideration to help identify which systems don't need it. And Java could be re-installed where subsequently found to be required. Where Java retained, maintain its updates (hard, currently!).

For: March 5 2013 mtg

Start answering the question "What does CRCF do, and for whom?"

A: CRCF does about 75% of their work in direct support of Research.

• Assumes that the number of opened tickets over 4 months adequately represents CRCF's relative effort distributions of Research vs. non-Research activities, over a year.