Requirements

Tutorials

MB Requirements Engineering: A Practicum

Erik van Veenendaal, Improve IT Services BV

Mon, 11/11/2013 - 8:30am

Identifying, documenting, and communicating software requirements are key to all successful IT projects. Common problems in requirements engineering are “How do we discover the real requirements?”, “How do we document requirements?”, and “How do user stories fit into requirements?” Erik van Veenendaal answers these questions and more while helping you improve your skills in requirements engineering for both traditional and agile projects. With practical case studies and hands-on exercises, Erik illustrates requirements issues and solutions.

TG Agile Project Failures: Root Causes and Corrective Actions

Jeff Payne, Coveros, Inc.

Tue, 11/12/2013 - 8:30am

Agile initiatives always begin with the best of intentions—accelerate delivery, better meet customer needs, or improve software quality. Unfortunately, some agile projects do not deliver on these expectations. If you want help to ensure the success of your agile project or get an agile project back on track, this session is for you. Jeff Payne discusses the most common causes of agile project failure and how you can avoid these issues—or mitigate their damaging effects.

TH The Role of the Agile Business Analyst

Steve Adolph, WSA Consulting

Tue, 11/12/2013 - 8:30am

The business analyst (BA) role seems conspicuously absent from most agile methods. Does agile make the BA role obsolete? Certainly not! But how does a BA exploit the short cycle times and collaborative nature of agile methods? Drawing from the principles of lean product development flow, Steve Adolph introduces five principles for the agile BA—Open the Channels, Chart the Flow, Generate Flow, Lean Out the Flow, and Bridge the Flow. As a communicator, the BA must Open the Channels and Chart the Flow to align all stakeholders.

Concurrent Sessions

AT6 Speed Grooming Requirements with SAFe

André Dhondt, Rally Software Development

Thu, 11/14/2013 - 2:15pm

Want your sprint/iteration planning to take less than fifteen minutes (excluding tasking)? The key is in the story writing we do during backlog grooming. Although the Scaled Agile Framework (SAFe) has little to say about story writing, this "speed grooming" practice makes iteration planning a breeze, and better software comes out of the process. André Dhondt shares stories of real-world agile teams using this technique and how they've moved to a customer-empathy mindset. How does it work?