Transitioning to agile can be difficult—often downright wrenching—for teams, so many organizations are turning to kanban instead. Kanban, which involves just-in-time software delivery, offers a more gradual transition 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. Ken 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 establishes explicit policies to define workflow changes and engender project visibility. Because you can easily expand kanban 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 and take away an initial plan for implementing kanban in your organization.