Requirements Engineering: Defining Success Requirements (2 day course)

Critical top-level quantified value-requirements analysis-and-specification, using Planguage

Tuesday 18 - Wednesday 19 February 2014 (2 day course)

9.00am for 9:30am - 4.00pm

BCS, 1st floor, The Davidson Building, 5 Southampton Street, London, WC2E 7HA | Maps

Free of charge for BCS Members and £25 + VAT for Non-BCS members.

If you book, and are unable to attend, please cancel your booking via the BCS site and also contact Soheir Ghallab, who is our committee member looking after Tom's courses.

Tom Gilb Hon FBCS and Kai Gilb


You will acquire the skill to write Project Critical Requirements with a focus on expressing the real need and values of the Critical Project Stakeholders. You will know how to identify, separate and specify: Stakeholder Values, Product Values (Qualities), Functions, and required Solutions (Solution Constraints).

This skill set will add tremendous value to any project, and to any conventional project style. It is a skill set sorely lacking in traditional project management methods, as well as lacking in the new Agile development methods (Lean, Scrum, XP etc). It is a necessary supplement.

Workshop mode:

You will be in a team of about 4 people who will pick a project and work out and specify the requirements for that project in a customized Google doc tool. There will be some lectures and lots of practical work on your teams project. At the end of the day, your team will present your team’s work.

PDF Icon Course content

About the Speakers:

Tom Gilb and Kai Gilb have, together with many professional friends and clients, personally developed the Agile methods they teach. The methods have been developed over five decades of practice all over the world in both small companies and projects, as well as in the largest companies and projects. Their website offers free papers, slides, and cases about Agile and other subjects.

There are many organisations, and individuals, who use some or all of their methods. IBM and HP were two early corporate-wide adopters (1980, 1988). Recently (2012) over 15,000 engineers at Intel have voluntarily adopted the Planguage requirements specification methods; in addition to practicing to a lesser extent Evo, Spec QC and other Gilb methods. Many other multinationals are in various phases of adopting and practicing the Gilb methods. Many smaller companies also use the methods. They have advised top management at UK Companies on Business Agile in 2013 and earlier.

Tom Gilb

Tom is the author of nine published books, and hundreds of papers on Agile and related subjects. His latest book ‘Competitive Engineering’ (CE) is a detailed handbook on the standards for the 'Evo' (Evolutionary) Agile Method, and also for Agile Spec QC. The CE book also, uniquely in the Agile community, defines an Agile Planning Language, called 'Planguage' for Quality Value Delivery Management. His 1988 book, Principles of Software Engineering Management (now in 20th Printing) is the publicly acknowledged source of inspiration from leaders in the Agile community (Beck, Highsmith, and many more), regarding iterative and incremental development methods. Research (Larman, Southampton University) has determined that Tom was the earliest published source campaigning for Agile methods (Evo) for IT and Software. His first 20-sprint agile (Evo) incremental value delivery project was done in 1960, in Oslo.

Tom has guest lectured at universities all over UK, Europe, China, India, USA, Korea - and has been a keynote speaker at dozens of technical conferences internationally. He did his first TEDx talk in Trondheim in 2013.

Tom is an Honorary Fellow of the BCS.

Kai Gilb

Kai Gilb has partnered with Tom in developing these ideas, holding courses and practicing them with clients since 1992. He coaches managers and product owners, writes papers, develops the courses, and is writing his own book, ‘Evo - Evolutionary Project Management & Product Development.’

Tom & Kai work well as a team, they approach the art of teaching their common methods somewhat differently. Consequently the students benefit from two different styles.