Name
Abstract | ||
|---|---|---|
In the recent years, the amount of metrics collected and monitored in a project has been grown. This increases the time and effort required to create and track the success of an organization or of a particular activity, but often does not lead to an improvement in project management. In this article we will show a different approach to finding those essential metrics that should not be missing in any project status report, especially for smaller teams or application projects. We will show how to obtain a complete list of generally useful metrics per process (taking into account the VDA scope) and how to extract from this list the two or three key metrics per process based on a risk evaluation to finally arrive at a lean metric framework. The processes Change Request Management (SUP.10) and Software Requirements Analysis (SWE.1) are used as examples described in detail. |
Year | DOI | Venue |
|---|---|---|
2020 | 10.1007/978-3-030-56441-4_49 | EuroSPI |
DocType | Citations | PageRank |
Conference | 0 | 0.34 |
References | Authors | |
0 | 6 | |
Name | Order | Citations | PageRank |
|---|---|---|---|
| Bernhardt Steger | 1 | 0 | 0.68 |
| Damjan Ekert | 2 | 67 | 16.41 |
| Richard Messnarz | 3 | 449 | 77.94 |
| Jakub Štolfa | 4 | 13 | 10.23 |
| Svatopluk Štolfa | 5 | 25 | 13.96 |
| Zdenek Velart | 6 | 0 | 0.34 |