(Software Engineering ) Agile Manifesto & its 12- Principles with diagram

•  Agile Manifesto  -

• A manifesto is normally associated with an emerging political movement—one that attacks the old guard and suggests revolutionary change 
• Agile software engineering combines a philosophy and a set of development guidelines. 
• The philosophy encourages customer satisfaction and early incremental delivery of software; small, highly motivated project teams; informal methods; minimal software engineering work products; and overall development simplicity 

WHAT IS AGILE? 

• 1)Agile proponents believe 

  • Current software development processes are too heavyweight or cumbersome 

  • Too many things are done that are not directly related to software product being produced 

• 2)Current software development is too rigid 

  • Difficulty with incomplete or changing requirements 

  • Short development cycles 

  • More active customer involvement needed 

 

AGILE SDLC 

• Speed up or bypass one or more life cycle phases 
• Usually less formal and reduced scope 
• Used for time-critical applications 
• Used in organizations that employ disciplined methods 

AGILE PROCESS 

• Is driven by customer descriptions of what is required (scenarios) 
• Recognizes that plans are short-lived 
• Develops software iteratively with a heavy emphasis on construction activities 
• Delivers multiple ‘software increments’ 
• Adapts as changes occur 

 

PRINCIPLES :

1. 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 efficient and effective 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 indefinitely. 
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 reflects on how to become more effective, then tunes and adjusts its behaviour accordingly.