Hardware Reference
In-Depth Information
a software development process in which agile practices are used. Finally, some
conclusions and future work are presented in section 5.
2 Background
2.1 CMMI Overview: CMMI v1.2
CMMI for Development [22] is a reference model that consists of best practices
that address development and maintenance activities applied to products and
services. CMMI-DEV contains practices that cover project management, process
management, systems engineering, hardware engineering, software engineering,
and other supporting processes used in development and maintenance.
2.2 ASD Overview: Scrum
Agile methodologies provide the infrastructure (i) to evaluate the state of the
product, (ii) to identify new changes in the development process, and (iii) to
incorporate them in the final product by means of continuous integration. There
are different agile methodologies such as Scrum [28] or eXtreme Programming
(XP) [29]. Each one of them defines their own techniques for planning, estimat-
ing, or reviewing, but all of them are based on the same values defined by Agile
Manifesto. Even, some of them share some practices, for example requirements
in agile are captured as User Stories (US) [30]. The US objective is to reduce
the cost of the requirement elicitation and management by means of scenarios
written by customers without techno-syntax versus conventional methodologies
based on formal requirements specification documents. These previous guide-
lines have offered a general vision of agile methodologies but this work has been
focused on the Scrum methodology. Following Scrum is described in detail.
Fig. 1.
Scrum Lifecycle
Scrum implements an iterative, incremental life cycle (see Figure 1) which
involves three stakeholders: the
Product Owner
,the
Team
,andthe
ScrumMas-
ter
[28]; all together make up the
Scrum Team
. The Scrum life cycle defines
a pre-game phase at the project beginning; planning, review, and retrospective
meetings in an iterative way; and daily meetings during the whole iteration. The
