AGILE PRINCIPLES

BATCH 30 B3
 AGILE PRINCIPLE-1

EARLY DELIVERY OF THE PROJECT

• Our highest priority is to satisfy the customer through early and continuous delivery of
valuable product.

BATCH 30 B3
 Example

Construction of house.

Requirement of customer : Build a house with required design.

Task of constructor : To satisfy the customer by building the house with their design.

 In this scenario, in order to fulfil the customer’s request, the constructor should build
the house within given time limit. The only way to achieve this is using agile methodology -
Early delivery of the project.

 To achieve this, the parts of constructing house should be divided into groups and
simultaneously the group should work accordingly. Then only we will be able to deliver the
project in time.

In this way, the organization should also work accordingly and complete the task in time.

BATCH 30 B3
 AGILE PRINCIPLE-2

ADAPT TO CHANGE

 Welcome changing requirements, even late in development. Agile processes harness

change for the customers competitive advantages.

 The goal is how about the development team is flexible to adapt the changes in last
stage of development and implement it.

BATCH 30 B3
 Example

 In an evening, mom has decided to cook chapathi and prepared the dough. But,
suddenly the guest has come, so mom decided to make something special.

 Now to make something special, mom has added some rava and salt to the
dough and made puri to the guest. Instead of replacing the whole dish, mom just
added few more things according to the requirements.

 This is similar to the organisation, we have to adapt to the changes and should
fulfill the requirements.

BATCH 30 B3
 AGILE PRINCIPLE-3

FREQUENT DELIVERY

 Deliver working software frequently, from a couple of weeks to a couple of

months, with a preference to a shorter time scale.

BATCH 30 B3
 Example

 In this scenario, mom is preparing aloo paratha. In the initial stage of

preparing the dough, mom asks to taste and makes any changes if necessary and later,
mom starts preparing the stuff for the snack, now she asks again to see whether the
correct blend has come. If the snack is all good, then mom completes doing it.

 Like this, frequent delivering project to the client in steps and asking for feedback
in each initial stage is required for efficient ending of the product.

BATCH 30 B3
 AGILE PRINCIPLE-4

BUSINESS AND DEVELOPERS COOPERATION

 Collaboration is key to agile project management. Business people and

developers must work together daily throughout the project.

 As mentioned, collaboration is key to agile project management, when the project

stakeholders communicate on a daily basis. It minimizes the risk of confusion and
ensure that everyone’s goal remain align.

BATCH 30 B3
 Example

 If a person from another state comes and open a restaurant in another state. For
the restaurant, he should hire staff for cleaning, chopping and preparing food.

 For a healthy business, he should collaborate with all the staff and should get
aware of all the customs and traditions of the state. If all the staff members
cooperate with the master, then he can have successful business.

 In this way, if the people in the team work together, they can achieve a healthy
profit and reduces the confusion.

BATCH 30 B3
 AGILE PRINCIPLE-5

MOTIVATED INDIVIDUALS

 Build projects around motivated individual, give them the environment support
they need and trust them to get the job done.

 The principle has two key points – 1. Motivated individual 2. Trust

Building projects around motivated individuals can complete our work faster, with better
quality in an efficient way.

BATCH 30 B3
 Example

 Imagine a scenario, where the superior is continuously asking about whether the
work has completed or not. In such case, the person will loose the interest in doing
the work.

 Instead if the superior build a trust on him and gives him some space,
responsibility for the way they want to do it, then the person will get motivated and
he can complete the task in time.

 In a organization, trust is the pillar of success.

BATCH 30 B3
 AGILE PRINCIPLE-6

FACE-TO-FACE INTERACTION

 The most efficient and effective method of conveying information within a

development team is face-to-face conversation.

 Barriers are broken easily when teams can converse in person. It promotes good
communication and boost the flow of information.

BATCH 30 B3
 Example

 Lets have an example of online applications like zoom app, which is widely used
for communication.

 But why zoom ? We can discuss everything on a normal phone call, but if we do
