TABLE OF CONTENTS In this chapter, we will look at how a project was planned using the ideas presented in the last chapter on Feature-Driven Development. As you will remember, an FDD project is based on the identification of features, their implementation as tasks (possibly grouped into packages of work) implemented within a fixed time box for each iteration.
Note that, in the context of this chapter, it is not important that you fully understand what each feature represents (indeed with a detailed explanation of the application and the associated business processes they would not be clear, and such topics are outside the scope of this chapter) but rather that you see how such a project planning process evolves and how the different aspects of the process relate.
The remainder of this chapter is structured in the following manner. In Section 10.2, we will consider how this project started off. In Section 10.3, we will discuss the overall project plan. Section 10.4 describes how the first iteration was planned. Section 10.5 then briefly addresses what happened post iteration 1 delivery.
The particular project being considered is a real system (with names changed to protect the innocent). One interesting aspect of this system was that it was based on an earlier system that we had implemented for the clients. The previous system had been implemented some time before in a non-agile manner. The resulting software worked, but by now the client's requirements had moved on. The new project...
