Your SlideShare is downloading. ×
0
*    Overview and Basics
* Agile is not a process or a set of practices,* It’s more like a mindset, a way to think about Software development that ...
*
* We are uncovering better ways of developing  software by doing it and helping others do it.  Through this work we have c...
*Individuals and interactions over processes and tools           *
*Working software over comprehensive documentation          *
*Customer collaboration over contract negotiation           *
*Responding to change over following a plan           *
* The Manifesto for Agile Software Development defines a set of 12 principles that represent the characteristics or inhere...
* Our highest priority is to satisfy the customer through early and continuous delivery of valuable software,* Welcome cha...
* Business people and developers must work together daily throughout the project,* Build projects around motivated individ...
* Working software is the primary measure of progress,* Agile processes promote sustainable development,* Continuous atten...
* Simplicity -the art of maximizing the amount of work not done- is essential,* The best architectures, requirements, and ...
Always                    Often               7%                    13%Never45%                       Sometimes           ...
90%          85%100%                                  83%80%                                                    66%60%40%2...
*
10%   20%   30%   30%   10%                  #1    #2    #3    #4    #5Elicit      10%   1%    2%    3%    3%    1%Design ...
*
* Technical  * Bringing Testing forward,  * Moving from Manual Testing to Automation* Organizational  * Dev/Test teams are...
*
Upcoming SlideShare
Loading in...5
×

Agile mindset

431

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
431
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
9
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "Agile mindset"

  1. 1. * Overview and Basics
  2. 2. * 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! *
  3. 3. *
  4. 4. * 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 *
  5. 5. *Individuals and interactions over processes and tools *
  6. 6. *Working software over comprehensive documentation *
  7. 7. *Customer collaboration over contract negotiation *
  8. 8. *Responding to change over following a plan *
  9. 9. * The Manifesto for Agile Software Development defines a set of 12 principles that represent the characteristics or inherent traits of an agile mindset. *
  10. 10. * 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, *
  11. 11. * 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, *
  12. 12. * Working software is the primary measure of progress,* Agile processes promote sustainable development,* Continuous attention to technical excellence and good design enhances agility, *
  13. 13. * 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, *
  14. 14. Always Often 7% 13%Never45% Sometimes 16% Rarely 19% *
  15. 15. 90% 85%100% 83%80% 66%60%40%20% 0% Increased Reduced Accelerated Reduced Cost Productivity Software Time to Market Defects *
  16. 16. *
  17. 17. 10% 20% 30% 30% 10% #1 #2 #3 #4 #5Elicit 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% *
  18. 18. *
  19. 19. * Technical * Bringing Testing forward, * Moving from Manual Testing to Automation* Organizational * Dev/Test teams are separate, * Everyone has not bought into agile practices. *
  20. 20. *
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×