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

Ditching Scrum for Kanban

Grant Ammons
February 09, 2016

Ditching Scrum for Kanban

I talk about our transition from an ad-hoc software development process, to implementing Scrum, and then finally moving to Kanban.

Grant Ammons

February 09, 2016

Transcript

25 slides
  1. WHO AM I? ▸ Grant Ammons - VP engineering at

    PipelineDeals ▸ Scaled From 1 to 12 engineers ▸ @gammons Medium + Twitter
  2. WHAT IS PIPELINEDEALS? ▸ Sales CRM software, Web-based, SaaS ▸

    Ruby/Rails ▸ Remote engineers ▸ Small (12 dev, 31 employee) long-lived product company ▸ One company, one product.
  3. WHO AM I NOT? ▸ A Scrum expert ▸ A

    Kanban expert ▸ All I have is my experience + story.
  4. OUR NASCENT PROCESS ▸ Detailed wireframes / comps with notes

    ▸ One developer -> One "project" ▸ Project completed when the comps were "done"
  5. PROBLEMS ▸ No shared understanding of architecture ▸ No real

    QA step ▸ No code reviews ▸ No real UX (we all wore the UX hat) ▸ Right onto the next "project", no follow-through
  6. WHAT WE KNEW ▸ Lack of organization ▸ We had

    QA issues ▸ We needed a better collaborative dev process
  7. SCRUM ▸ Hired a coach, he came in for an

    intense 2 day session ▸ Learned Scrum properly. Set up development board.
  8. ROLES ▸ 4 Engineers (one of which was mainly QA)

    ▸ 1 Designer ▸ 1 Scrum master ▸ Shared "product owner" role
  9. 3 MONTHS IN ▸ We were much more organized ▸

    QA issues were much much better, combo of making time for it + better eng. practices ▸ The shared PO role was bizarre ▸ Will our estimating get better?
  10. 12 MONTHS IN ▸ Still shipping high quality software, benefiting

    from discipline ▸ Got a PM But, Problems. ▸ We were sick of day-long tasking meetings ▸ Estimations were consistent, but still inaccurate ▸ QA problems because of cramming
  11. WHAT IS KANBAN? ▸ Kanban is basically Scrum with the

    goalposts removed ▸ Continuous flow ▸ Pull system ▸ WIP limits
  12. 12 MONTHS IN ▸ Team morale is very high ▸

    Very good cadence ▸ Delivery process + QA process is in very good place

More Decks by Grant Ammons

Other Decks in Technology