Home

Proposal  Management

Management

Training

Support

Technical Project Management

Consulting

Staffing & Mentoring

Training

Tools

Methodology & Beliefs

Partners

Contact Us

 

Developing & Managing Technical Requirements

Managing Requirements throughout the Technical Project Lifecycle – From Initial Identification through Verification & Final Delivery

Effective requirements management throughout the project lifecycle is essential to any project’s success.  In fact, poor requirements management is the number one reason for project failure.
Requirements drive the technical system solution.  This in turn drives cost, schedule, and overall system performance.  From the elicitation and documentation of initial user requirements to the decomposition of user requirements to system requirements to the conversion of system requirements into a design concept (system architecture) through design and integration, requirements management is a critical skill for any technical project manager.
Throughout this process, you must resolve requirements issues with users and developers, maintain requirements traceability, ensure requirements are satisfied, evaluate requirements risks, manage requirements changes, and verify that requirements are being met.
This two-day exercise intensive course will teach you these critical project success skills.
Course Overview
The course provides a detailed look at developing and managing technical project requirements across the project lifecycle.
The course is designed to familiarize you with all aspects of requirements management from elicitation and development of user requirements through final verification and validation of requirements with the customer.
After completing this course you will have an excellent understanding of how to develop and manage requirements to assure satisfied users and customers.
Course Format
The course, based on a threaded case study, is two-days in length.
Interactive lecture sessions and discussion are used to prepare participants between class project phases.  The course is highly experiential to ensure students learn by doing.
Who Should Attend
Technical project and subproject managers, engineering managers, technical professionals, and anyone involved in technical development or integration projects.
You Will Learn

·      Types of requirements: user, system, functional, constraints, etc. and how each applies to the development process

·      How to elicit user requirements using operational scenarios, focus groups, existing operational systems, etc.

·      How to plan for successful system validation and system sell-off

·      How to convert user requirements to system requirements (requirements decomposition & system definition)

·      How to maintain requirements traceability

·      How to create and use different requirements views to ensure all user requirements are met (functional, interface, information flow, etc.)

·      How to define and control system interfaces through ICDs

·      How to plan for system verification (proving requirements are met)

·      How to use requirements to plan for system integration and testing

·      How to define system specifications and technical performance measures

·      How to establish infrastructure for, and manage, requirements changes (user, system, etc.) across the lifecycle

Course Outline

·      Overview

§      What are requirements

§      Types of requirements (user, business, system – functional, nonfunctional, constraints, derived, etc.)

§      Best practices in requirements management

·      Developing user requirements

§      Defining the users

§      Operational scenarios, current system analysis, focus/brainstorm group sessions, other methods

§      Documenting user requirements & getting buy-in from users

§      Managing stakeholder expectations

·      Requirements decomposition & traceability

§      System requirements

§      Types of system requirements: functional, derived, interface, etc.

§      Developing good system requirements

§      System requirements views (functional, interface, information flow, etc.)

§      Requirements simulation

§      Requirements traceability

·      Converting requirements to a technical (system) concept

§      The role of the system architect

§      Developing candidate technical concepts

§      Selecting the architecture (trade studies, simulation, prototyping, etc.)

§      Developing performance specifications

·      Planning for integration & test

§      Developing integration & test plans

§      Requirements role in testing

·      Managing change

§      Change happens

§      The Configuration Control Board (CCB)

§      The change proposal process

§      Full lifecycle change management

 

Send mail to webmaster@projtechinc.com with questions or comments about this web site.
Copyright © 2003 ProjTech, Inc.
Last modified: 01/18/03