Please Provide The Mapping Between The Agile Values and Agile Principles in Two Column Table Format.

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 2

Duygu ERSOL

Student Number:2459600

SM 522- AGILE SOFTWARE DEVELOPMENT


ASSIGNMENT 1
“Please provide the mapping between the agile values and agile principles in two column
table format.”
ANSWER OF ASSIGNMENT 1
The four values of Agile Manifesto are;
1) Individuals and Interactions Over Processes and Tools: Valuing people more highly
than processes or tools is easy to understand because it is the people who respond to
business needs and drive the development process. If the process or the tools drive
development, the team is less responsive to change and less likely to meet customer
needs.
2) Working Software Over Comprehensive Documentation: The Agile Manifesto values
documentation, but it values working software more.
3) Customer Collaboration Over Contract Negotiation: The Agile Manifesto describes a
customer who is engaged and collaborates throughout the development process,
making. This makes it far easier for development to meet their needs of the
customer.
4)  Responding to Change Over Following a Plan: Agile’s view is that changes always
improve a project; changes provide additional value.
The Twelve Agile Manifesto Principles are;
1) Customer satisfaction through early and continuous software delivery: Customers
are happier when they receive working software at regular intervals, rather than
waiting extended periods of time between releases.
2) Accommodate changing requirements throughout the development process: The
ability to avoid delays when a requirement or feature request changes.
3) Frequent delivery of working software: Scrum accommodates this principle since the
team operates in software sprints or iterations that ensure regular delivery of
working software
4) Collaboration between the business stakeholders and developers throughout the
Project: Better decisions are made when the business and technical team are aligned.
5) Support, trust, and motivate the people involved: Motivated teams are more likely
to deliver their best work than unhappy teams.
6) Enable face-to-face interactions: Communication is more successful when
development teams are co-located.
7) Working software is the primary measure of progress: Delivering functional
software to the customer is the ultimate factor that measures progress.
8) Agile processes to support a consistent development pace: Teams establish a
repeatable and maintainable speed at which they can deliver working software, and
they repeat it with each release.
9) Attention to technical detail and design enhances agility: The right skills and good
design ensures the team can maintain the pace, constantly improve the product, and
sustain change.
10) Simplicity: Develop just enough to get the job done for right now.
11) Self-organizing teams encourage great architectures, requirements, and designs:
Skilled and motivated team members who have decision-making power, take
ownership, communicate regularly with other team members, and share ideas that
deliver quality products.
12) Regular reflections on how to become more effective: Self-improvement, process
improvement, advancing skills, and techniques help team members work more
efficiently.

According to these Agile Values and Principles mentioned above, the relation table
between the Agile Values and Agile Principles is shown below in Table 1.

Table 1. Mapping between the agile values and agile principles

Agile Values Related Agile Principles


1 4,5,6,8,10,11,12
2 1,3,7
3 1,2,3,4,8,10
4 2,8,9,12

You might also like