TodAY, AS ALWAYS, many different initiatives are
under way to improve the ways in which software is
developed. The most popular and prevalent of these
is the agile movement. one of the newer kids on
the block is the Software Engineering Method and
Theory (SEMAT) initiative. As with any new initiative
people are struggling to see how it fits
into the world and relates to all the
other things going on. For example,
does it improve or replace their current ways of working? Is it like lean,
which supports and furthers the aims
of the agile movement; or is it more
like waterfall planning, which is in opposition to an agile approach?
Many have wondered whether SEMAT and agile are complementary or
competitive initiatives, and if they are
complementary, how do they fit together? In this article we demonstrate
how these two initiatives support each
other and we discuss the benefits of
using them together.
Generally speaking, both initiatives
promote non-prescriptive value-based
philosophies that encourage software
development teams to select and use
whatever practices best fit their con-
text and, more importantly, continu-
ously inspect, adapt, and improve their
ways of working. These two initiatives
complement one another, providing
the perfect foundation for teams that
want to master the art of software de-
The agile movement has provided a
new way of looking at the day-to-day activities of software development—how
teams are built and work is organized.
This has led to the empowerment of development teams and the prominence
of agile practices (such as Scrum and
test-driven development) as the modern developer’s practices of choice.
Article development led by
Combining agile and SEMAT yields more
advantages than either one alone.
By iVaR JaCoBson, ian sPenCe, anD Pan-Wei nG