Scrum with Agile Requirements: Achieving Sustainable Agility

Course Tabs

Course Overview
Summary: 

The intention of teams adopting Scrum should be to help them quickly deliver value to customers predictably, sustainably and with high quality. Although Scrum was created for a single team doing development it is rarely used in exactly that context now. It is part of a bigger picture and teams often find themselves competing for limited capabilities. This requires an understanding of how Scrum teams fit into the bigger picture of Agile Product Management.  Given that most companies have limited resources in dollars and time spent by their teams in learning Scrum, this workshop is designed to provide key Agile practices that help software development while providing the core of Scrum that is required. This workshop focuses on those aspects teams need right from the start to successfully adopt Scrum, while only lightly covering aspects that they can figure out on their own (or have a good Scrum Master provide). Experience has shown that teams new to Agile will not usually figure out how to do good Agile development (analysis, design, code and test) on their own.

This workshop looks at the bigger picture of what is needed and provides that which teams find hardest to learn. 

Based on a robust operating model

This course is based on Scrum/ATDD, which is an operating model that incorporates Scrum. This prepares people to adopt Scrum to their environment.  It is also useful for training SAFe® ARTs since it both accommodates large class sized and integrates Agile Product Management which SAFe for Teams does not cover to such a deep extent. If needed, the course can be taught using SAFe and/or customer-specific terminology. 

Supporting materials for new Scrum Teams

After training, you should not have to choose between going  it alone or paying for embedded coaches. By properly preparing you during the workshop and providing needed support materials many of the challenges faced by teams with standard Scrum training can be avoided.

Workshop attendees have access to a collection of templates, online videos, and discussion boards to ask questions of experts and the community.

Templates for Team Agility

All participants in this workshop are provided with six month free access to Net Objectives Premium Content. Here are some of the Team Aglity Templates provided.

  • Outcome-based Thinking Mindset
  • Definition of Done, Definition of Ready, Team DoR-DoD Template
  • The MBI Mindset
  • Team-Agility Scorecard
  • Components of a good Scrum/Kanban Board
  • How we agree to new practices
  • How to do a retrospection
  • Classes of service
  • Agreements to make with other teams and management
  • Ensuring what's being built can be delivered
  • Going  beyond "Scrum-but" (how to change practices that commonly get dropped by those new to Scrum)

Support videos

These short videos help improve common Scrum practices.

Course Objectives: 

Before adopting Scrum, you must ensure it is the correct framework to use. Included in this workshop is a half-day consulting with management to ensure it is the right framework for you and if and how it needs to be tailored. If a flow model works better for you, this workshop can be tailored to that.

Most of the work development teams do are understanding requirements, developing code, and validating that the code meets the requirements. Behavior-Driven Development (the defining of test specifications before developing software) has been integrated into teaching Scrum because although Scrum itself is simple, teams need to learn how to create stories. This workshop integrates story writing with tests into Scrum training to take advantage of this. This is done with the teams' own stories so that  get a start on applying it to their own work.

After the training teams can then take ATDD as far as they want, but their mindset will have definitely shifted towards the better. For more, see How to Start with ATDD/BDD.

More information, read What you need to get started with Scrum on the Net Objectives portal.

Target Audience:

Primary Audience: 
Development team and the Product Owner. The Scrum Master should also attend to facilitate collaboration.
Learning Objectives: 

A CSM course teaches teams the roles, events, artifacts and rules of Scrum. It typically adds estimation, decomposing epics to features to stories. Some trainers include some management of Work-in-Process (WIP). The focus is on the process of building software incrementally.

The most difficult challenge facing teams that are new to Scrum is how to decompose epics into stories small enough to fit in a 1-2 week sprint. Students in this workshop learn to address this challenge by specifying requirements in the form of acceptance criteria. Acceptance Test-Driven Development (ATDD) in conjunction with the Given-When-Then construct of Behavior-Driven Development (BDD) suits this very well. It provides solid guidance to teams to get clarity on what is needed, to decompose large Product Backlog Items (PBIs) into smaller ones and to focus on completing small slices of work. 

Therefore, this workshop covers:

  • Basic Scrum curriculum
  • Lean principles of flow
  • Agile Product Management including concepts of MVPs and MBIs
  • How to use defining acceptance criteria as part of the requirement to achieve small stories
  • Using Scrum as Example so Scrum can be accommodated to your teams’ environments
  • Managing people who have to be split across teams
  • Focusing on realization of value not merely deployment
  • How multiple teams can work together on multi-team projects
Course Description PDF: 

Any Certifications/PDUs

28 PDUs
 

Maximum Number in Class

75 (Approximate. Depends upon make up and experience level of team.)