Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Agile Project Management

Sponsored · SiteGround - Reliable hosting with speed, security, and support you can count on. →

Agile Project Management

Oliver Hankeln

November 18, 2026

Transcript

18 slides
  1. What does “Agile” mean? The “Manifesto for Agile Software Development”

    [1] gives four pairs of values: 1. Individuals and interactions over processes and tools 2. Working software over comprehensive documentation 3. Customer collaboration over contract negotiation 4. Responding to change over following a plan
  2. Cynefin Complex probe – sense – respond Emergent Practice Complicated

    sense – analyze – respond Good Practice Confused Chaotic act – sense – respond Novel Practice Adapted from Dave Snowden [2] Clear sense – categorize – respond Best Practice Cliff: Clear can tip into Chaotic
  3. Management Approaches by Domain Clear Standardize Changing a wheel on

    your bike Complicated Analyze and Plan Designing an electronic circuit Complex Run experiments and adapt Ecosystem Management Chaotic Act first to stabilize Chemical spill in a river
  4. How to Deal with Complex Problems ▪Inspect and Adapt ▪Test

    your riskiest assumptions first ▪Design safe-to-fail experiments ▪Psychological Safety
  5. From Project to Product Project Product Time Has a start

    and an end Lives as long as it creates value Success On time, in budget, in scope Value for the people who use it Team Disbands when done Stays together and keeps learning Focus Deliver what was agreed Learn what is needed, then adapt
  6. Agile Is a Family, Not a Framework Kan ba n

    m u r c S Lean Startup DevOps Sh p U e ap g in m m a r g o r P e E x tr e m Design Thin kin l a t s Cr y Rs K O g LeSS s e i r o t S r Use Retrospectives Frameworks, practices, mindsets: different things, same neighborhood Ne x us
  7. Scrum in a Nutshell Scrum Team Events Artifacts Product Owner

    Sprint Product Backlog maximizes the value of the product Scrum Master helps the team and organization be effective Developers build a usable Increment every Sprint 1 month or less, the container for all events Sprint Planning why, what, how Daily Scrum 15 minutes, plan the next day Sprint Review inspect the Increment Sprint Retrospective improve how we work commitment: Product Goal Sprint Backlog commitment: Sprint Goal Increment commitment: Definition of Done
  8. Scrum Is Built on Empiricism Transparency Product Backlog, Sprint Backlog,

    Increment, Definition of Done Inspection Daily Scrum, Sprint Review, Sprint Retrospective Adaptation Reordering the Product Backlog, re-planning the Sprint, improving how we work
  9. Key Takeaways ▪ Not all problems are created equal ->

    your approach to them shouldn’t be either. ▪ Projects work for complicated problems, Agile works where projects break down ▪ Agility is based on Transparency, Inspection, and Adaptation ▪ Agility focuses on learning instead of on speed alone ▪ Agile is a family of approaches. Scrum is just one of them

More Decks by Oliver Hankeln

Other Decks in Technology