Top Navigation Menu

Collaborating and Communicating Agile Requirements


In just two days, learn how to:


  • Master writing user stories

  • Appreciate how best known methods in traditional requirements processes can apply to Agile methods

  • Communicate requirements using agile techniques to bridge the customers’ and developers’ needs.

  • Identify stakeholders and user roles to ensure that all requirement viewpoints are elicited

  • Create and maintain a product backlog

  • Prioritize requirements so that the most important customer needs are delivered first

  • Formulate an iterative project plan with feedback cycles that keep the project on track

  • Estimate business value for requirements to track how a project contributes to the enterprise

  • Develop requirements in an iterative approach to capture the details at the appropriate time


Classroom Live Online  14 PDU’s + 12 CPE’s + 14 CDU’s Custom Sessions


FREE Items

Select a free item included with your class. (more info)

Class Description

Eliciting Effective Requirements for Your Agile Project!

In just two days, learn how to:

  • Master writing user stories
  • Appreciate how best known methods in traditional requirements processes can apply to Agile methods
  • Communicate requirements using agile techniques to bridge the customers’ and developers’ needs.
  • Identify stakeholders and user roles to ensure that all requirement viewpoints are elicited
  • Create and maintain a product backlog
  • Prioritize requirements so that the most important customer needs are delivered first
  • Formulate an iterative project plan with feedback cycles that keep the project on track
  • Estimate business value for requirements to track how a project contributes to the enterprise
  • Develop requirements in an iterative approach to capture the details at the appropriate time

Gathering Requirements for an Agile Project

Project failures are often due to poor requirements gathering, analysis and planning. Traditional requirements documents may not contain complete and accurate requirements due to rapidly changing business environments. Agile requirements gathering, by moving detailed requirements closer to implementation, allows for rapid response to change. “Collaborating and Communicating Agile Requirements” will show you how to gather and manage these requirements.

Organizing and Managing Requirements

Traditional requirements are documented in a requirements specification. Changes to the requirements are managed through a change process. This course will demonstrate alternative ways of documenting requirements and managing changes. These alternatives can allow for a less “heavy” process in projects that can benefit from quick changes in direction.

Discover Real-World Techniques

This two-day course will give you hands-on experience with techniques for gathering Agile requirements. Explanatory lectures with demonstrations, combined with practice exercises will provide you with the experience needed to create requirements that meet business needs.

In-Class Group Exercises:

In-class exercises help you identify and examine firsthand problems that you may experience. With our demonstrations and case studies, you will discuss ways you can handle problems up front, and how you can make improvements, throughout the phases of requirements development.

  • Establish a project charter, define roles for the project team and determine appropriate communication
  • Define customer roles and personas
  • Document requirements with user stories
  • Create and maintain a product backlog
  • Determine customer value and priority for each user story
  • Participate in engaging and innovative estimating techniques
  • Communicate a release plan for a product
  • Document requirement details with use cases
  • Plan and execute an iteration cycle
  • Learn how to continuously improve requirements collaboration

20 Immediate Benefits of Participating in this Workshop

  1. Learn how to adapt quickly and positively to rapidly changing business needs and priorities
  2. Learn how to collaborate on requirements for a project
  3. Learn how customer satisfaction increases with more frequent customer-developer feedback
  4. Align development to business needs to provide business value quickly
  5. Learn the benefits of using Agile methods to communicate requirements
  6. Understand the five levels of planning in Agile
  7. Use agile requirements as an effective basis for planning and testing
  8. Learn more effective methods for accurate estimating while elaborating requirements
  9. Understand the characteristics of a well-written agile requirement
  10. Understand how to plan frequent releases so that customers can recognize benefit quickly
  11. Minimize risks of ineffective solutions by obtaining frequent feedback
  12. Shorten project schedules by prioritizing requirements to get the most important needs met first
  13. Keep business requirements focused on the customer
  14. Model user roles to capture the needs of specific users
  15. Identify gaps not usually found or corrected in requirements gathering
  16. Reduce requirements inventory in process
  17. Define the right requirements at the right time
  18. Know what to do when new technologies render features of your project obsolete
  19. Learn how to determine an iteration plan
  20. Get earlier validation of requirements against a working system to keep a project moving in the right direction

Course Outline

Section I: Agile Overview
More than simply a methodology or approach to software development, Agile embraces a set of principles that drive more effective software development. Agile focuses on the customer, embraces the ever changing nature of business environments and encourages human interaction in delivering outstanding software. In this introduction, we’ll discuss the following:

•Agile Manifesto
•Agile Principles
•Agile Methodologies
•Agile Benefits

Section II. Project Initiation
Among the key contributing factors leading to project failure is poor communication between the customer and developer groups. It is critical, therefore, that each successful project start out right. In this section we’ll cover the following topics:
•Project Charter
•Project Roles
•Project Planning