so, there will not be effective communication -we cannot understand the person’s
perspective which may leads to misunderstandings.

 But if we use applications like zoom which are provided with features like
camera, where we can have a face-to-face interactions and do our work efficiently.

 In this way in an organization, face-to-face interactions reduces

misunderstandings, creates a bond and friendly vibe among people.

BATCH 30 B3
 AGILE PRINCIPLE-7

WORKING SOFTWARE

Working software is primary measure of progress.

 Working module is far better than documentation. Product manager should

have more focus on minimizing paperwork and maximizing productivity.
Unfinished software has no value.

BATCH 30 B3
 Example

 Lets take an example of tata nano car, when it was announced that the price of
the car is 1 lakh, it created a buzz in market. The product was launched
successfully.

 The major change was made is the software. They has shifted the engine
backside, and in the tyres they have used three screws instead of four. By making
the changes in software, the price of the car has reduced and rated good by
customers.

 So, by having efficient software we can mould the product in an efficient way.

BATCH 30 B3
 AGILE PRINCIPLE-8

SUSTAINABLE DEVELOPMENT ENVIRONMENT

 Agile processes promote sustainable development. This principle invites

teams to commit a constant pace.

 The sponsors, developers, and users should be able to maintain a constant

pace indefinitely.

BATCH 30 B3
 Example

 Let us imagine , where there is a marathon between A and B for 3 km.

 ‘A’ intension is only to win the race, so as soon as race started, ‘A’ started running very
fast and after 2 km ‘A’ has exhausted and now he unable to run fast. Whereas, ‘B’ started
running the race with a constant pace and at last ‘B’ won the race.

 Therefore, maintaining constant pace gives efficient result.

BATCH 30 B3
 AGILE PRINCIPLE-9

TECHNICAL EXCELLENCE

 Focusing on enhancing technical skills improves agility.

 Goals of agility are to go deliver software of higher quality, faster, with a

higher acceptance to end-users and able to follow the changing business
requirements to strive for competitive advantage.

BATCH 30 B3
 Example

Scenario:

There are two developers namely A and B.

(1) A person have knowledge of Java. He does not know any other languages.
(2) B person have knowledge of Java and Python.

 In future if any Python project comes then B will get more chances to work
rather than A.

BATCH 30 B3
 AGILE PRINCIPLE-10

SIMPLICITY

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

The simplicity in designing the project welcomes easy understanding.

BATCH 30 B3
 Example

 Delivery boy A has to deliver three products at different locations D,E,F…

from the shop Dmart.

 For saving time, the delivery boy should ensure that whether he has
following simplicity or not. The delivery boy should deliver the products first at
the destinations D and E, then he should go for destination F.

 It also works same for the organization, we should simplify the work
instead of making complex.

BATCH 30 B3
 AGILE PRINCIPLE-11

TEAMS SELF ORGANIZING

 The best architectures, requirements, designs emerge from self-organizing

teams.

 For better result, we have to coordinate with the team, then only the best
outcome can come.

BATCH 30 B3
 Example

Scenario:
There are two teams named A and B.

(1) Team A is self-organized and working with collaboration.

(2) Team B is not self-organized and having disputes in teams.

So, if they both are assigned with the same project and lets imagine the project has
two segments and two teams should finish the project .
With organized manner, team A has divided the segments of work and
completed. But where as team B with the missing coordination, both the teams has
done the same segment of work and everything gone in vain.

Here, for an company team self organization plays a vital role.

BATCH 30 B3
 AGILE PRINCIPLE-12

REFLECTIONS AND ADJUSTMENTS

 At regular intervals, the team reflects on how to become more effective, then
tunes and adjusts its behaviour accordingly.

BATCH 30 B3
 Example

 The team A done the project named ABC recently, in which they had delivered
ludo game. In which, the dice has the problem of not showing the number 6 and
later they resolved the issue.

 Later they got another project of designing the game that also includes a die.
This time, they didn’t repeat the mistake which was done previously and they have
learned from the mistake.

BATCH 30 B3
 END

BATCH 30 B3