Collaborating and Communicating Agile Requirements

Collaborating and Communicating Agile Requirements Course Description

Duration: 2.00 days (16 hours)

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

NOTE: Live Virtual Classroom course length is 3 days.

Next Class Dates

Contact us to customize this class with your own dates, times and location. You can also call 1-888-563-8266 or chat live with a Learning Consultant.

Back to Top

Intended Audience for this Collaborating and Communicating Agile Requirements Course

  • » 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
  • » In-Class Gro

Back to Top

Collaborating and Communicating Agile Requirements Course Objectives

  • » 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

Back to Top

Collaborating and Communicating Agile Requirements Course Outline

      1. Section I: Agile Overview
        1. 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:
          1. Agile Manifesto
          2. Agile Principles
          3. Agile Methodologies
          4. Agile Benefits
      2. Section II. Project Initiation
        1. 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:
          1. Project Charter
          2. Project Roles
          3. Project Planning
          4. Communication
          5. 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.
      3. Section III: Focus on the Customer
        1. 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:
          1. Customer Involvement
          2. Customer Roles
          3. Creating and Using Personas
          4. Constraints
          5. 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.
      4. Section IV: User Stories
        1. 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:
          1. User Stories
          2. Goals and Objectives
          3. Acceptance Criteria and Acceptance Tests
          4. Non-user Stories
          5. 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.
      5. Section V: Product Backlog
        1. 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:
          1. Who owns the Product Backlog?
          2. Functional and Non-functional Requirements
          3. Story-Writing Workshop
          4. Prioritizing the Product Backlog
          5. Maintaining the Product Backlog
          6. Techniques for further elaboration
          7. 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.
      6. Section VI: Estimating and Planning
        1. 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.
          1. Relative vs. Actual Estimating
          2. Using Story Points
          3. Planning Poker (Grenning 2002)
          4. Five Levels of Planning in Agile
          5. Estimating Team Velocity
          6. 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.
      7. Section VII: Release Plan
        1. 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:
          1. Iteration Estimates
          2. Prioritization Revisited
          3. Ownership and Participation
          4. Communication
          5. 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.
      8. Section VIII: Use Cases
        1. 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.
          1. Use Case Advantages
          2. Use Case elements
          3. Success Path
          4. Alternate Paths
          5. Exceptions
          6. 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.
      9. Section IX: Iteration Plan and Execution
        1. 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:
          1. Iteration Planning
          2. Defining "Done"
          3. Test-Driven, Test Often
          4. Demonstrate Working Software (Delivered Requirements)
          5. Inspect and Adapt applied to Requirements
          6. Finding your rhythm
      10. Section X: Retrospective on Communicating Requirements
        1. 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.

Back to Top

Collaborating and Communicating Agile Requirements Course Benefits

  • » 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

Back to Top

Do you have the right background for Collaborating and Communicating Agile Requirements?

Skills Assessment

We ensure your success by asking all students to take a FREE Skill Assessment test. These short, instructor-written tests are an objective measure of your current skills that help us determine whether or not you will be able to meet your goals by attending this course at your current skill level. If we determine that you need additional preparation or training in order to gain the most value from this course, we will recommend cost-effective solutions that you can use to get ready for the course.

Our required skill-assessments ensure that:

  1. All students in the class are at a comparable skill level, so the class can run smoothly without beginners slowing down the class for everyone else.
  2. NetCom students enjoy one of the industry's highest success rates, and pass rates when a certification exam is involved.
  3. We stay committed to providing you real value. Again, your success is paramount; we will register you only if you have the skills to succeed.
This assessment is for your benefit and best taken without any preparation or reference materials, so your skills can be objectively measured.

Take your FREE Skill Assessment test »

Back to Top

Award winning, world-class Instructors

Our instructors are passionate at teaching and are experts in their respective fields. Our average NetCom instructor has many, many years of real-world experience and impart their priceless, valuable knowledge to our students every single day. See our world-class instructors.   See more instructors...

Back to Top

Client Testimonials & Reviews about their Learning Experience

We are passionate in delivering the best learning experience for our students and they are happy to share their learning experience with us.
Read what students had to say about their experience at NetCom.   Read student testimonials...

Back to Top