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.
No entries found