02/24/2009

11 am, N42-286, CSS Managers 

Agenda

• Resource Models: How can CSS use this information?  Desired Outcome: Agreement on a draft plan on how best to use the information collected in the Team Resource Models.  Answer the questions: What are the benefits of collecting this data (to CSS/IS&T/MIT)?  How can the data help CSS teams, help each other? How is this data going to be used? How often should we be updating the Resource Models?

Kate led a discussion on how RMs were ever used and is there a way to use them better within CSS?
a.) capturing staff time on specific named work (like projects) that want to be totalled up to see how much the total contribution of everyone amounts to.  Drives a financial view of any particular effort.  "Costing a line of business" in Anne's parlance.
b.) individual managers are interested in knowing how their staff is deployed, to (within the team's management) understand if they're deployed right.
c.) analyzing revenue models to drive billing for the time spent.  DITR and DCAD use it this way. 

The RMs are useful bases to answer the management questions that come along about "how much of FTE is going to something".  When asked an ad-hoc question, the data to draw on is already there.
It's just a good management practice.

Time reporting certainly makes the tabulation possible of what they are doing, versus what they're being told to do.  The lack of a consistent effort in this area undermines the usefulness or constitency of the data. 

Have a list of questions like what do we want to know, and then generate the data accordingly. 
A Wilson question may be very different than a Terry Stone sort of question.
Anne remarked that the current focus seems to be how much time and mondey is being invested per product or service.

Another use of the model is to know whether certain resources are or aren't available for borrowing.  Nowadays a manager needing someone goes and asks.  This was the original reason for the previous resource model; to accomodate questions from SAIS and ISDA about CSS resource availability.

The challenge lies in answering multiple questions (time, product line, etc.) at the same time, all the time.  It seems to Jon like a lot of investment for not so much return.  Everyone would benefit from being asked things earlier, instead of requiring night-before fire-drills.

One useful question likely to reappear is "if we cancel this project, what resources will it free up?"
Tim reinforced the point of "What are the questions that the data needs to answer?"

a.) you have to capture time;
b.) you have to have people willing to be honest with you;
c.) each reporter needs their own work labels for work that 's unique, and shared labels for work that is the same.
To be successful, the group of us needs to commit to collecting time, and all the other stuff that ought to be known.

• Quick overview of RT Enhancement project underway.  Pat Sheppard, Oliver and Steve Turner have been in conversation with Best Practical on steps to both get us up to a more current version of RT and carry out some much needed performance enhancements.  I've asked Oliver to give us all a quick overview of this project and where it stands.  (goguen - left over from last week)
• Thoughts on priority projects (goguen - in prep for VP staff meeting on Thursday)
•   

03/03/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

03/10/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

03/17/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

03/24/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

03/31/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

04/07/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

04/14/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

04/21/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

04/28/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

05/05/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

05/12/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

05/19/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

05/26/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

06/02/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

06/09/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

06/16/2009

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

06/23/2008

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

06/30/2008

11 am, N42-286, CSS Managers 

Agenda

• awaiting the first agenda item
•  
•   

[*]