The document outlines the principles of Agile software development, emphasizing customer satisfaction through early and continuous delivery, and welcoming changing requirements. It highlights the importance of collaboration between business and development teams, face-to-face communication, and the need for a motivated environment to support effective project execution. Key practices include iterative development, maintaining a sustainable pace, and focusing on technical excellence and simplicity to maximize value.

1. Our highest priority is to satisfy the
customer
through early and continuous
delivery
of valuable software.
Welcome changing requirements, even late in
development. Agile processes harness change
for
Individuals and interactions over the customer's competitive advantage.
processes and tools Deliver working software frequently,
from a
Working software over comprehen- couple of weeks to a couple of
sive documentation months, with a
Manifesto preference to the shorter timescale.
Customer collaboration over contract negotiation Business people and developers must
work
together daily throughout the project.
Responding to change over following a plan
Build projects around motivated
individuals.
Scrum Master Give them the environment and
support they need,
Product Owner Roles and trust them to get the job done.
Team The most efficient and effective
method of
12 Principles conveying information to and within
User Stories a development
Estimates in Ideal Hours team is face-to-face conversation.
Requirements
As <a specific user> I want <something> Working software is the primary
so I can achieve <specific value> measure of progress.
Scrum Checklist
Agile processes promote sustainable
Have newspaper heading like goal development.
The sponsors, developers, and users should be
Planning meeting: 1-6 hrs able
to maintain a constant pace indefinitely.
Product demo Sprints
Retrospective Continuous attention to technical
excellence
Definition of DONE and good design enhances agility.
Simplicity--the art of maximizing
Product vision exists the amount
of work not done--is essential.
Project budget is allocated Assumptions
The best architectures, requirements,
Full-time allocation of team members and designs
emerge from self-organizing teams.
Empiricism At regular intervals, the team
reflects on how
Time boxing
to become more effective, then
Self-organisation Foundations tunes and adjusts
its behavior accordingly.
Collaboration
Prioritisation
&{MAP_NAME} - 28/04/2010 - Mindjet