Essays collection 2012
Home Home SK
"metrics"
Baďura Filip

Abstract. Every day thousands of people work on development of thousands of software projects. To insure, that a reasonable cost and adequate time are spent on development of these projects, it is necessary to control this development. And it is part of management of project – monitoring, that serves to us, so that we don't waste a time and costs. Monitoring of project helps us to keep project on schedule and avoid unnecessary problems in its development. However, if we want to monitoring project, we need to determinate how to do it, what to look for and which metrics to use.


Habdák Martin

Abstract. Monitoring is often used for better project planning. It follows the state of the project and helps to uncover errors which cause problems in software development. Monitoring provides a view on team behavior too. We can rate it on the basis of collected data. Results can be inaccurate when improper metrics are used. This Essay describes how can such a vagueness lead to bad relationships in a team. Many well established metrics can be used by the team members to pretend that they have done more work. Therefore various conflicts emerge. They tend to reflect on the project development. Team morale and efficiency is also reduced. Project managers often use easy to follow metrics, which incite such team problems. This essay shows that such metrics are unsuitable and presents alternatives to their use.


Obal Tomáš

Abstract. The author of this essay attend to the importance of monitoring software projects. Author proposes to add human-use reporting with metrics which are objective source of information. The introduction shows the possible ways of monitoring and resources for gathering metrics. For creating the plan is to use metrics included in the analysis, which must be measured to express the size of the project. The focus is on control and porogresu porductivity work in the development of software projects. The second section is devoted to monitoring quality control of source code with the complexity of functions and classes. By providing a proposal to use a minimum number of metrics to ensure good performance in project development.


Left Separator
monitoring software project metrics function points plan planning software product risk management test driven development error effective communication sofware metrics software development team problems development software quality development support management extreme programming pair programming Scrum communication relations control progress subversion git critical path method project planning estimation agile development risks motivation requirement collection testing use case points support tools support tools outsourcing team size estimation version management quality cooperation risk documentation project software versioning conflict