Metrics In Project Management

1607 Words7 Pages
A metric is a quantitative measure of the degree to which a system, component, or process possesses a given attribute [3]. Metrics can be used for measuring the performance of SP manager. Performance metrics should be objective, timely, simple, accurate, useful, and cost-effective. Performance metrics can be divided into three basic categories [1]: measures of efforts, measures of accomplishments, and measures that relate efforts to accomplishments. • Measures of efforts: Efforts are the amount of resources, in terms of money, people, etc., applied to a project. Examples: The amount of money spent and the number of person-hours burned on a project. • Measures of accomplishments: Accomplishments are milestones achieved with the resources used.…show more content…
They present the common pitfalls that plague all software projects and rookie mistakes that are made repeatedly. They present the tools, techniques, best practices, and practical advices that can be used on software projects for building better software. They cover many performance issues, but they don’t cover performance metrics issues. • Basharat et al. [21] describe different factors that cause the success or failure of projects. Their results present general guidance for project managers to make sure that their projects be successful. This study shows the importance of project management tools and techniques in the industry. It also shows how project management is important for a successful and quality software product. • J. Procaccino and J. Verner [22] examine the mindset of software development project managers with regard to how they define a successful project in order to arrive at a richer perspective of success. They investigated components of the developed system in order to place traditional measures of success in context with other organizational and managerial measures that have been suggested in the literature. They conclude that involvement of users and stakeholders during project development is an important success…show more content…
Verner and W. Evanco [24] surveyed 42 software projects in Australia in order to understand what project management practices are used in these projects. The relationship between practices and software project outcomes enables the authors to investigate why some projects succeed and others fail. They found that nearly 20% of projects had no lifecycle methodology and 10% of the respondents did not understand what was meant by a software development lifecycle methodology. Many recognized software practices are not being applied consistently in the projects investigated. Fifty percent of projects began with unclear requirements. Risk assessment is not normally a part of the development process and the organizations are not learning from their mistakes as post mortem reviews are much more likely to be held for successful projects than they are for failed
Open Document