Design – Build – Run: Applied Practices and Principles for Production-Ready Software Development

3.2. Development Mobilization

Development mobilization activities ensure that the actual development activities are completely defined and ready to use. The output of development mobilization feeds into a number of other mobilization activities. For example, once you've defined the inputs that you need for development, these will be fed into the design mobilization activities to ensure that they're accounted for. There can be a number of tasks carried out in this mobilization activity that could be split into parallel streams, where necessary.

The previous chapter looked at a high-level development plan and the activities involved. I also discussed scope in the previous chapters, so I'm not going to dwell on what has already been covered. Ultimately, the scope defines the inputs, approach, and outputs of construction. The next chapter looks at some of the inputs and outputs of construction. In this section, I'm simply going to provide some clarity for the scope and approach that will be taken during the formal development activities.

3.2.1. Defining the Development Scope

Initially, it is important to clarify the scope and approach of development. You need to ensure that the development team understands:

• What it needs to be doing

• How it's supposed to be doing it

• What it's using to do it

• When it needs to complete it

• What it needs to deliver at the end

It is important that all the artifacts that the development team is responsible for are clearly stated and understood. It really depends ...