KT-7051 Collaborating and Communicating Agile Requirements Training - Minneapolis, Minnesota IT MN Technical Financial New York, NY
Knowledge Transfer Microsoft Certified Silver Training Partner CPLS
Knowledge Transfer is a Microsoft Certified Silver Learning Partner
Oracle University

 

Microsoft Certified Training Partner CTEC
Search for a Course Topic:
Public Courses
Corporate Services & Training
 

 

 



 Course Search
Keyword
Course #
State

 Training Delivery
 
Training Delivery
Custom Curriculum
Course List
Certifications
 
 Main Menu
 
Home
View Courses
Site Index
 
 


Collaborating and Communicating Agile Requirements


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 & 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

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

 
Click here to view the Course Outline
     
Prerequisite: 
 
   
     
Duration: 
2 Days  
     
     

View Printer Friendly Page

 


To Inquire About Future Classes

Request a class date

if one is not scheduled.



Comments on the Course

14 PMP PDUs are awarded upon full completion of Collaborating & Communicating Agile Requirements .

Please call for Group Rate for 3 or more registrations. 

  • Registrations must be made at the same time to receive discount. 

If class start date is less than 5 business days from today, please call for pricing.