1st Software Measurement eWorkshop Agenda

Each of the areas below is probably an eWorkshop of its own. There are some concerns about being able to reasonably cover the bolded subset of points in this one session.

We are using this 1^st eWorkshop as an opportunity to propose key questions and structure the discussion for future ones.

The entire list of goals and subtopic questions has grown to include (bolded items are main goals for this 1^st eWorkshop):

a. Calculating Return on Investment (ROI)

Goal: Gather ROI stories; categorize the types of issues encountered; begin to understand the relevant factors and activities involved; and define a ROI process.

o What experiences have you had in calculating ROI?

o At which organizational level (project, business unit, etc.) did you approach the problem?

o On which program areas did you base the ROI calculations?

· Measurement

· Management

· Process improvement

· Introducing new technologies

· Making architectural changes

· Making organizational changes

· other?

o Were your conclusions accepted?

§ What were the easy issues, if any?

§ What were the inhibitors to acceptance? (the “Yes, buts” …)

§ What follow-up occurred?

o What should a ROI process include?

§ What factors are used/should be used in calculating ROI?

§ What activities are part of the ROI model (e.g., generate process documents)?

b. Measurement and CMM, CMMI, Profes

Goal: Gather a set of measurement goals relating to CMM,CMMI, and Profes; put these goals into context on project and/or organizational levels; and define relationships between CMM, CMMI, Profes measures and “management through measurement” program measures.

o What are the goals of measurement in these models (CMM,CMMI, and Profes)?

o What is measured in these models? (consider both process and product)

o What, if any, measures are not part of the models? Why important?

o What is a recommended path to introduce measurement in a company that uses CMM/CMMI as improvement vehicle?

o How can a project/organization accommodate/ represent variations of similar measures (e.g., size measures) for different contexts/purposes in a repository?

o How can a project/organization balance the collection of "standard" metrics as well as the collection of individual problem-oriented data?

o How does one couple measurement and model development?

	FC-MD is a Research Affilliate of the University of Maryland.
	Please visit the Center for Empirically Based Software Engineering (CeBASE) website