Overview and Basics

*Agile Mindset

*What is Agile ?!

*Agile is not a process or a set of practices,

*It’s more like a mindset, a way to think about Software development that could be applied to any process using any set of practices!

*What is Agile ?!

*Agile Manifesto

*We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value,* Individuals and interactions over processes and tools,

* Working software over comprehensive documentation,

* Customer collaboration over contract negotiation,

* Responding to change over following a plan.

*That is, while there is value in the items on the right, we value the items on the left more

*Agile Manifesto ❶

*Individuals and interactions over processes and tools

*Agile Manifesto ❷

*Working software over comprehensive documentation

*Agile Manifesto ❸

*Customer collaboration over contract negotiation

*Agile Manifesto ❹

*Responding to change over following a plan

*Agile Principles

*The Manifesto for Agile Software Development defines a set of 12 principles that represent the characteristics or inherent traits of an agile mindset.

*Agile Principles ❶

*Our highest priority is to satisfy the customer through early and continuous delivery of valuable software,

*Welcome changing requirements, even late in development,

*Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale,

*Agile Principles ❷

*Business people and developers must work together daily throughout the project,

*Build projects around motivated individuals,

*The most efficient and effective method of conveying information to and within a development team is face-to-face conversation,

*Agile Principles ❸

*Working software is the primary measure of progress,

*Agile processes promote sustainable development,

*Continuous attention to technical excellence and good design enhances agility,

*Agile Principles ❹

*Simplicity -the art of maximizing the amount of work not done- is essential,

*The best architectures, requirements, and designs emerge from self-organizing teams,

*At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly,

*Features Usage!

Always7% Often

13%

Sometimes16%

Rarely19%

Never45%

*Agile Benefits!

0%

30%

60%

90%90% 85% 83%

66%

*Traditional | Agile

*VER | HOR

10% 20% 30% 30% 10%

#1 #2 #3 #4 #5

Elicit 10% 1% 2% 3% 3% 1%

Design 20% 2% 4% 6% 6% 2%

Develop 40% 4% 8% 12% 12% 4%

Test 20% 2% 4% 6% 6% 2%

Integrate 10% 1% 2% 3% 3% 1%

*Typical Agility DEV.

*Challenges

*Technical

*Bringing Testing forward,

*Moving from Manual Testing to Automation

*Organizational

*Dev/Test teams are separate,

*Everyone has not bought into agile practices.

*The End!