Page 202 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Principles of Software Engineering

Notes for activity 5.2 Plan the measurement process, we used the Goal/Question/Metric (GQM)
methodology originally developed by Basili and Weiss since it has been widely used over
more than two decades, it is simple to use, and very effective.

Phase described in the ISO/IEC 15939 standard
Clause number and name Main outcome
5.1: Establish and sustain • Management commitment and
measurement commitment responsibility, team roles
5.2: Plan the measurement process • Selected metrics definition
5.3: Perform the measurement • Metrics program implementation
process results
5.4: Evaluate measurement • Metrics analysis and validation
We also took a look at the IEEE Standard for a Software Quality Metrics Methodology that
describes a very similar process to the one defined in the ISO/IEC 15939 standard except that
it consists of five phases instead of four. Finally, we also for Software Productivity Metrics
as a guideline to identify some productivity metrics.
Related Work
The academic literature is abundant on case studies about implementing metrics programs
in software organizations. However, for the purpose of this, our particular interest focused
on recent works associated with applying metrics in agile organizations. Many works have
been published on this issue. Most recently proposes a quality model and a set of metrics for
agile software development organizations and discusses the problem of trying to implement
conventional metrics models in agile organizations. In the present a similar experience
but using object-oriented metrics as part of their agile methodology. In a similar line of
work, presents an exercise in validating three different sets of object-oriented Experience of
incorporating software metrics practices into an iterative commercial.
The Organization
Round Box Global (RBX) originated in 2003 in Atlanta, Georgia, USA. Since 2006, the
company has a 90-person development team in San Jose, Costa Rica. The organization
develops mainly Java web applications for corporate education and training programs. The
several development teams are supported by a project management infrastructure along
with a quality assurance group.
RBX uses Scrum, one of the best known agile methodologies. Scrum proposes a process
model comprising a set of practices and roles that can be used as a guide line to define a
software development process. There are three main roles: The Scrum Master maintains the
process and acts as project manager, The Product Owner represents the stakeholders and
The Team includes all the participating developers.
At each sprint, which lasts between 15 and 30 calendar days, the team develops deliverables
software increment. The Product Backlog, a prioritized list of high-level software requirements,
defines the functionality to be implemented in each increment.
For each sprint, and during the Sprint Planning meeting, the Product Owner requests
requirements from this list to the team, whose members determine the quantity of work that
can be developed during the sprint? During a sprint, the Sprint Backlog can no be changed
thus a requirements baseline can be defined.
Agile organizations that use Scrum generally would have a matrix structure where each
project team would have the mixture of people from various Departments with the skills
required for each sprint (e.g., project manager, developer, programmer, quality assurance
engineer). Each individual in a team would belong to a different but work under a single
Scrum Master for a particular project. The organizational process, depicted.
Contd...

196 LOVELY PROFESSIONAL UNIVERSITY