Part 3 – Small Scale Development with Practices
In this part, we will motivate the need for explicit practices and discuss how explicit practices that are described on top of Essence are used by small development teams to help solve the common challenges they often face. As an example, we have chosen a team that uses an agile approach, but we could have chosen a team that uses a more traditional approach, such as a waterfall approach. Agile development, of course, is the mainstream approach to delivering software at the time of writing this book and is utilized in many organizations. Agile development is not just a method, but rather it is a mindset, with principles as well as practices. Over the years, common agile practices have been codified (i.e., written down), and we explain in this part how to modularize them as practices using Essence. In particular, you will learn how a small agile teammakes use of Scrum, User Stories, Use Cases, and Microservices practices to solve specific challenges they face during their development. This development typically takes several weeks to complete, and we will see how this team evolves their way of working practice-by-practice while working on a list of changes. Now we consider a new and different situation with respect to the TravelEssence development team. We consider it now enlarged with new persons. Also we start with a slightly different development situation which is summarized below (see Chapter 13).
Part III will cover the following objectives.
- Appreciate what practices are, and the types of challenges teams often face where practices can help. We will describe practices including Scrum, User Stories, Use Cases, and Microservices.
- Appreciate the value that representing practices in an essentialized form provides in helping you find the right practices for your team.