Category: kanban

  • The Kanban Story: The Beginning

    So I found myself in this small team, part of a bigger company but working pretty independent of the rest of people here. Kind of start-upish environment. I knew every single person I worked with. Well, actually I’d chosen most of them and hired them here. The team was great (if you guys are reading this: no, it is not a reason to come for a raise) and personally I didn’t feel an urge to strictly control everything. On the other hand some order is always a nice thing.

    Initially I gave a lot of thought to project management practices and didn’t come with a solution I was happy with.

    I rejected PMP-based heavy-weight process which works for many projects in the organization. We didn’t need all the hassle they bring. At least not at that stage. A natural idea was Scrum which I didn’t like either. Scrum is pretty formalized methodology too and I wanted to avoid formalisms as much as possible. Actually with a lot of R&D work, pretty much prototyping and priorities changing all the time I needed something more flexible.

    I didn’t want to be time-boxed since we were planning to work simultaneously on a few independent small projects which would be hard to synchronize if we wanted to put them all in one team-wide sprint. Creating independent sprints for each of projects was a complete overkill since you don’t really need Scrum sprint for a one-and-a-half-person project.

    Actually I’d say we were at the point where we were too flexible for agile methods. Now, go burn me in flames for being iconoclast.

    After some discussions we collectively agreed we wouldn’t adopt Scrum as a whole but would use some of techniques used there and some other ideas we thought were good. In the next post in the series you’ll find more details how we initially organized our development.

    Keep an eye on the whole story.

  • The Kanban Story

    My current team works with Kanban for some time already. For all of us this is a kind of experiment on live organism. Ongoing experiment. That’s what led me to an idea of The Kanban Story – a set of posts which are a logbook of our cruise with Kanban.

    The story has its beginning and several chapters since some things already happened since we started our friendship with Kanban. There’s no end however. I don’t know what we’re going to end up with but I’m going to share with you all ups and downs which we encounter along the road.

    Hopefully this will become a kind of manual which helps with other Kanban implementations and generally with your work on projects and teams.

    Technically it would work as pretty much every series on this blog – I will publish new chapter of The Kanban Story every week or so and you’d be able to find links all of them which are already published below since this post will be updated every time new post in series appears on Software Project Management.

    1. The Beginning
    2. Initial Methodology
    3. First Issues
    4. Discovery of Kanban
    5. Implementation of Kanban
    6. Kanban Board
    7. What We Do And What We Don’t Do
    8. Kanban Board Evolution
    9. Kanban Alone Is Not Enough
    10. I Don’t Know, Experiment
    11. Throwing Sticky Notes Out
    12. Pseudo Iterations
    13. Kanban Board Revisited
    14. Kanban Boosters
    15. Measuring Lead Time
    16. Coarse-Grained Estimation
    17. Swarming
    18. When and Why We Abuse Limits
    19. Small Tricks Do the Job
    20. Moving Cards Back
    21. Retrospectives
    22. Standard-Sized Features
    23. Skipping Part of Process
    24. Kanban Board Should Reflect the Reality