Class Exercise
Working in small teams, you will establish a project charter including goals and objectives for a sample project. You will participate in defining key roles for project team members and set clear expectations for project communication.

Section III: Focus on the Customer
It is critical that the customer be the focus of a product throughout the development lifecycle. Every requirement should bring some value to the customer. Therefore, prior to defining requirements, it is important to define the customer. This will include the following topics:
•Customer Involvement
•Customer Roles
•Creating and Using Personas

Class Exercise
Within your teams you will brainstorm some customer roles for your example project. From the brainstorming, you will consolidate the larger list of roles into key roles that will be the focus of your sample project. For each of the key roles, each team will create personas and share them with the class.

Section IV: User Stories
User stories are a way to capture requirements from a customer point of view. Stories do not capture all of the detailed requirements, but require enough information to estimate and plan. A proven tool used in Agile teams to capture initial requirements, in this section we will explore the following topics:
•User Stories
•Goals and Objectives
•Acceptance Criteria and Acceptance Tests
•Non-user Stories

Class Exercise
Led by the instructor, the class will come up with some user stories for a sample project. We will discuss how to determine as a team what is appropriate for your user stories to be effective.

Section V: Product Backlog
The Product Backlog is the complete list of desired elements, or requirements, for the product. It is NOT a Requirements Specification, but a high level identification of what the software may satisfy. In this section we will discuss effective means of creating, prioritizing and maintaining the Product Backlog. We will peruse the following topics:
•Who owns the Product Backlog?
•Functional and Non-functional Requirements
•Story-Writing Workshop
•Prioritizing the Product Backlog
•Maintaining the Product Backlog
•Techniques for further elaboration

Class Exercise
In small teams identified previously, you will engage in a story-writing workshop as a means of building a product backlog for your sample project. Subsequently, you will participate in prioritizing your product backlog and present the highest priority stories to the class.

Section VI: Estimating and Planning
Among the greatest challenges in developing software and delivering against stakeholder expectations is estimating accurately and subsequently planning how those expectations can be met. Agile cannot make that challenge disappear, but offers some very helpful tools that enable teams to set and meet the appropriate expectations.
•Relative vs. Actual Estimating
•Using Story Points
•Planning Poker (Grenning 2002)
•Five Levels of Planning in Agile
•Estimating Team Velocity

Class Exercise
Using the estimating techniques taught using story points, you’ll enjoy a few rounds of Planning Poker with your team to establish estimates for your highest priority stories. This fun and highly effective method of relative estimating is certain to be a valuable tool for you to incorporate into your own estimating process.

Section VII: Release Plan
The release plan identifies a goal for the stories that will be included for a release of the software. Through the prior processes, the team will have prioritized the stories and estimated the team velocity. These key elements will come together to give the team a level of confidence that they can deliver the necessary requirements for a product release in what is normally a fixed timeframe. We’ll examine the following topics:
•Iteration Estimates
•Prioritization Revisited
•Ownership and Participation

Class Exercise
Each team will establish a release plan for their sample project incorporating priority, estimates and velocity as appropriate. We’ll discuss how real experiences of fixed time and requirement projects that work well with an Agile release plan.

Section VIII: Use Cases
At the appropriate time, prior to entering into the development of a story, requirements will need to be discussed in more detail. Use cases are a proven method for documenting the appropriate detail from a user interaction point of view. In this section, the instructor will introduce use cases and discuss some of the foundational elements that support the development process.
•Use Case Advantages
•Use Case elements
•Success Path
•Alternate Paths

Class Exercise
Teams will discuss and document use cases, including alternate paths and exceptions, for some of their high priority stories. As a class we’ll discuss the relationship between use cases and stories, and how they complement each other.

Section IX: Iteration Plan and Execution
An iteration is a fixed amount of time in which stories/requirements will be developed, tested and ready for release. Because the requirements communication process takes you into each iteration throughout the product release, we’ll explore the iteration planning and execution process. During this section we will discuss the following topics:
•Iteration Planning
•Defining “Done”
•Test-Driven, Test Often
•Demonstrate Working Software (Delivered Requirements)
•Inspect and Adapt applied to Requirements
•Finding your rhythm

Section X: Retrospective on Communicating Requirements
Using Agile Methods – Retrospectives are a key practice in Agile. We will take an opportunity to review our learning collectively and how we can improve. Each participant will identify one or two things that they will adapt in their working environment based on their learning. The instructor will also identify any elements of the course that should be adapted for a better learning experience, thus benefiting future course participants.

Who Should Attend?

This course will be valuable to all those involved in developing technology solutions that meet business requirements and would like to do so using Agile methods. This class is for you if you are a….

•Business Customer or Partner
•Product Manager or Customer Representative
•Business or Systems Analyst
•Architect or Developer
•QA Tester or QA Engineer
•Project Manager or Team Leader
•IT Manager/Director

Additional Info

Class Length

3 Days

