Collaborating & Communicating Agile Requirements
2502
Collaborating & Communicating Agile Requirements
Classroom
Live Virtual
Private/On Site
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. In this course, you will learn how to gather and manage these 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, allowing for a less "heavy" process in projects that can benefit from quick changes in direction. You will gain hands-on experience with techniques for gathering agile requirements. Through explanatory lectures with demonstrations combined with practice exercises, you will gain the experience needed to create requirements that meet business needs.
Follow-on Courses:
Working in small teams, you will establish a project charterincluding goals and objectives for a sample project. You will participate indefining key roles for project team members and set clear expectations forproject communication. Within your teams, you will brainstorm some customer roles for yourexample project. From the brainstorming, you will consolidate the larger list ofroles into key roles that will be the focus of your sample project. For each ofthe key roles, each team will create personas and share them with the class. Led by the instructor, the class will come up with some user storiesfor a sample project. We will discuss how to determine as a team what isappropriate for your user stories to be effective. In small teams identified previously, you will engage in astory-writing workshop as a means of building a product backlog for your sampleproject. Subsequently, you will participate in prioritizing your product backlogand present the highest priority stories to the class. Using the estimating techniques taught using story points, you''llenjoy a few rounds of Planning Poker with your team to establish estimates foryour highest priority stories. This fun and highly effective method of relativeestimating is certain to be a valuable tool for you to incorporate into your ownestimating process. Each team will establish a release plan for their sample projectincorporating priority, estimates, and velocity as appropriate. We''ll discusshow real experiences of fixed time and requirement projects working well with anAgile release plan. Teams will discuss and document use cases, including alternate pathsand exceptions, for some of their high-priority stories. As a class, we''lldiscuss the relationship between use cases and stories and how they complementeach other.Outline
1. Agile Overview
2. Project Initiation
3. Focus on the Customer
4. User Stories
5. Product Backlog
6. Estimating and Planning
7. Release Plan
8. Use Cases
9. Iteration Plan and Execution
10. Retrospective on Communicating Requirements
Exercises:
Exercise 1:
Exercise 2:
Exercise 3:
Exercise 4:
Exercise 5:
Exercise 6:
Exercise 7:
Upcoming Classes
Dates | Location | GTR | |
---|---|---|---|
May 23-25 (12pm-4:30pm) | EST | ||
Jun 13-14 (9am-5pm) | EST | ||
Jul 6-8 (12pm-4:30pm) | EST | ||
Sep 19-21 (12pm-4:30pm) | EST | ||
Nov 16-18 (12pm-4:30pm) | EST |
Questions?
Whether you need assistance scheduling a class for yourself or for your group, GCA's Education Account Manager's will craft a customized training solution to meet the needs of your organization.