As the internet proliferates beyond the PC to myriad devices - from iPhone to smart-phone - anyone delivering digital products deals with complexity: varying form factors, cultural differences and contexts of use. In this workshop we explore the implications of this complexity, discover through collaborative experience where the pain points lie, and identify strategies for dealing with them. We conclude that the unique challenges faced in the design and development of mobile applications benefit from agile software development and its ability to cope with such complexity.

How do you become agile with all the constraints surrounding you and your team? This tutorial introduces a new way to approach agile adoption efforts. We will go through important and key concepts related to agile adoption such as adopting values not practices, the difference between education and training, readiness assessments, and the process of organizational change. One of the tangible outcomes from this tutorial is a roadmap to agility that consists of five different levels, or steps, along with the different practices that can help an organization achieve each level of

How do agile teams account for backlog items that do not fit the user story paradigm? Aside from user stories, what are ways you can represent product needs? Teams struggle with incorporating quality attributes (sometimes called “quality of service” requirements), external interfaces, design and implementation constraints, and team or technical “stories” into their backlogs. Without these items, you will not build the right product, or build it right. This tutorial will introduce you to ways that agile teams represent these nonfunctional requirements and other items in the backlog.