Requirements Gathering

Training

In London

£ 995 + VAT

Description

  • Type

    Training

  • Location

    London

  • Duration

    2 Days

This training shows you how to precisely define the scope of the business problem, to discover and involve the appropriate stakeholders, to use techniques such as apprenticing and use case workshops to learn what the users really need, to write testable requirements, and to phase the requirements to allow incremental delivery of the product. Suitable for: Business consultants, Business analysts, Project Managers, IT professionals.

Facilities

Location

Start date

London
See map
Grosvenor Gardens, 19, SW1

Start date

On request

About this course

Basic Windows knowledge,

Questions & Answers

Add your question

Our advisors and other users will be able to reply to you

Who would you like to address this question to?

Fill in your details to get a reply

We will only publish your name and question

Reviews

Teachers and trainers (2)

Alain Dries

Alain Dries

Trainer

Van der Stighelen Philippe

Van der Stighelen Philippe

Trainer

Philippe Van der Stighelen is an independent consultant, lecturer and author. As a coach/consultant he has advised a multitude of organizations on designing their information processing and service oriented architecture. Worldwide, Philippe has built a very good reputation as a speaker on conferences and seminars. His lectures are always received with great enthusiasm and get excellent evaluations.

Course programme

"Build the Right Software - First Time."

Requirements Gathering - 2 days

Volere

Requirements are the most misunderstood part of systems development, and yet the most crucial. Requirements must be correct if the rest of the development effort is to succeed. Our training presents a complete process (Volere) for eliciting the real requirements, testing them for correctness, and recording them clearly, comprehensibly and unambiguously.

Software development today has more demands on it than ever; and fewer resources to meet those demands. Getting the software right - the first time - is the most effective way to succeed under these circumstances. Today's requirements process is incremental with quick cycle times. It uses prototypes and scenarios, and it ensures that your developers know precisely what you - and your customer - mean when you write a fit criterion: a concise test case for the requirement.

This training shows you how to precisely define the scope of the business problem, to discover and involve the appropriate stakeholders, to use techniques such as apprenticing and use case workshops to learn what the users really need, to write testable requirements, and to phase the requirements to allow incremental delivery of the product.

2 days course contents

- Determine your client's needs - exactly
- Write requirements that are complete, traceable, and testable
- Precisely define the scope of the project
- Discover the stakeholders and keep them involved
- Use up-to-date techniques such as storyboarding and e-collaboration
- Get the requirements quickly, and incrementally

What you will learn :

Key Principles & Concepts

  • Business analysis.
  • Requirements management.
  • Document management strategies.
  • Structure of business requirement documentation.
  • Types of project users and their characteristics.
  • The value of creating a requirements management plan.
  • The elements in a generic requirements management plan.
  • Project Lifecycle and Systems Development Lifecycle.
  • Concepts, tools & techniques for analysts.

Types of Requirements and Requirements Discovery

  • Attributes and types of effective requirements.
  • Effective versus poor requirements.
  • The types of requirements.
  • Requirements in the development process.
  • Advantages & disadvantages of discovery techniques.
  • Using discovery techniques on a project architecture.
  • Gathering and Structuring Requirements.
  • Techniques used to gather & structure types of requirements.
  • Interviews.
  • Questionnaires.
  • Workgroup / JAD sessions.
  • Surveys and observations.
  • Use cases for gathering/documenting requirements.
  • Data/Process/Workflow modeling.
  • Validating User Requirements.
  • Reasons for validating requirements & methods used.

Documenting User Requirements

  • Developing appropriate documentation.
  • Using requirements for informative communication.
  • Transforming requirements into specifications.
  • Differences between requirements/specifications architecture.
  • Techniques for transformation.
  • Using requirements as foundation for development.

Managing Requirements

  • Understanding the requirements management life cycles .
  • Identify, categorize and assess stakeholders.
  • Create a communication plan.
  • Understand risk factors.
  • Common requirements issues that lead to project challenges.
  • Traceability and global requirements mapping.
  • Identify multiple views & global requirements.
  • Understand how to review documentation standards.
  • Select tools and techniques for specific types of projects.
  • Evaluate a policy for project needs.
  • Understand acceptance criteria and project test results.

Requirements Gathering

£ 995 + VAT