Event: Agile Development – A Curse or a Blessing for Requirements Engineers?


Thursday 22 March 2012, 6pm-8:30pm


BCS headquarter, 5 Southampton Street, London WC2E 7HA


Free, but compulsory.

Register at the BCS Event Booking Site via this link.

Closing date for bookings is midnight on Wednesday 21st March 2012. No more bookings will be taken after this date. For overseas delegates who wish to attend the event please note that BCS do not issue invitation letters.

RESG Free Evening Event with Refreshments.

Many organisations have turned to, or are considering turning to agile methods of software development. These methods have been described as the revenge of the programmers against heavyweight documentation-centric processes that many associate with traditional requirements engineering. Agile methods aim at reducing the risks of requirements problems that have plagued many projects by developing software in small iterations with intensive customer involvement throughout development. Requirements knowledge is transmitted orally with minimal documentation in the form of user stories and acceptance tests. But what is the reality of agile practices at addressing requirements risks? Can we believe the hype surrounding agile methods? What are the effects of these practices on the day-to-day work of requirements engineers and business analysts?

This RESG event will take a look at agile development from a requirements engineering perspective and will leave plenty of time for discussion to identify common concerns and practical guidelines for requirements engineers.

The discussions will start with a talk by Keith Braithwaite on agile requirements by examples.


  • 18.00 Refreshments
  • 18.30 Talk: Agile Requirements by Example, Keith Braitwaite
  • 19.00 Discussions
  • 19.30 Drinks and Sandwiches


Title: Agile Requirements by Example

Abstract: System-building projects which fail (which is many of them) do so more often because they build the wrong thing, not because they do a bad job of building the right thing. The Agile community has developed a range of techniques for making sense of system requirements and capturing them in artifacts that are familiar and understandable by business, useful to developers and informative to managers. The central concept is that of a “checked example” In This talk Keith will illustrate some of these techniques and artifacts by example and discuss the impact that they can have on users, developers and managers.

Bio: Keith Braithwaite is a Principal Consultant with Zuhlke Engineering in London where he leads the Centre for Agile Practice (CAP). He has been using what Agile techniques to develop systems ranging from mobile handset firmware to world-spanning distributed systems for more than a decade while working for companies ranging from startups to multi-national consultancies.

Share Button