Print Page   |   Contact Us   |   Sign In   |   Join
AEA Search
IRM UK | Mastering the Requirements Process: Getting Requirements Right
Map this EventMap this Event Tell a Friend About This EventTell a Friend

This workshop, presented by a real business analyst, gives you a thorough and well-established process for uncovering the real requirements, testing them for correctness, and ensuring that all the requirements have been discovered. The process is used with variations by both agile and traditional projects.

 Export to Your Calendar 11/13/2019 to 11/15/2019
When: 13 - 15 November 2019
Wednesday through Friday
Where: Map this event »
etc.venues Marble Arch
Garfield House,
86 Edgware Rd,
London W2 2EA
United Kingdom
Presenter: James Archer
Contact: +44 (0)20 8866 8366

« Go to Upcoming Event List  

    IRM UK               

Mastering the Requirements Process:
Getting Requirements Right

Use code AEA10 to receive 10% AEA member discount when registering!!

Register On-line:
13 - 15 November 2019, London

Seminar Fee
£1,595 + VAT (£319) = £1,914


Requirements. The most crucial part of development. You can overcome poor planning; you can overcome poor coding. But nobody has ever succeeded with poor requirements. Requirements are the underpinnings for whatever you intend to build, whether it be software, hardware, consumer product, service or anything else. Simply put, only the right requirements will get you the right solution.

Requirements discovery is no longer about producing large, unreadable (and often unread) specifications. Requirements today is about uncovering the real needs of the problem space, understanding the needs of the people who use your solution, recognising the environment for the solution, then, in a timely manner, delivering requirements that are concise, clear and testable.

This workshop, presented by a real business analyst, gives you a thorough and well-established process for uncovering the real requirements, testing them for correctness, and ensuring that all the requirements have been discovered. The process is used with variations by both agile and traditional projects. It starts with the business, for it is only within the business that you discover the real needs. When you know the real needs, it becomes possible to determine what will best serve those needs, and to write the requirements or stories to build the right solution.

Learning Objectives

  • Determine the real needs of your stakeholders
  • Understand the role of the business analyst in agile projects
  • Write agile stories that are more effective and accurate
  • Write requirements that are complete, traceable, and testable
  • Learn diverse elicitation techniques to uncover the real requirements
  • Use the Volere Knowledge Model to ensure you have all the needed information, and nothing that is not needed
  • Understand the need for, and how to write, functional and non-functional requirements.
  • Precisely define the scope of the problem
  • Discover all the stakeholders and keep them involved
  • Uncover the essence of the business
  • Use prototypes, sketches and storyboards to discover hidden needs
  • Use state of the art requirements techniques
  • Get the requirements quickly, and incrementally
  • Write the right requirements and stories

Course Outline

The Requirements Process
The course begins with an overview of the process. It looks at how agile and traditional projects both need requirements but are done differently, the requirements food chain, and the topics to be covered by the course. Delegates will discuss with the instructor their particular problems and objectives for the course.

Project Blastoff
The blastoff builds a foundation for your requirements project by establishing its scope, its stakeholders and the goal. The scope is the problem space or the business area to be studied. The stakeholders are the people with an interest in the outcome. The goal is testable, and ensures that the project will deliver stakeholder value. The Blastoff is also there to ensure that the project is viable and worthwhile.

Trawling for Requirements
At the core of any requirements process is the ability to get people to tell you what they really need, rather than their perceived solution, or what they think you might be able to deliver. We show you how to use business events, apprenticing, use case workshops, interviewing, brainstorming, personas and other techniques to discover exactly what your stakeholders do, and what they need to do it.

This section introduces the brown cow model that gives the business analyst different ways of thinking about the problem, and allows the essence, the real problem to emerge. We also look at innovation – fresh thinking about the problem – and how it is a necessary component of any requirements process.

Functional Requirements
Functional requirements are the things the product must do. You discover them by understanding the real work of the organisation, and determining what part of that work your solution can best do.

The solution is usually established using scenarios – these are great if you need a sign-off – and then specified by well-formed requirements or stories.

Non-functional Requirements
Non-functional requirements are properties the product must have. These include the desired look & feel, usability, performance, cultural, conformance, and so on. Non-functional requirements often determine the success or failure of solutions, so this section demonstrates their importance, and how to find and then precisely specify the qualitative requirements for your solution.


Requirements for Agile Projects
Requirements are equally important for agile projects if your solution is to match the real business needs. Effective agile projects understand that there are two parts: Discovery and Delivery. Discovery involves understanding the real work and the real problem to be solved if you are to deliver the value proposition. It uses business stories to communicate the Discovery findings. Delivery focuses on iterative development and how a story map provides the best guide to the product under development. We also teach you how to write better, more effective stories.

