13 Kick-Starting Development with Practices

In Part II, we saw how a small team kick-started development using Essence. The goal of this chapter is to extend the process with the use of explicit practices to help the team with particular challenges they face. Specifically, in this chapter we show

  • the elements behind kick-starting development with explicit practices, and
  • the role of these elements - at an elementary level—the roles of four popular practices detailed later in the book (i.e., Scrum, User Stories, Use Cases and Microservices).

Furthermore, we demonstrate through our example how a real endeavor can progress as more people and stakeholders become involved.We reflect on the state of our simple endeavor after the demonstration discussed in Part II, and move forward from there. We will learn how the conditions have changed and what effect that has had on the state.

Nowthat our kick-start process will involve not just tacitly agreeing on the things
to monitor as we saw earlier, but agreeing on explicit practices to apply, the kickstart sequence has changed. It is now as follows.

  1. Understand the context through the lens of Essence.
  2. Agree upon development scope and checkpoints (where it begins and where it ends).
  3. Agree upon practices to apply.
  4. Agree upon the important things to watch.

In the remainder of this chapter, we will explain what each of these items means,
and we will describe how teams can use practices effectively in development. As this part of the book progresses, we will see firsthand through TravelEssence’s team the value explicit practices can bring to them over the simpler tacit practices they have used so far.