Project Management

 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.

Many organizations are childlike. They blithely plan the project as if nothing will go wrong. And then, when something does go wrong, they are shocked and dismayed. Risk management is not just worrying about your project, and it is not about running away from risk. Risk management for software projects is all about when you make decisions and when you take action. How do you deal with uncertainty? When do you decide to deal with a risk while it is still just a risk, and when do you decide to wait to see if the risk does turn into a problem and manage it then? When done with utmost skill and to its greatest advantage, risk management starts before a project is even born. Tim Lister presents the advantages—and the dangers—of practicing risk management like a grown-up. Tim offers a process for you to consider tailoring for your organization and discusses how your organization can grow up.