We're at Agile Development East this week where industry experts and agile practitioners gather to share key insights on the issues they deal with every day.
We'll be in and out of the keynotes and tutorials over the course of the week and sharing some of the key takeaways.
In his tutorial, Eight Steps to Kanban, Ken Pugh of Net Objectives shared the steps involved in implementing Kanban in your organizaton. Transitioning to agile can be difficult for teams and as such many are turning to Kanban, and the just in-time software delivery methodology as a more gradual evolution to full-on agile.
Unlike agile, where all stories are created equal, lean focuses on business value first.
#Lean: deliver highest business value first/highest return on investment. #bscadc
— Agile Connection (@agileconn) November 12, 2013
business value trumps flow trumps waste @kpugh #bscadc #Lean
— Agile Connection (@agileconn) November 12, 2013
Lean assumes someone knows what business value is -@kpugh #bscadc
— TechWell (@TechWell) November 12, 2013
And getting feedback early and often is key:
The faster you get feedback the faster you know if you're in the right direction @kpugh #lean #kanban #bscadc
— Agile Connection (@agileconn) November 12, 2013
because
Unclear requirements lead to rework and diminished business value. #lean #bscadc
— Agile Connection (@agileconn) November 12, 2013
We're curious, have you implemented Kanban in your organization? What are some of the lessons you've learned? Tell us in the comments below.