Thursday, October 6 | Introduction to Scrum
Scrum is the most adopted agile methodology. Time and again, it has transformed low performing development teams into powerful creators of business value. Scrum does particularly well in environments where requirements shift or change unpredictably and in areas with substantial uncertainty. During this event, we will introduce the three Scrum roles, dive into the basic Scrum processes, and explore the reasons behind Scrum’s power. Although this event is an introduction to Scrum, we will provide several tips and tricks to assist in Scrum adoption.
Friday, October 7 | Scrum-damentals
Scrum is the most adopted and recognized agile methodology. However, there are still challenges to Scrum adoption. This event will dive into several Scrum adoption pitfalls and how an organization can avoid them. In particular, we will highlight some of the proven practices that have worked for diverse sets of teams. We will also leave time for questions and encourage attendees to bring your most challenging problems!
Friday, October 21 | Visualize Work – The Power of Big Visible Displays
Visible work has a profound impact on a team. By making work visible, teams can rapidly identify bottlenecks and issues, visualize the amount of work the team has under development, and most importantly understand the “life story” of the features they are working on. At a glance, teams can identify overloaded people, problematic stories, quality problems, and overall development speed. Visualization is one of the key tools in an effective Kanban implementation. During this event, we will discuss how Kanban teams visualize work, where to get started with visualization, and the tools available to help build effective visualizations electronically.
Friday, November 4 | Limit Work in Process (WIP)
Overloaded individuals and teams suffer from bad multitasking. They are also cursed with long lead times, poor quality, and high rates of failure. Kanban limits work in process (WIP) to improve the flow in a development process. This event is more technical than the earlier Kanban events. During the event, we will expose the problems caused by excessive WIP, and the wide-ranging benefits of reducing WIP.