Download to read offline
Uploaded byJulian Andres Sucerquia
Agile
The document discusses the Agile methodology for project management. It began in 2001 with the Manifesto for Agile Software Development. Agile is a mindset and way of working together to deliver value to customers through principles like welcoming changing requirements, frequent delivery of working software in small batches, collaboration between business and development teams, and responding to change. Common Agile methods in use today include Scrum, Kanban, XP (eXtreme Programming) and Lean. The document emphasizes that Agile is not just for software but can be applied to any type of work.
Agile
- 1. AGILE? BY : J UL I A N A N D R E S S U C E R Q U I A U R I B E
- 2.
- 3. A mindset A way of working together AGILEIS: to get things done
- 4. It started in2001 when Manifesto for Agile Software Development I Was penned
- 5. It started in2001 when Manifesto for Agile Software Development I Was penned it consists of a set of PRINCIPLES That define BEST practices for taking an idea and creating a product
- 6. • Creating plans •Ensuring quality • Admiting changes Agile is simply common sense
- 7. WORKING IN SMALLBATCH SIZES
- 8. WORKING IN SMALLBATCH SIZES GETTING DONE WITH THINGS BEFORE YOU START SOMETHING ELSE
- 9. WORKING IN SMALLBATCH SIZES GETTING DONE WITH THINGS BEFORE YOU START SOMETHING ELSE PROVING THAT YOU ARE DONE AND THAT YOU HAVE CREATED WHAT YOUR TEAM COMMITTED TO CREATE
- 10. WORKING IN SMALLBATCH SIZES GETTING DONE WITH THINGS BEFORE YOU START SOMETHING ELSE PROVING THAT YOU ARE DONE AND THAT YOU HAVE CREATED WHAT YOUR TEAM COMMITTED TO CREATE TAKING RESPONSIBILITY AND ACCOUNTABILITY FOR WHAT YOU COMMIT TO DOING
- 11. WORKING IN SMALLBATCH SIZES GETTING DONE WITH THINGS BEFORE YOU START SOMETHING ELSE PROVING THAT YOU ARE DONE AND THAT YOU HAVE CREATED WHAT YOUR TEAM COMMITTED TO CREATE TAKING RESPONSIBILITY AND ACCOUNTABILITY FOR WHAT YOU COMMIT TO DOING WORKING TOGETHER
- 12. WORKING IN SMALLBATCH SIZES GETTING DONE WITH THINGS BEFORE YOU START SOMETHING ELSE PROVING THAT YOU ARE DONE AND THAT YOU HAVE CREATED WHAT YOUR TEAM COMMITTED TO CREATE TAKING RESPONSIBILITY AND ACCOUNTABILITY FOR WHAT YOU COMMIT TO DOING WORKING TOGETHER CONSTANTLY LEARNING
- 13. it is thesimplest thing you will ever try to do, but at the same time, it is one of the hardest things there is to do well
- 14. AGILE MANIFESTO … betterways of developing software by doing it and helping others do it
- 15.
- 16.
- 17.
- 18. 1 "Our highest priorityis to satisfy the customer through early and continuous delivery of valuable software.”
- 19. 2 “Welcome changing requirements,even in late development. Agile processes harness change for customer’s competitive advantage.”
- 20. 3 “Deliver working softwarefrequently, from a couple of weeks to a couple of months, with a preference to the shorter timeline.”
- 21. 4 “Business people anddevelopers must work together daily throughout the project.”
- 22. 5 “Build projects aroundmotivated individuals. Give them the environment and support they need, and trust them to get the job done.”
- 23. 6 “The most efficientand effective way of conveying information to and within a development team is face-to-face conversation.”
- 24. 7 “Working software isthe principal measure of progress.”
- 25. 8 “Agile processes promotesustainable development. The sponsors, developers and users should be able to maintain a constant pace indefinitely.”
- 26. 9 “Continuous attention totechnical excellence and good design enhances agility.”
- 27. 10 “Simplicity—the art ofmaximizing the amount of work not done—is essential.”
- 28. 11 “Best architectures, requirements,and designs emerge from self-organizing teams.”
- 29. 12 “At regular intervals,the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.”
- 30. AGILE METHODS USEDTODAY SCRUM KANBAN XP LEAN LEAN STARTUP DESIGN THINKING
- 31. isn’t agile justfor it or software development?
- 32. isn’t agile justfor it or software development? NO, IT´S NOT
- 33.