Agile, down the rabbit hole
4 likes244 views
The document discusses the need for adaptive project management in the face of constant change, contrasting traditional methodologies with agile practices. It outlines key agile principles aimed at fostering customer satisfaction, effective collaboration, and continuous improvement while minimizing the cost of change. The document emphasizes that agile is not a one-size-fits-all solution but rather requires tailored application to meet specific project needs.
Agile, down the rabbit hole
- 1. 1 Agile, down the Rabbit hole by Amit Khanna, PMI – ACP, PMP, SMC, SPOC, SAMC & SA (SAFe Agilist) PMI Mumbai chapter volunteer & AVP – Membership Email me: [email protected]
- 2. 2
- 3. 3
- 4. 4 Change and cost of Change • Things Change – Requirements change – Needs change – Priorities change – Technology changes – Fashion changes • Question really is: How do we deal with change or better How do we deal with change when it happens ? How do we minimize impact and cost
- 5. 5 Traditional methodology doesn’t work anymore • Traditional methods are presumptuous, It assumes: – All aspects can be defined prior to start of work – Force up front design and therefore specification – All requirements are stable – Technology is well known to team and mature in its implementation – Product Management has patience – Customer has patience • It is harder to determine value (ROI is longer) • Traditional methodologies were good at managing the known • To succeed we have to Adapt
- 6. 6 Planning Example When the map and the terrain don’t agree, believe the terrain
- 7. 7 Comparison of customer or business engagement over time
- 8. 8 What is Agile anyway ? • Agile is the ability to create and respond to change swiftly and easily
- 9. 9 12 Principles 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable solutions. 2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. 3. Deliver working solutions 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 what 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 solutions are 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 behavior accordingly.
- 10. 10 • Continuous reflection and learning • Removing inefficiencies and waste • Building a collaborative team environment • Working together to find better ways of delivering What Agile IS…
- 11. 11 Agile is NOT... • A Silver bullet • Time-boxing the Waterfall Approach • “Cowboy coding” • Just a collection of practices • A check list of things to do on every project While there are common practices and principles It does need to be applied and tailored to each situation (start by the book, tailor each iteration) It is not a One size fits all What Agile IS NOT…
- 12. 12 So How will Agile Help • Business Ownership – Align with business needs + stakeholder goals – Continuous business involvement – Improve relationship between IT and business • Managing risk – Daily stand-ups, iteration planning meetings, release planning meetings, demos, reviews, and retrospective meetings are all venues for risk management activities on an agile project • Reduced cost of change – Collaborative planning allows stories to be discarded or modified at any time – Detailed analysis/design carried out for current iteration only • Eliminating waste – Only software that is actually being used has the opportunity to deliver value
- 14. 14 Summarizing – Agile Objectives are: • Continuous Innovation – To deliver on current customer requirements • Product adaptability – To deliver on future customer requirements • Improved time-to-market – To meet market windows and improve return on investment (ROI) • People and process adaptability – To respond rapidly to product and business change • Reliable results – To support business growth and profitability
- 15. 15
- 16. 16
- 17. 17 FINAL TAKEAWAY • Technology waits for no man or brand and ignoring those that threaten your business is a sure fire way to lose out to smaller, hungrier competitors who are itching for an opportunity to shine. • A repeatable process is one in which doing the same thing in same way produces the same result. One that is reliable delivers regardless of the impediments thrown in the way – reliability means constantly adapting to meet a goal How deep does the rabbit hole go?
- 18. 18 Further Reading/Resources Books The Art of Agile Development by James Shore and Shane Warden Essential Scrum A Practical Guide to the Most Popular Agile Process by Kenneth S Rubin URL http://www.agile-software-development.com/ http://www.ambysoft.com/essays/agileLifecycle.html https://www.mountaingoatsoftware.com/
- 19. 19 Reference • http://nerds.airbnb.com/engineering-culture- airbnb/?utm_content=buffer6dbcf&utm_medium=social&utm_source=linkedin.com&ut m_campaign=buffer • https://www.quora.com/What-are-some-examples-of-big-corporations-which-use-Agile- Development-successfully • Presentation from BCG • https://www.forbes.com/sites/jeffboss/2015/11/14/6-secrets-of-organizations-that- successfully-adapt-to-change/#5dd184352b0b • http://www.salsify.com/blog/5-companies-that-didnt-adapt-to-new-technology...and- then-went-bankrupt -- Done • https://www.vocoli.com/blog/july-2014/10-companies-that-failed-to-innovate-and-what- happened-to-them/ --- Done • http://www.businesspundit.com/10-businesses-that-failed-to-adapt/11/ -- Done • http://www.allaboutagile.com/10-good-reasons-to-do-agile-development/