Class Locations

Austin-Round Rock-San Marcos, TX, Columbus-Marion-Chillicothe, OH, Denver-Aurora-Boulder, CO, Grand Rapids-Muskegon-Holland, MI, Houston-Baytown-Huntsville, TX, Jacksonville FL, Kansas City-Overland Park-Kansas City, MO-KS, Live Virtual Class-Attend from Anywhere, Minneapolis-St. Paul-St. Cloud, MN-WI, Raleigh-Durham-Cary, NC, San Jose-San Francisco-Oakland, CA, St. Louis-St. Charles-Farmington, MO-IL, Washington-Baltimore-Northern Virginia, DC-MD-VA-WV

Class Dates

Apr 21, 2016 thru Apr 22, 2016, Aug 22, 2016 thru Aug 23, 2016, Dec 09, 2015 thru Dec 10, 2015, Dec 14, 2015 thru Dec 16, 2015, Dec 19, 2016 thru Dec 20, 2016, Feb 08, 2016 thru Feb 10, 2016, Feb 17, 2016 thru Feb 18, 2016, Jan 11, 2016 thru Jan 12, 2016, Jan 20, 2016 thru Jan 22, 2016, Jul 11, 2016 thru Jul 12, 2016, Jun 09, 2016 thru Jun 10, 2016, Mar 21, 2016 thru Mar 22, 2016, May 16, 2016 thru May 17, 2016, Nov 03, 2016 thru Nov 04, 2016, Oct 24, 2016 thru Oct 25, 2016, Sep 22, 2016 thru Sep 23, 2016

Guarantee & Policies

Course registration info, our commitment to your privacy,

and general terms and conditions


Course registration information:

All courses carry Project Consult’s Guarantee of 100% Satisfaction: 
Project Consults provides an unsurpassed training experience. If for any reason you are not satisfied with the program, simply notify the instructor or registrar of your intent to withdraw from the program prior to the first morning break, turn in your course materials and receive a 100% refund. If at the end of the program day, you are unsatisfied with the program, we will credit your tuition towards a future program of your choice.

Payment Policy:
Payment is required at time of registration. Approved forms of payment include a company purchase order, PayPal, or credit card. We accept Visa, MasterCard, American Express, and Discover.

Courses are available as onsite training: 
All courses are available as onsite training at your location. On-site options can be very cost effective.

Course Hours:
This course begins promptly at 8:30 AM and ends at 4:30 PM, unless otherwise noted on the course page or in email notifications. Please arrive at 8:00 AM on the first morning of class to sign-in and meet your fellow attendees.

Shipping of Course Materials:
In an effort to reduce paper waste, course materials for live-online sessions will be digital. You will recieve information on how to obtain your course materials in your confirmation email.

Substitution & Cancellation Policy: 
If a change needs to be made to your public course registration (cancel, transfer, or substitution) Project Consults must receive written notice via email at If a cancel or transfer request is made less than 15 business days prior to the class start date, payment will still be due, no refunds will be issued and you will be charged a $200 change fee. Your paid tuition will be available for one year to be used as a credit towards another course of equal value; only one reenrollment opportunity is allowed. Failure to attend the course without written notification will result in forfeiture of the full course price. Student substitutions may be made at any time prior to the start of class free of charge. If a student substitution is made for a live, online session and any hard-copy materials have been provided to the initial student, it is the responsibility of the client to pass along those materials to the new attendee. If Project Consults is forced to cancel a course for any reason, liability is limited to the registration fee only. If you have questions or concerns, please contact or call 469-424-1084.

In certain situations, Project Consults may not have the required enrollment to hold a course as scheduled. We do our best to confirm every class, but our main mission is to provide students with the skills and knowledge to have a positive impact on their work performance. Based on this, should there be a cancellation for a class you are enrolled in, Project Consults will proactively automatically enroll you into the next available live, online session of the same course to provide you with the knowledge you originally needed. You will be notified during this process and have the ability to work with an Project Consults representative regarding alternate options if you are unable to attend the new session.

Substitution & Cancellation Policy (PMP Boot Camp): 
If you are unable to attend your scheduled training class, please contact us directly at 469-424-1084. We require a 16 calendar day notice to reschedule or to cancel any registration (and receive refund for payment). Failure to provide the required notification will result in a 100% charge of the course fee. If a student does not attend a scheduled course without prior notification, or contacts us to cancel within the notification window, the student will have the option to pay a $200 reschedule fee to attend one of the live, online sessions of the PMP Boot Camp. Within the notification period, only student substitutions will be permitted.

Hotel Reservations:
Project Consults does not set aside a block of rooms for class participants. If you wish to book a sleeping room please contact Project Consults for the best hotel options or recommendations. For directions to the course location please call Project Consults or you may also contact the training center or hotel directly.


There are no reviews yet.

Be the first to review “Collaborating and Communicating Agile Requirements”