There is a consensus that the controlcontrol and management management of any process and activity can be improved by using measures to monitor its performance. In general, software engineering is a discipline that acknowledges products measures as well as measures of the development process. Specifically, the agile approach promotes a constant tracking during the entire process of software development. For example, the team velocity explained in Chapter 4, Time, is one of the important ways to control the project’s progress. Further, the tracker role is responsible for the definition and refinement of the team measures, for the collection of the required data, and for the measure presentation. Some measures are presented daily, like the daily progress within the iteration; some measures are presented every iteration, like code coverage or iteration progress within the release; yet other measures are presented every release, like customer satisfaction or level of product testability. By using measures on a regular basis, all teammates and stakeholders can view them, give feedback, and suggest refinements, and thus become accountable for the project development.
- BeckBeck K K, FowlerFowler M M (2000) Planning extreme programming. Addison-Wesley, Reading, MAGoogle Scholar
- CohnCohn M M (2006) Agile estimating and planning. Robert C. Martin Series, Prentice Hall PTR, Englewood CliffsGoogle Scholar
- Dubinsky Y, Yaeli AYaeli A, Feldman YFeldman Y, Zarpas EZarpas E, Nechushtai GNechushtai G (2008) Governance of software development: the transition to agile scenario, IT governance and service management frameworks and adaptations. Idea Group Publishing, Information Science Publishing, IRM PressGoogle Scholar
- Hazzan O, LeronLeron U U (2006) Why do we resist testing? System Design Frontier 3(7): 20–23Google Scholar
- TalbyTalby D D, Hazzan O, Dubinsky Y, Keren AKeren A (2006) Agile software testing in a large-scale project. IEEE Software, Special Issue on Software Testing, pp 30–37Google Scholar