0% found this document useful (0 votes)
49 views2 pages

Agile Software Development Principles

The document summarizes key aspects of agile software development principles and methods. It outlines the 12 principles of the Agile Manifesto which emphasize satisfying customer needs through early delivery, welcoming changing requirements, frequent delivery of working software, collaboration between business and development teams, self-organizing teams, face-to-face communication, measuring progress through working software, sustainable development pace, technical excellence, simplicity, emergent design, and regular reflection and adjustment. It also includes figures and tables on business goals, architectural decisions, responsibilities of project managers and architects, and the relationship between architecture effort and rework.

Uploaded by

rm
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
49 views2 pages

Agile Software Development Principles

The document summarizes key aspects of agile software development principles and methods. It outlines the 12 principles of the Agile Manifesto which emphasize satisfying customer needs through early delivery, welcoming changing requirements, frequent delivery of working software, collaboration between business and development teams, self-organizing teams, face-to-face communication, measuring progress through working software, sustainable development pace, technical excellence, simplicity, emergent design, and regular reflection and adjustment. It also includes figures and tables on business goals, architectural decisions, responsibilities of project managers and architects, and the relationship between architecture effort and rework.

Uploaded by

rm
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Figures and other key details

Wednesday, April 3, 2019 12:06 PM

Figure 23.1. Business goals, architectural decisions, costs, and benefits

Results of the CBAM Exercise

Table 22.1. Division of Responsibilities between Project Manager and Architect

Manifesto for Agile Software Development


We are uncovering better ways of developing software by doing it and helping others do it.
Through this work we have come to value:

That is, while there is value in the items on the right, we value the items on the left more.
[[Link]]
The authors of the Manifesto go on to describe the twelve principles that underlie their
reasoning:
1. Our highest priority is to satisfy the customer through early and continuous delivery
of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness
change for the customer’s competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months,
with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.

Quick Notes Page 1


4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and
support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and
users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity—the art of maximizing thev amount of work not done—is essential.
11. The best architectures, requirements, and designs emerge from self-organizing
teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes
and adjusts its behavior accordingly.

Figure 15.1. Architecture effort vs. rework

Quick Notes Page 2

You might also like