Database Reference
In-Depth Information
should be developed. One stack has an ordered set of features for the whole system, and the
other has those features to be executed in the current 30-day sprint. Scrum involves frequent
management activities and daily meetings called scrums in order to identify and correct any
defi ciencies or obstacles in the development process. Scrum defi nes team members' roles
and responsibilities and is suitable for small teams up to 10 people.
Adaptive Software Development
Adaptive Software Development (ASD) was developed by Jim Highsmith and published
in Higsmith (2000). Many of ASD principles are derived from Highsmith's earlier research
on iterative development methods. ASD focuses mainly on the problems in developing
complex, large systems. The method strongly encourages incremental, iterative develop-
ment with constant prototyping. ASD suggests the importance of collaborating teams and
teamwork and building an adaptive organizational culture, but proposes very few practices
for day-to-day software development work. That is why there is a space for this method to
be accompanied with the development practice of XP, for example. ASD process includes
three phases— Speculate
three phases— , Collaborate and Learn —performed in the cycles. ASD is explicitly
feature-based (or component-based) rather than task-oriented, which means that the focus
is on results and products rather than the tasks for producing them. ASD does not propose
the team structure in details, and does not enforce that the team member must be co-located
like most other agile methodologies.
three phases— Speculate
Crystal Method Family
The Crystal family of methodologies includes a number of different methodologies, as
well as principles for tailoring them to fi t into the varying nature of different projects (Cock-
burn, 2002). The family consists of four methods—Clear, Yellow, Orange, and Red—with
the principle, 'the darker the color, the heavier the methodology'. There are certain rules,
features and values that are common to all Crystal methods. The projects always use in-
cremental development cycles with a length between one and three months. The emphasis
is on communication and cooperation of people. Crystal methodologies do not limit any
development practices, and therefore can easily adopt XP practices. The Crystal methods
use the common work products from XP, such as stories/use cases, screen drafts and design
sketches. Crystal Clear is suited for small projects and small co-located teams (up to six
developers) with precisely defi ned roles. Cockburn's Crystal Family is now merged with
Highsmith's Adaptive Systems Development.
Dynamic Systems Development Method
Dynamic Systems Development Method (DSDM) was developed in 1994 in United
Kingdom as a framework for rapid application development (RAD) (Stapleton, 1997, 2003).
DSDM is a non-profi t and non-proprietary framework maintained by the DSDM Consor-
tium (DSDM, 2003). DSDM has underlying principles that include active user interaction,
frequent deliveries, empowered teams and testing throughout the life cycle. Three major
phases of DSDM—functional iteration, design-and-build iteration and implementation—are
themselves iterative processes. DSDM suggests making a series of prototypes in short cycles
to gradually solve the problems that are not precisely defi ned in advance, or not stable dur-
ing that time. DSDM does not offer detailed documentation of its work products; rather, a
Search WWH ::




Custom Search