Join Philip Lew from PNSQC and Yingki Kwong from PPLF (Portfolio and Project Leaders Forum) as they discuss Agile Risk and Uncertainty. Agile is designed to handle uncertainty in requirements as new features are requested and their priorities shift in real time. Agile sprints produce frequent software releases based on direct input from the business. This tight coupling with the business enables, in theory, early detection of defects in requirements and designs; as high level user stories / scenarios are elaborated to produce detail requirements that support design, development, and implementation. However, in chasing agility, projects often ignore or can only poorly understand the uncertainties and associated project risks introduced by important Agile processes, such as the backlog. With relentless sprints, it is easy to view completed sprints as a proxy for progress. The risk trap is poor understanding of the probability and impact of the actual project risks associated with implementing certain user stories incorrectly (scope / quality risks) and actual velocity falling short of the expected (schedule / budget risks). A key question is: how do we mitigate the uncertainties that are introduced by using Agile? Phil Lew suggests that an important problem is that we sometimes carry assumptions which either cause us to spend too much effort on things we can’t control or give us unfounded comfort and reassurance. If we can’t understand the uncertainties and risks, how can we have confidence in our software as systems become more complex? Phil supplements classic risk management techniques with a lifecycle approach on risk and uncertainty to identify and address the uncertainties that matter—and those that don’t. Then Phil outlines methods that you can use to address these risks while maintaining rhythm in your agile software processes. Come and learn about risks you never thought of and see how you can manage or avoid them.