Continuous Deployment
Going Agile via the Fast Lane – How FiftyOne.com switched from quarterly releases to 2 weeks Scrum and Kanban.
Ben Peer shares the story of FiftyOne.com’s transition in the last year. Starting with Scrum, involving the whole team in true inspect and adapt, evolving to Kanban/ScrumBan, evolving team formation and definition of done, adding Agile Testing approaches including ATDD. In parallel, tight collaboration with a remote Product Management team, and usage of an electronic highly visual Kanban board. Ben will discuss the benefits, the challenges and how the team dealt with them, and will provide recommendations to others considering this journey.
Agile Risk Management Reading list Risk Management in Kanban – The TameFlow Chronologist Risk Kanban Board – Zsolt Fabók Managing Risk on Agile Projects with
When going to use kanban, a team/organization needs to decide whether to use a physical or electronic board.A physical board is tangible, fully customizable, and
IT support organizations, as the name applies, are business enablers that achieve success by providing business customers the services they need, when they need it, and at a cost that is affordable to the organization. In the past 20 years, as companies grew, we have seen that many IT organizations have become a nest of complex processes, distributed environments, long delays and ever decreasing customer satisfaction. The IT service organizations have become complex to manage, over bureaucratized, expensive to operate all under the umbrella of reduced costs.
What is it?
A game to help you really understand how to apply Kanban to software development
An effective teaching tool for your organization or training program
The quickest, most effective way to teach the principles and mechanics of Kanban.
The physical board game version developed by Russell Healy is available from GetKanban.
Background: I recently had a short twitter chat with Catherine Swetel and Steven Holt about the relation between TOC Critical Chain and Kanban. This post will try to sum up my thoughts in a way that is a little bit more persistent, as well as add a bit more color and depth that is not possible in 140 characters. To start with, lets just make clear – I’m no expert at TOC or Critical Chain. I’ve done my share of reading over the years and have seen organizations using CC and helped them explore the Agile/Kanban world. I’ve read Critical Chain for the first time back in 1996 or so and also familiarized myself with the MPCC S&T tree in the last couple of years. With that disclaimer, here are my thoughts, for what they’re worth:
The Freeze, No New Work, Limit Later, and some Mashups… Some of us have the luxury of designing processes for Greenfield systems meaning there is no history/legacy to deal with.
Kanban is a powerful and flexible system. One of the popular emerging ways of using it is to create and manage product development flow. Whether for a single project, a program, or a portfolio, we will explore the need for product development flow, see how kanban fulfills this need in a couple of examples from real clients, and discuss the next frontiers for program management flow.
Request for additional information and prices