Presented by: Daniel Greenleaf and Anita Shankar
Analysis Track: 11am-noon
Presentation Materials: Slide Deck

Successful projects depend on deeply understanding users needs. Too often though, during the transition from traditional methods to Agile, teams swing the pendulum too far in the other direction using “working software over comprehensive documentation” as an excuse to abandon capturing and communicating requirements. User Stories can be an extremely effective technique to communicate requirements, but they require the disciplined application of new skills. The good news is those skills can be acquired with a little guidance.

Join Anita and Dan for a fun and interactive session that will show you how to write effective user stories. The common pitfalls to avoid when writing user stories. What good acceptance criteria looks like. And how to still be effective without resorting to comprehensive documentation.

Presented by: Daniel Greenleaf
Analysis Track: 2:45pm-3:45pm
Presentation Materials: Slide Deck

“The child who receives a hammer for Christmas will discover that everything needs pounding” (Gerald Weinberg). User Stories are a wonderful tool that work in most situations. But like any tool User stories have their limitations. Thankfully there are other tools analysts have to define and communicate requirements. Come find out about other tools Agile analysts can use in conjunction with user stories. Learn about agile projects that don’t have user stories. And even when being Agile means not having user stories.

Presented by: Elaine McCormick
Analysis Track 1:30pm-2:30pm
Presentation Materials: Slide Deck

When will the work be completed? How does introducing new stories effect my timelines? We will cover how to quickly size a project backlog as well as how to work with stories for an iteration and how each of these can give immediate feedback to the team and the organization in what is happening on your project

Presented by: Don McGreal
Analysis Track: 9:45am-10:45am
Presentation Materials: Slide Deck

So we now acknowledge that complete upfront requirements is an impossible mission. Agile approaches have emerged as a way to manage the creation of systems that can never be completely defined and are certain to change.

But what about architecture and design for these systems? How much is the right amount? How do you plan for emergent design? What is the architect’s role on an agile project?

Join Don McGreal as he examines these questions and more in this deep dive into architecture in an agile world.