What Is Agile? | Agile Methodology | Agile Framewroks-Scrum, Kanban, Lean, XP, Crystal | Simplilearn

1. Imagine a time in the late 90’s in a software development firm…

2. Imagine a time in the late 90’s in a software development firm…

3. Sir! We have a problem!

4. Imagine a time in the late 90’s in a software development firm… Click here to watch the video

5. What happened?

6. Our clients want a new feature to the software! We’re already midway creating the software! We can’t add the feature!

7. OH NO!

8. I knew we shouldn’t have used the waterfall methodology for development!

9. During the time, the methodology being used was the waterfall model • The waterfall model involves teams following a series of steps, and only going forward after the previous steps are completed • It is best used in scenarios where the teams are small, and the project is expected to move in a predictable manner

10. The Waterfall Model

11. The Waterfall Model - Disadvantages These are some of the reasons why the move to an alternative to the waterfall model was necessary: The testing phase is delayed until most of the project is completed Measuring the progress within stages is difficult Makes changes difficult It doesn’t focus on the end-user/ client

12. What is Agile?

13. Then, in 2001 Agile was introduced! A G I L E 2001

14. What Is Agile? Agile is a set of principles used in project management and software development

15. What Is Agile? • It enables teams to deliver value to their customers with ease

16. What Is Agile? • It enables teams to deliver value to their customers with ease • Agile teams deliver work in small, but usable increments

17. What Is Agile? • It enables teams to deliver value to their customers with ease • Agile teams deliver work in small, but usable increments • Evaluation of the requirements, plans, and results take place continuously. This allows teams to respond to changes quickly

18. What Is Agile? The concepts of agile are detailed in the agile manifesto

19. What Is Agile? The Agile Manifesto Created in February 2001, the Agile Manifesto details the values and principles of agile processes

20. What Is Agile? The Agile Manifesto Here are some of the values mentioned in the manifesto: Processes and Tools Comprehensive Documentation Contract Negotiation Following a plan Individuals and Interactions Working Products Customer Collaboration Responding to Changes OVER

21. Agile Principles

22. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 1 Customer Satisfaction You need to satisfy the customer through early and quick delivery of the product

23. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 2 Welcome Change Changing needs need to be addressed, even late in the development process

24. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 3 Deliver Frequently Ensure software is delivered frequently, focusing on a shorter timescale

25. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 4 Work Together Developers and business individuals need to work together through the course of the project

26. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 5 Motivated Team Projects need to be built around motivated individuals and they must be trusted to get the job done

27. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 6 Face-to-face Face-to-face conversation is the most efficient means of communication

28. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 7 Working Software Working software is the primary measure of progress

29. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 8 Constant Pace The agile process promotes sustainable development

30. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 9 Good Design Agility can be improved by focusing on technical excellence and good design

31. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 10 Simplicity The amount of work that’s not being done needs to be minimized

32. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 11 Self-organization Self-organized teams provide the best architectures, requirements, and designs

33. Agile Principles The Agile Manifesto Here are some of the principles that need to be followed to a make a process agile: 12 Reflect and Adjust Effectiveness can be improved by the team regularly reflecting on it

34. What are the Advantages of Agile?

35. What Are the Advantages of Agile? Large amounts of interaction between the client and the project team Improved transparency to clients in every phase of the project The delivery of the output is predictable and can sometimes be earlier than expected The costs of the project are predictable and follow a rigid schedule

36. What Are the Advantages of Agile? The client can provide the priority of features, allowing the team to ensure maximum project value The project is broken into smaller units, with high-quality development, testing, and collaboration It allows for changes to refine and re-prioritize the product backlog By focusing on the needs of the users, the team can deliver value to the customers

37. Agile Methodologies

38. Agile Methodologies Here are some of the methods to implement Agile XP

39. Agile Methodologies Extreme Programming • It is a framework that enables teams to create high-quality software and improves their quality of life • It enables software development with the appropriate engineering practices

40. Agile Methodologies Extreme Programming • When is it applicable? • Changing software requirements • To handle risks caused due to new technology • Working with a small, extended development team • To use technology to allow automated unit and functional tests

41. Agile Methodologies Here are some of the methods to implement Agile Kanban

42. Agile Methodologies Kanban • This method is used to design, manage and improve the flow of systems • Organizations can visualize their flow of work and limiting their work in progress

43. Agile Methodologies Kanban • When is it applicable? • It can be used in situations where work arrives in an unpredictable fashion • It is also used to deploy work immediately, without waiting for other work items

44. Agile Methodologies Here are some of the methods to implement Agile Lean

45. Agile Methodologies Lean • Lean is a set of tools and principles that aims to identify and remove waste to increase the speed of process development • It focuses on maximizing value to the client, ensuring waste is minimized

46. Agile Methodologies Lean When is it applicable? Lean’s principles apply to any sector where there’s waste of any form

47. Agile Methodologies Here are some of the methods to implement Agile Scrum

48. Agile Methodologies Scrum • Scrum is a framework that is used by teams to establish a hypothesis, try it out, reflect on the experience and adjust • It is used to enable teams to incorporate practices from other frameworks depending on the team’s requirements

49. Agile Methodologies Scrum When is it applicable? It is used when cross-functional teams are working on product development when work is split into more than one 2-4-week iterations

50. Agile Methodologies Here are some of the methods to implement Agile Crystal