2.

1 Agile principles

1. Customer satisfaction by early and continuous delivery of valuable software

The first agile principles which is satisfied the customers. To satisfied the customers, the
development team should deliver the product features and functionality that brings value to the
customers. To satisfied the customers is to keep them happy and satisfied by delivering those
requests features from themselves. The satisfaction of customers not only occur in the early
development of system, it is also continuously deliver during the project.

2. Welcome changing requirements, even in late development

In agile principles, it welcome changes of the projects at all time even it is in the late in
development. Changes of requirements helps to ensure the customers get exactly what they need.
Also, the purpose of changes it is just greater to fix requirements at the beginning of the projects.
So, the development teams know what to do and what customers are expected at the end of the
project. One of the reasons of changing in the execution of project is business change. Business
change do not hold when the project is executing. To keep a competitive advantages, it is difficult
to keep no change during the project. It is because in business, new market is explored and the
customers wants to change service and competitors keep on deliver new products and services.

3. Working software is delivered frequently (weeks rather than months)

Deliver working software frequently from a couple of weeks to a couple of months, with a
preference to the shorter timescale. The customer always wants their project delivered as soon as
possible. Frequently deliver working software make sure the development team having the right
scope and agreeing on what can or cannot be delivered with the given resources available. This
principle is also making sure the development iteration stays on time and deliver valuable software
which having backlog that containing all stakeholders and requirements on the system.
4. Close, daily cooperation between business people and developers

This principle is to get client and developers to work closely together to ensure the developer gain
a deeper understanding of the business requirement. Close cooperation helps to discover missing
or incomplete requirement. The best way to ensure a high-quality software is develop, someone
from the respective team should be send to work or cooperate with the developer. Alternative
approach can be considered as one of the way to achieve the principle such as relocate developer
to work in business teams who will be sitting with peoples that are going to use the new system.
The developer can keep focus on the end user since the developer is sitting with the users itself.
(Parkhurst, 2015)

5. Projects are built around motivated individuals, who should be trusted

A company will need to trust the developers since they are the people who will be taking
responsibility of the system of the company. The project manager has to take the position of
dictator for a more collaborative approach so that it would be easier and produce better outcomes.
Probably this is one of the reason project manager role in a traditional sense does not exist in true
agile. There is a need to have someone who will have to takes over the leadership of the overall
project. Usually the focus will shift into defending development team and helps to support their
effort. This can be achieved by recognizing training requirements, ensuring the developers
equipment is equally powerful for the job or simply backup idea. (Parkhurst, 2015)

6. Face-to-face conversation is the best form of communication (co-location)

Face-to-face communication is the most effective and efficient way to convey information to and
within the development team. With the advance of technologies, employees can work at any place
using social media, cloud and mobile technologies. However, face-to-face communication can
make things and requirement clearer and easier to be understand. Understand the problems of the
system is important for developer team to come out with the best solution for the problems. The
advantage of face-to-face communication is to have deeper trust and responsibility can be form
from by reading the body language of each other. Hence, face-to-face communication is very
important to get things done in the most effective way. (Francino, 2016)
7. Working software is the principal measure of progress

The whole project progress is use working software as measurement. The developers need deliver
the functional software to the customers on time, no matter how great was the program, if it doesnt
meet client requirement, it doesnt fill up the progress bar. A good team needs to produce quality
software -- all other measures are pretty much irrelevant if you cant get it working correctly.

8.Sustainable development, able to maintain a constant pace

When the workers working on the same thing for a long period, they will feel exhausted. The
unlimited overtime work cant increase the quality nor quantity of completed task. To prevent this,
Agile methodologies seek work-life balance among the team members and advance satisfaction
by avoiding burnout or exhaustion. The team should focus on choosing the right pace for each
member so that the member can satisfied both the work progress and the life.

9.Continuous attention to technical excellence and good design

Developers shouldnt wait to clean up redundant or confusing code. Code should get better with
each iteration. The team should take time to review their products in meeting, and
these retrospective meetings ensure that the fault founded during the project are corrected in the
next iteration.

10. Simplicity - the art of maximizing the amount of work not done is essential

According to the Pareto principle, 80% of the result can be obtained by 20% of invest input.
(Lavinsky, 2014) It is essential to analyze and identify the unimportant work and eliminate a clear
understanding of work should be done for team, by reducing all the unimportant work can speed
up the progress of development. Developer team can keep track on the work should be done and
avoid doing things that are not related to the project development by using project management
tools such as trello, dashable and InVision, so that the developer team can ensure the completion
of the work. Simplicity basically refers to focus on the essential task.
11. Best architectures, requirements, and designs emerge from self-organizing teams

Self-organizing teams refers to each member in a team knows how to perform task and each of the
members have the responsibility to meet the goal of the project not only the project manager. All
members in a team should know what task they should perform, members should not only wait for
the project manager to ask them work but members should perform task automatically. Members
can ask or wait for the response from project manager when there are some big issue occurs during
the development. Developer team can communicate or interact with other team to exchange
information and share ideas so that the developer team can develop quality products.

12. Regularly, the team reflects on how to become more effectives, and adjusts
accordingly

A product that have been develop for a long period of time does not means that that is a best
product as the project situation and realities keep on changing hence the project teams need to
adjust the team behavior to adapt with the change circumstance. This principle basically means
that if there are any improvement that can be made to the product, the project team should
implement the adjustment to make the product in a better way. In another word, user does not
know how the system behave unless the user have try to use the system and there will be some
changes request from the user, hence project team need to adjust the system according to the
changes request.