Conference Presentations

Realistic Test-Driven Development: Paying and Preventing Technical Debt

Are you considering implementing Test-Driven Development (TDD), or have you tried it and failed? If so, this class is for you. Rob Myers describes the basic mechanics and components of TDD. In addition, he explains the real long-term benefits to the individual, team, and organization of using this technique. Teams find that their defect rate is considerably lower (compared to no unit testing, or unit testing after coding). Even greater rewards are gained in future enhancements and releases. As developers build a “safety net” of automated tests around the growing product, the team can rapidly modify the design and add features required by changes in a dynamic market. The TDD tests guarantee that any defects introduced in those modifications are quickly detected. Rob shares first-person stories of how TDD provided astounding returns.

Rob Myers, Agile Institute
Growing Pains: Why Scaling Scrum and XP Hurts - and What You Can Do

Do you have a large scale program with multiple agile teams? If so, you may have experienced some of the growing pains we encountered when we scaled Scrum and XP-conflicting priorities across teams, handling dependencies across multiple backlogs, planning a release date for teams with changing velocities and backlogs, inconsistent technical practices, and ineffective cross-team communication. Ed Kraay presents his organization's experience working on a large, complex Scrum program with multiple, interrelated Scrum teams. Learn the secrets of what to avoid and ways to minimize the pain so that your teams can reduce defects, improve delivery, and have more fun. Ed’s practical tips include synchronizing sprints across teams, using multi-team release planning, building a cross-team roadmap, embedding architects and coaches, and facilitating vertical transparency using a meta-scrum framework.

Ed Kraay, SolutionsIQ
Instill Scrum Values to Build High-Performance Teams

Your teams are using agile practices well and starting to understand the principles behind them, but they are still not high-performing. Although they're getting a bit better with each sprint and they're meeting commitments, they are not producing the great results you thought agile was supposed to create. Come learn the framework for guiding teams to those great results using the Scrum values as the root and ground of the journey. The Scrum values that lead to high performance and the fruits of high performance teams are put into a context that causes teams and people outside teams-even senior managers and executives-to "get it." They get what makes agile work and what we are moving toward when we talk about high-performing teams. Lyssa Adkins offers an interactive experience for you to learn and practice how to teach your team to use this Scrum framework so they, in turn, can chart their own paths toward high-performance.

Lyssa Adkins, Cricketwing Consulting
CMMI or Agile: Why Not Embrace Both?

Agile development methods and CMMI® best practices are often perceived to be in conflict with each other. Some even argue that the Agile Manifesto was largely a counter response to the original CMM®. Hillel Glazer explores ways that CMMI® and agile champions can work together to derive benefit from both approaches to dramatically improve business performance. Arm yourself with the knowledge to address any Agile-CMMI® rift within your organization and learn ways to benefit from both practices. Hillel fills in some of the missing details that led to the original perceived conflict and discovers that CMMI® is missing components that agile provides and agile is missing components that CMMI® provides. He presents examples of how CMMI® can help propagate agile ideas and propel them towards fully optimized performance levels.

Hillel Glazer, Entinex, Inc.
Determining Business Value

Agility focuses on delivering business value to the customers as rapidly as possible, and user stories are a common way to describe the features and functions that define value incrementally. However, to concentrate on delivering most business value earlier in the project, we must determine and assign the relative business value to each of those stories. Through lecture and interactive exercises, Ken Pugh presents two methods for quickly estimating and assigning business value for features and stories. Ken explains the relationships between business value estimates and story point estimates, and how to chart business value for iteration reviews. Ken demonstrates what estimates really represent in both dollars and time. On a larger scale, he shows you how to use business value assessment as a portfolio management tool to prioritize feature development across several projects.

Ken Pugh, Net Objectives
Agile Development Practices 2009: The Power of Retrospectives

One principle in the Agile Manifesto states, "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly." Retrospectives are a powerful, repeatable tool to help your team continuously learn and improve. Linda Rising shares techniques for project retrospectives to help teams discover what they're doing well and identify what should be done differently. Not finger pointing or blaming sessions, retrospectives are structured interactions in which team members reflect on the past in order to become more effective in the future. Linda shares her experiences with leading retrospectives-both successful and unsuccessful. Learn ways to apply her positive experiences and a proven retrospective model to your projects.

Linda Rising, Independent Consultant
Agile Development Practices 2009: Rightsizing Your Project in a Down Economy

In tough times, both shoes drop simultaneously and "scarcity thinking" takes over in senior executives, managers, and development teams. In this environment, dysfunction can wreak havoc on your projects in the form of scope greed, death-march deadlines, and budget cuts. Often, the tendency is to say "yes" to impossible dates, take on too much, suffer the budget cuts, and pray that heroics might save the day. This is a disaster waiting to happen. It takes a skillful manager to "rightsize" critical projects-right team, right scope, right dates-at the beginning. Scarcity thinking threatens all three. Michael Mah describes how to lead difficult conversations and discuss the "undiscussables." He shares how to artfully frame trade-offs for stakeholders to set priorities. Learn how to get buy-in by using a blend of common sense, essential measurement concepts, and rules of software estimation.

Michael Mah, QSM Associates, Inc.
User Stories for Agile Requirements

Expressing requirements as user stories is one of the most broadly applicable techniques introduced by the agile processes. User stories are an effective approach on all time constrained projects and are a great way to introduce a bit of agility to any project. Mike Cohn describes the six attributes of good stories-independent, negotiable, valuable, estimable, sized appropriately, and testable. Explore how user stories help a team shift from more documents to more discussion, encouraging the right mix of both. Learn practical, proven techniques for gathering user stories. Discuss how much work should be done on a user story in advance and by whom and see why a just-in-time, just-enough approach aids a team in becoming agile. Discover the relationship between user stories, epics, themes, and conditions of satisfaction.

Mike Cohn, Mountain Goat Software
Small is Beautiful: Business Agility Through Adaptive Governance

In this economic downturn, is your company looking beyond knee-jerk cost cutting to focus on creative ways to solve business problems? When businesses tap the innovative capabilities that agile development teams possess and scale up through adaptive governance, they can produce game-changing solutions. Sanjiv Augustine shares how leading businesses are using agile to jumpstart and scale their new product development by incorporating user-centered product design and a user story “maturity progression” to support the creative evolution of system development. To optimize their project investments, these businesses are adopting incremental funding and portfolio-level feature prioritization, reducing team churn by creating stable teams with embedded specialists, and tracking and monitoring project portfolio progress across multiple teams in a visual, agile fashion.

Sanjiv Augustine, LitheSpeed
The Scrum Product Owner Demystified

A Scrum product owner's job is challenging, to say the least. Unfortunately, the specific concepts and techniques required to succeed often aren't spelled out in books and training classes. And being referred to-in Scrum jargon-as "the single wringable neck" is enough to discourage anyone from signing up for the job. While there's no silver bullet, Jeff Patton helps fill your Scrum tool-kit with valuable approaches that help product owners succeed: the basics of collaborative discovery sessions to identify business and user goals; how to create effective user stories for better planning; how to split and thin user stories to support iterative/incremental development; approaches for reducing the risk of late delivery; and techniques for keeping users, stakeholders, and the team involved from inception through delivery.

Jeff Patton, Independent Consultant

Pages

AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.