Preface What FDD Is! Feature-Driven Development (FDD) is a process designed and proven to deliver frequent, tangible, working results repeatedly. This is the first book to spell out the day-to-day details of using FDD on a real project, giving development team leaders all the information they need to apply FDD successfully to their situations. FDD is a straightforward approach to producing systems that uses simple, easy-to-understand and easy-to-implement methods; problem-solving techniques; and reporting guidelines providing every stakeholder of a project with the information they need to make sound, timely decisions. Programmers are provided with the information and supporting infrastructure they need to produce applications. Team leaders and managers get timely information about their teams and projects that allows them to reduce the project risk . Project managers and executive sponsors see the current project status and trouble areas so that they can actually make timely, informed decisions in a controlled, planned manner (no knee-jerk reactions). Reporting becomes easy, relatively painless, timely, and accurate ! Users (customers, sponsors, end users) can actually see areas of their business automated as the project progresses and give early, constructive feedback about the system while it is being developed. At the same time, the development team has the tools and information it needs to control "scope creep!" What FDD Is Not ! FDD is not yet another process that takes up resources, time, and money but just doesn't produce the needed results. It is not another method whereby administrators, bureaucrats, and process-centric fanatics can focus everyone's time and energy on producing reams of printouts and signatures with nothing to show for it. FDD is not another set of process volumes that will sit on your shelf, collecting dust and impressing your supervisor, co-workers, and significant others with your knowledge of another less-than-useful set of directions for producing systems. Why Should I Read this Book? (What's in it for Me ?) If any of the following questions apply to you, you will find the answers you are looking for on the following pages: Are you in charge of a group assigned to deliver a critical system with limited resources and short deadlines, and need help to organize the project? Are you tired of filling out so many process forms and reviewing so many documents that you don't have time to do your real work? Are you frustrated at the unfulfilled promises of process initiatives that claim to provide a way to deliver quality results repeatedly? Are you looking for a more efficient way to organize your team to streamline productivity, cut down on unnecessary interruptions, and improve the accuracy of reporting for your projects? Are you currently working on a project that is in trouble because the team has failed to produce a system? Do you want to add to the tools and techniques in your project management or team leader toolbox? Prego (It's in There!) Although FDD was first introduced in print in Java Modeling in Color with UML Coad 99, we give a more thorough coverage of the topic. We point out the critical tips for success, as well as the pitfalls that may not be apparent from a cursory glance. Contents include: Who should use FDD The roles, artifacts, goals, and timelines Why FDD includes the practices and techniques that it does The driving forces behind the development of FDD Adapting the use of FDD to different styles of projects FDD blends a number of industry-recognized best practices used successfully by Peter Coad, Jeff De Luca, and others in their consultancies. These practices are all driven from a client-valued feature perspective. It is the potent combination of these techniques and practices that makes FDD so compelling.