NO:7"8$

!"#$%E$%$<=&a_$?5:6&A*(7
ZT9L&XE&T[\\WB] !B^_N`L&>9,9\W>W,L !B^HW`L&>9,9\W>W,L `^GG9K^B9LX^, EL9BL&)^B&)BWW
O7*P5%$a&56&=@$&4$6(&=*&<7$"=$
"&O$7?*6"%5b$8&?O"<$S

\*=&5=

!"#$%&'(")*"+,'"-./%'"0$1/*'(+)
$12"34"-./%'"56/17/8%'("9$(/%:
9;8%$/1'2
!"#$%&'( )*%%*+
,*#&-./&0.12&·&3&456&7$"8

What was before the famous “Agile Manifesto”? It is rather di:cult to

imagine but there were many software solutions that had been born before
it.

Before the “Manifesto,” software development was not so fast. Many

projects in the pipeline were canceled due to changing business needs. The
software development industry was prime for disruption. 12 principles of
Agile software sought to change things, speed up development time, and a
produce a quality.

The Agile Manifesto is the base of the Agile transformation movement. Here
I brieHy describe the four values and twelve principles that lead to higher-
quality software delivered to satisJed customers on a continuous basis.

!"#$%#&'%$"'%&(($)*
As any framework or methodology, Agile also has its own history. In the
1990s, several methodologies with a diNerent combination of diNerent old
and new ideas began to gain public attention.

The methodologies highlighted close collaboration between business

stakeholders and developments and meant the frequent delivery of
business value and self-organizing teams.

“Agile” as the term was applied to this set of methodologies in 2001.

It was the collaboration of 17 software developers who gathered in Utah,

USA, to discuss their ideas and diNerent approaches to software
development. Their smart thoughts were expressed in the famous Agile
Manifesto that included 12 principles.

The Agile Manifesto consists of 4 foundational values and 12 supporting

principles that lead the Agile approach to software development.

Each Agile methodology applies the 4 values in diNerent ways. However, all
of them rely on these values to guide the development and delivery of high-
quality, working software.

+%,#-.')%(/%$"'%012-'%3#42/')$(
56%7482,28.#-)%#48%24$'&#9$2(4)%(,'&%:&(9'))')%#48%$((-)
The value #1 in the Agile Manifesto is known as “Individuals and
interactions over processes and tools.” It’s crucial to value people more
highly than processes or tools. It is the people who respond to business
needs and drive the development process. When the development is driven
by the process or tools, then the team is less responsive to changes and less
likely to meet customer needs.

;6%<(/$=#&'%(,'&%8(9.>'4$#$2(4
Historically, documenting the product for development and ultimate
delivery required enormous amounts of time. Technical requirements,
speciJcations, prospectus, testing plans, interface design documents, and
diNerent approvals were required for each. There were long delays in
development.

Agile streamlines documentation, not eliminating it. In this form, it gives

developers what they need to do without getting bogged down in minutiae.
Agile values documentation, but it values working software more.

?6%@.)$(>'&%9(--#A(&#$2(4%(,'&%9(4$&#9$%4'1($2#$2(4
Negotiations are important. It’s about the period when customers and a
product manager work out the details of a delivery with all the details.
However, collaboration is a diNerent creature entirely and it really matters.

According to Waterfall, customers negotiate the requirements for the

product, often in great detail, prior to any work starting. The Agile
Manifesto describes a customer who collaborates throughout the
development process, making. It’s easier for development to meet their
needs of the customer.

According to Agile methods, the customer may be included at intervals for

periodic demos, but a project could just as easily have an end-user as a daily
part of the team.

+6%B'):(48241%$(%9"#41')%(,'&%/(--(=241%#%:-#4
Traditional software development regarded change as an expense. It was to
be avoided.

According to Agile, the shortness of an iteration means priorities can be

shifted from iteration to iteration and new features can be added into the
next iteration. Changes always improve a project and provide additional
value.

5;%:&2492:-')%(/%012-'%8','-(:>'4$
These principles can be your litmus test to deJne whether or not you’re
being Agile. So, always remember them in a short form:

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.

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 e:cient and eNective 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
indeJnitely.

9. Continuous attention to technical excellence and good design enhances

agility.

10. Simplicity — the art of maximizing the 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 reHects on how to become more eNective,
then tunes and adjusts its behavior accordingly.

C)'%#::&(:&2#$'%:&(D'9$%>#4#1'>'4$%$((-)%$(%1'$%)$#&$'8%=2$"%012-'
Hygger is a powerful task and project management tool with collaboration
features that are crucial for Agile project management. With its help, you
can make real-time updates and alert your team about the new changes,
share your plans with internal and external stakeholders to increase
transparency and keep everyone on the same page.

The following tutorials will be helpful if you decide to rub your projects
with Hygger:

How to do Kanban with Hygger Software?

How to Do Scrum with Hygger Software?

9:5%$ !7*;$<=&>"6":$4$6= !7*;$<=? 9:5%$&>$=@*8*%*:A >$=@*8?

1-&<%"O? 1&7$?O*6?$

ZBXLLW,&K[

I#,'-%J. )*%%*+

>"7R$=56:&<*6=$6=&4"6":$7

KH11'&62( )*%%*+

X6?5:@=P(%&?=*75$?&P7*4&TA::$7&=$"4

3(&'%E&(>%3'82.>

B$%"=$8&7$"8? 9%?*&="::$8&9:5%$&>$=@*8*%*:A B$%"=$8&7$"8?

<,:"=)>?/'"@76&>"A'$>("B)1C+ E'(+"-./%'"56)F'7+"0$1$.'>'1+ J)K"+)"6'K$62"/12/H/2&$%

@,/8"D$(+ 0'+,)2)%).:"*)6"G)G"-88 8'6*)6>$17'"/1"-./%'"+'$>(
C*4D5$&E<7(4&B$?5?=F&G5D$7"=*7? B'H'%)8>'1+"/1"4I43 K@(+"6&H"56&56&N6F&>"6":$4$6=
1-3 3II
H(%&I/&0.0.&·&J&456&7$"8
G5D$7"=*7? H(6&1-/&0.1M&·&2&456&7$"8
>"6":$4$6=
K*L7$$L$<@6*%*:5$?
>"7&1M&·&J&456&7$"8

F'#&4%>(&'6 3#G'%3'82.>%H(.&)6 <"#&'%H(.&%$"24G2416

>$85(4&5?&"6&*O$6&O%"=P*74&+@$7$&1Q.&45%%5*6&7$"8$7?&<*4$ )*%%*+&=@$&+75=$7?/&O(D%5<"=5*6?/&"68&=*O5<?&=@"=&4"==$7&=*&A*(/ XP&A*(&@"#$&"&?=*7A&=*&=$%%/&R6*+%$8:$&=*&?@"7$/&*7&"
=*&P568&56?5:@=P(%&"68&8A6"45<&=@56R56:S&T$7$/&$UO$7=&"68 "68&A*(V%%&?$$&=@$4&*6&A*(7&@*4$O":$&"68&56&A*(7&56D*US O$7?O$<=5#$&=*&*PP$7&Y&+$%<*4$&@*4$S&X=V?&$"?A&"68&P7$$&=*
(685?<*#$7$8&#*5<$?&"%5R$&85#$&56=*&=@$&@$"7=&*P&"6A&=*O5<&"68 WUO%*7$ O*?=&A*(7&=@56R56:&*6&"6A&=*O5<S&Z75=$&*6&>$85(4
D756:&6$+&58$"?&=*&=@$&?(7P"<$S&G$"76&4*7$

9D*(= T$%O G$:"%