Subscribe by Email


Showing posts with label Measurement. Show all posts
Showing posts with label Measurement. Show all posts

Wednesday, June 12, 2013

Too many meetings: Calculate total spent of people in the meeting and highlight ..

It's a tricky situation. Your boss or other senior managers like to have a number of meetings on all issues and this gives you less time do your job. But how do you get them to change this strategy. We had a situation similar to this one where the boss was trying to have a number of meetings on different topics, and it was getting uncomfortable. On the other hand, there was also the oft stated position by many members of the team that they did not know about what was happening with regard to company strategy, and felt detached from the policies and steps being taken by the company, and this was expressed in internal surveys carried out by the company.
So, meetings can happen on many basis:
- When there is a chance in strategy, meetings would be held to explain what has happened and invite people to ask questions
- When there are senior management officials wanting to meet the team, there would be meetings to showcase strategy and status, and a lot of preparations to fine-tune
- Frequent meetings to walk through ongoing matters, including when the boss has ideas that he is looking to sound off from his direct managers or from the extended team
- Meetings where the boss is traveling to other geographic locations of the company and wants to talk about strategy before doing this traveling
- Meetings where the boss has been talking to senior management and wants to share feedback from such meetings, even when the meetings are of an interim nature
- And so on ...

Now, if you look at the set of meetings above, there are many that would seem correct and fine, and part of sharing ideas and strategy in the organization down the line. And this is what the boss would feel, that all these meetings were necessary and to ensure that people felt connected with what the group and the organization was doing. However, there is a fine line where the meetings go beyond what was necessary and start moving into the arena of time wasting. This is true in a number of organizations, although the scale of the time being wasted can differ. The problem with a situation like this is that this spoils the mood for all meetings, where even genuine meetings seem like a wastage of time, connected to the other meetings which are a genuine waste of time. And since these meetings are held by the manager or by senior managers, it is frustrating that one cannot stop such meetings.
There was one approach that was discovered about how to stop such meetings, or atleast ensure that there was a realization that such meetings are causing problems with the team and reducing the amount of time that can spent in more genuine work. There was an excellent article in a publication that talked about the amount of time that was spent in meetings, and suggested that for every meeting, there would be a clock that measures the amount of time spent, and then does a summary of time spent in such meetings, and time spent for each such person. Given that the article was suggesting that this would lead to a rise in productivity, we managed to ensure that another senior manager circulated this article, and we started following this principle. It was not good for us to not be able to raise this issue directly, but once we started measuring the amount of time spent in such meetings and showing the results on a monthly basis, we could see that there was a prioritization of such meetings, and things got better to some extent.


Tuesday, August 30, 2011

What are different object oriented metrics in software measurement?

Object Oriented Metrics


Lines of code and Function point metrics can be used for object oriented projects but they do not provide enough granularity for schedule. Some object oriented metrics are as follows:

- Number of scenario scripts
A scenario script describes the interaction between user and application. It is directly related to application size and number of test cases developed to exercise the system.

- Number of key classes
Key classes are independent components. The number of key classes is the indication of the amount of effort that is required to develop the software and it also indicates the potential amount of reuse applied during system development. The key classes are directly related to problem domain.

- Number of support classes
Support classes are not directly related to problem domain. Support classes can be developed for key class. Number of support classes indicates amount of effort required to develop software and potential amount of reuse to be applied.

- Number of subsystems
Subsystem is gathering of classes supporting a function visible to the end user. A schedule is laid out in which work on subsystem is partitioned.

- Average number of support classes per key class
Estimation becomes easy and simplified if average number of support classes per key class is known.

As database grows, relationships between object oriented measures and project measures provides metrics for project estimation.


What are different metrics used for software measurement?

Software measurement can be categorized in two ways:
- direct measures of software process.
- indirect measures of product.
There are many factors that can affect the software work so metrics should not be used to compare individuals or teams.

Size oriented software metrics are derived by normalizing quality measures by considering size of the software that is produced. Lines of code is chosen as the normalization value to develop metrics that can get absorbed with similar metrics from other projects. Size oriented metrics are widely used but there is always a debate about their validity and applicability continues.

Function oriented metrics uses measure of functionality that is delivered by an application as a normalization value. Function point metric is based on characteristics of software's information domain and complexity. Function point is language independent and it is based on data that is likely to be known early in evolution.

The quality of the design and the language used to implement the software defines the relationship between lines of code and function points. Function points and LOC based metrics are exact predictor of software development effort and cost.


Thursday, August 4, 2011

What is the framework for product metrics? What are the measurement principles?

A fundamental framework and a set of basic principles for the measurement of product metrics for software should be established. Talking in terms of software engineering:

- Measure provides a quantitative indication of extent, amount, dimension, size of an attribute of a product or process. Measure is established when a single data point has been collected.
- Measurement is an act of determining a measure. Measurement occurs when one or more data points are collected.
- Metric is the quantitative measure of the degree to which a system, component or process possess a given attribute. It relates individual measures in some way.
- Indicator is a metric or combination of metrics providing insight into software process, project or product itself.

There is a need to measure and control software complexity. It should be possible to develop measures of different attributes. These measures and metric can be used as independent indicators of the quality of analysis and design models.

Product metrics assist in evaluation of analysis and design models, gives an indication of the complexity and facilitate design of more effective testing. Steps for an effective measurement process are:
- Formulation which means the derivation of software measures and metrics.
- Collection is the way ti accumulate data required to derive the metrics.
- Analysis is the computation of metrics.
- Interpretation is the evaluation of metrics.
- Feedback is the recommendation derived after interpretation.

Metrics characterization and validation includes:
- Metric should have desirable mathematical properties.
- The value of metric should increase or decrease in the manner in which a software characteristic increases when positive trait occurs or decreases when undesirable traits are encountered.
- Metric should be validated empirically.


Facebook activity