Prototyping and Deviations
Prototyping is a way of discovering requirements by sketching wireframe solutions. Here you assess the merits of low and high-fidelity prototypes, and how scenarios can be used to discover previously-hidden requirements. You also look at the wanted alternatives, unwanted exceptions and potential misuses of the product.

Writing Requirements
There is a need to communicate requirements – how to formulate them and how to include an unambiguous fit criterion. The fit criterion makes the requirement measurable and testable, as well as ensuring the implemented solution precisely matches the client’s expectations.

The Quality Gateway
Testing is most effective when it is done early in the development cycle. Here we demonstrate how to test requirements so that the developers receive the correct requirements. The Quality Gateway assesses the requirements and rejects any that are out-of-scope, gold-plated, non-viable, incorrect or incomplete.

Managing your Requirements
Requirements are the lynchpin of any development effort, and so must be managed effectively. You are given strategies for your requirements management, the requirements knowledge model, how to prioritise requirements, and how to resolve conflicting requirements. We take a look at tools to help manage requirements.

Your Requirements Process
You discuss and determine how to make your own requirements process as effective and efficient as possible. This involves incorporating your own organisational processes into the requirements activity. You build a demonstration of how you will use what you have learned when you return to your own work place.

We want you to be able to use this right away. Each of the teaching chapters is reinforced with a workshop where you apply the concepts presented in the course. You work in a small team to scope the problem space and then discover, specify and evaluate requirements for the solution.

Special Features

  • Your instructor is not an “announcer”. He or she is a practicing business analyst who also happens to be an excellent instructor.
  • The course is written to show real-world situations and provide real-world solutions. You will be able to relate your own work situation to the course.
  • You can discuss your own requirements issues with your instructor.
  • You learn that requirements come from understanding the business and its internal processes, and how the business interacts with its external customers.
  • The course provides a realistic framework for requirements discovery, not a strict methodology. The framework provides the freedom and encouragement to adapt to your own organizational needs.
  • The techniques are applicable regardless of your development method – agile, traditional or anything else.
  • The Brown Cow model to give you different and beneficial ways to look at the problem.
  • The Volere requirements knowledge model which ensures you collect the right information, and the right amount of it.
  • You receive the Volere Requirements Specification Template (downloaded over 20,000 times) with advice on how to make this your own template.
  • A free copy of Suzanne and James Robertson’s best-selling book, Mastering the Requirements Process – 3rd Edition, Getting Requirements Right.

Who It's For

If you want to be involved in delivering the right systems—the ones that get used, then this course is for you.  Typical delegates include:

  • Business Analyst
  • Systems Analyst
  • Requirements Manager
  • Requirements Engineer
  • Agile Team Members
  • Project Leader / Manager
  • Product or Program manager
  • Product Owner
  • Consultant

or similar. Team members on agile projects benefit from understanding how requirements are best done in agile projects.

Users, software customers and business stakeholders have found that this course equips them to participate more effectively in the requirements process, and so ensure that the end solution matches what they really need.



James traces his structured approach to understanding processes and data to solve problems back to being trained as a Cobol programmer 30 years ago. He has 20 years experience practicing and teaching business analysis.  Building on the success of IIBA events in London that he organised, James is a co-founder of this conference. He was awarded a Masters in Innovation, Creativity and Leadership and with Penny Pullan co-edited the book, Business Analysis and Leadership (Kogan Page).   Recent work includes collaborating with NHS and Social Care organisations to set-up self-managed teams of nurses and care workers, adapting an innovative model from the Netherlands; and as a Privacy Champion for ITV International Studios to implement GDPR regulations for ITV.  James has taught Business Analysis in 17 different countries and believes that the key to great business analysis is an inclusive leadership style, thinking innovatively, working collaboratively, acting strategically and helping people discover their real business needs and requirements.

Register On-line:
13 - 15 November 2019, London

Seminar Fee
£1,595 + VAT (£319) = £1,914

Sign In
Login with LinkedIn

Latest News
AEA Events

10/21/2019 » 10/24/2019
IRM UK | Enterprise Architecture Conference co-located with BPM Conference Europe 2019

The Rise of Data Driven Enterprise Architecture | Sydney, Australia

10/28/2019 » 10/31/2019
*** Project World | Business Analysts World, Vancouver, BC ***

The Rise of Data Driven Enterprise Architecture | Brisbane, Australia

11/4/2019 » 11/7/2019
The Open Group - Agile Architecture | Amsterdam, The Netherlands


Join our AEA LinkedIn Group!

This website uses cookies to store information on your computer. Some of these cookies are used for visitor analysis, others are essential to making our site function properly and improve the user experience. By using this site, you consent to the placement of these cookies. Click Accept to consent and dismiss this message or Deny to leave this website. Read our Privacy Statement for more.