Datasheet

Approaches to Project Management
❘
13
Customer collaboration over contract negotiation
Responding to change over following a plan
These are not values in any moralistic way but preferences for working with products, individuals,
teams, and customers on Agile projects. In addition, 12 principles guide Agile software development:
Our highest priority is to satisfy the customer through early and continuous delivery of
valuable software.
It ’ s important to welcome changing requirements, even late in development. Agile processes
harness change for the customer ’ s competitive advantage.
It ’ s important to deliver working software frequently, from a couple weeks to a couple
months, with a preference to the shorter time scale.
Businesspeople and developers must work together daily throughout the project.
An organization should build projects around motivated individuals. Give them the
environment and support they need and trust them to get the job done.
The most effi cient and effective method of conveying information to and within a
development team is face - to - face conversation.
Working software is the primary measure of progress.
Agile processes promote sustainable development. The sponsors, developers, and users
should be able to maintain a constant pace indefi nitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity — the art of maximizing the amount of work not done — is essential.
The best architectures, requirements, and designs emerge from self - organizing teams.
At regular intervals, a team should refl ect on how to become more effective and then tune
and adjust its behavior accordingly.
The following section describes the high - level process that Scrum follows, from planning through
execution.
The Practice of Scrum
Scrum is an iterative software development process. In an iterative process, a product undergoes
many releases, some major and some minor, with each release adding more value to the product.
This type of process enables a team to deliver value to the customer early and to get feedback that
can be quickly incorporated into future product development.
In the Scrum method, the product feature set is defi ned by user stories , which are brief narrative
descriptions of how the product will be used, by whom, and why. As features are scheduled for
development, user stories are decomposed and augmented with increasing levels of detail.
The product release cycle in Scrum is divided into sprints. These are fi xed durations, typically two to
eight weeks, in which all development activities take place. Each sprint produces a potentially shippable
➤
➤
➤
➤
➤
➤
➤
➤
➤
➤
➤
➤
➤
➤
CH001.indd 13CH001.indd 13 3/23/11 2:47:00 PM3/23/11 2:47:00 PM