Why agile?
1 like602 views
The document discusses Agile software development, emphasizing its iterative and incremental approach to project management through collaboration among self-organizing, cross-functional teams. It critiques traditional methods that rely on rigid, upfront requirements, highlighting Agile's flexibility in adapting to evolving needs and prioritizing continuous delivery and integration. Overall, it underlines the importance of teamwork, customer collaboration, and adaptability in achieving successful software development.
Why agile?
- 1. WHY AGILE? Laurynas Antanavičius Product Manager @ Data Dog 2014.09.29
- 2. ABOUT US • Custom web development and support • Cloud-based application and software development • B2B, B2C eCommerce solutions • Specialised in PHP • Over 35 developers • Wide base of clients: UK, US, UAE, Canada, Luxembourgh, France…
- 4. OUR TEAM • Crypto-Currency exchange / Forex market • 6 members in the development team • Agile - Scrum, TDD, CI, CD • PHP & GO
- 5. HOW WE WORK • Prioritise features with the PO • Work in short iterrations 1-2 weeks • Development team chooses the features • Write tests before each line of code (TDD & CI) • Ship the feature as soon as it is ready (CD) • Focus on performance & quality
- 6. ARE WE AGILE? Yes, but what is Agile?
- 9. BEFORE STARTING WITH IT let’s look how Agile has evolved in response to standard development issues
- 10. Most of us were taught to write down all our requirements at the very beginning of the project. There are only three things wrong with this: “requirements”, “the very beginning,” and “all.”
- 11. There is a very strong “80-20” rule in software development requirements lists. Most of the business value comes from a very small subset of the so-called requirements. So these other things aren’t “requirements” at all. They’re ideas, and some of them are not very good.
- 12. The client wants to know how long something is going to take, and how much it will cost at the beginning. But how can we say how long it will take if he does not know what he wants?
- 13. Then we come to a situation where a development contract is based on an unrealistic list of requirements, using weak estimates, made at the moment of maximum ignorance, by people who are always optimistic about their own abilities.
- 14. It’s all right, though. We’ll just keep the pressure on, and it’ll be fine.
- 15. The project is planned for months / years until it’s perfectly describing all the functionality. The development is painfully pushed through, with numerous bugfixing, until finally delivered. And the final launch day comes…
- 18. “Agile software development is a group of software development methods based on iterative and incremental development where requirements and solutions evolve through collaboration between self- organising, cross-functional teams. ”
- 19. Scrum Kanban XP Jedi Or whatever else we call it.. “a group of software development methods”
- 20. iterative development - code vs feedback. keep iterating until it’s done incremental development - build what is needed right now then refine “based on iterative and incremental development”
- 21. requirements evolve - I will tell what I need when I see it solutions evolve - minimum fit to requirements then refine “requirements and solutions evolve”
- 22. collaboration - plan together, share work self-organising team - common pool of work cross-functional team - everyone can do everything “collaboration between self-organising, cross-functional teams”
- 23. THAT’S IT! It is not exactly brain surgery, is it?
- 25. FOCUS
- 26. single location & teamwork single tool for managing process Individuals and interactions over Processes and tools
- 27. working demos - don’t break it if you make it documented parts - parts that will be done must be specific Continuous Delivery and Continuous Integration are essential for the success of the project. Working software over Comprehensive documentation
- 28. project owner requirements - user stores flexible outcome - customer gets what he asked for flexible contract - defined in increments Customer collaboration over Contract negotiation
- 29. respond - yes, I heard the customer react - yes, I will change it plans help - manage chaos Responding to change over Following a plan
- 32. “Don’t document bad code — rewrite it.” - Kernighan and Plauger
- 33. Developers are supposed to choose an amount of work on and forecast what can be accomplished in that time.
- 34. Defects should not be piled up, but cleaned periodically. If you wait for a release until the end of the project, you’re gonna have a bad time.
- 35. It’s less stress for you as a developer and as a team member More comitment to work as you choose it yourself Immediate results for you and the client
- 36. WHAT’S NEXT?
- 37. Read about Agile, understand it, memorise it, sleep with it… Until you are 100% confident with using Agile methods
- 38. XP “Extreme Programming” by Ron Jeffries, Ann Anderson, Chet Hendrickson http://xprogramming.com/
- 40. SCRUM “Scrum Guide” by Jeff Sutherland, Ken Schwaber http://www.scrumguides.org/
- 41. TEAMWORK “The Clean Coder” by Robert C. Martin
- 42. TDD, BDD… “Engineering Long-Lasting Software” by Armando Fox David Patterson
- 43. TRUST YOURSELF BEFORE TRUSTING ANYONE