Be the first to like this
Because transitioning to agile can be difficult—and often wrenching—for teams, many organizations are turning to kanban practices. Kanban, which involves just-in-time software delivery, offers a more gradual evolution to agile and is adaptable to many company cultures and environments. With kanban, developers pull work from a queue—taking care not to exceed a threshold for simultaneous tasks—while making progress visible to all. Ken Pugh shares eight steps to adopt kanban in your team and organization. He begins with a value stream map of existing processes to establish an initial kanban board, providing transparency into the state of the current workflow. Another step is to establish explicit policies to define workflow changes and engender project visibility. Because kanban can easily be expanded to cover many parts of development, another step is to increase stakeholder involvement in the process. Join this interactive session to practice these key steps with hands-on exercises. By the end, you will have an initial plan for implementing kanban in your organization.