Introduction to Eliciting and Writing Agile Requirements

This course is a 1-day overview of the concepts of capturing requirements effectively.  It allows teams to determine where they will need more skills for requirement elicitation, procedure analysis, solution analysis and organizational change.  

Unified Software Development Process 

Iterative and incremental writing requirements

Diagram illustrating how the relative emphasis of different disciplines changes over the course of the project

The Unified Process is an iterative and incremental development process. The Elaboration, Construction and Transition phases are divided into a series of timeboxed iterations. (The Inception phase may also be divided into iterations for a large project.) Each iteration results in an increment, which is a release of the system that contains added or improved functionality compared with the previous release.

Although most iterations will include work in most of the process disciplines (e.g. Requirements, Design, Implementation, Testing) the relative effort and emphasis will change over the course of the project.

Architecture-centric

The Unified Process insists that architecture sits at the heart of the project team’s efforts to shape the system. Since no single model is sufficient to cover all aspects of a system, the Unified Process supports multiple architectural models and views.

One of the most important deliverables of the process is the executable architecture baseline which is created during the Elaboration phase. This partial implementation of the system serves to validate the architecture and act as a foundation for remaining development.

Risk-focused

The Unified Process requires the project team to focus on addressing the most critical risks early in the project life cycle. The deliverables of each iteration, especially in the Elaboration phase, must be selected in order to ensure that the greatest risks are addressed first.

Source: https://en.wikipedia.org/wiki/Unified_Process

Upon successful completion of this course, the attendee will gain knowledge in the following:

• Understanding Application Lifecycle Management (ALM) as a starting Framework
• Understanding of the Requirements Workflow
• Writing requirements from different perspectives and what it involves
• Challenges of writing requirements
• Functional vs Non-Functional Requirements
• Use Cases vs. User Stories
• How to model the requirements
• Framework Overview: Agile vs Waterfall

None

• Business Analysts
• Systems Analysts
• Project Managers
• Developers and Testers