Agile Techniques Training for Scrum Practitioners Course

Duration: 3 days
Course code: SS-AG-001


This course is intended for any agile team members and Scrum Masters.

  • Software Developers
  • Project Managers
  • Software Architects
  • Scrum Masters
  • Scrum Team Members

Experience with project management and software development.


The Agile Techniques for Scrum Practitioners training course (Agile Software Development with Scrum training) provides a detailed exposure to the various agile principles and techniques to provide a solid foundation for any person working in agile organization. The course is also suited for teams to learn key agile techniques so essential to the success of Scrum and related approaches. The strength of Agile Techniques for Scrum Practitioners training course is that it not only teaches the techniques but that it imparts the proper mindset necessary for success with agile development. After the course, the participants will be able to join or run an agile project as productive team members. The participants will be challenged with numerous real-world examples and tested in problem solving using the techniques taught.


Upon completion of this course, attendees will be able to:

  • Apply key agile practices with sound understanding of agile principles
  • Understand the value of the various agile techniques
  • Productively work in an agile organization
  • Make a successful transition to agile development

Outline for Agile Techniques for Scrum Practitioners Training Course

What is Agile?

  • The Agile Manifesto
  • The Agile Principles
  • Characteristics of Agile Methods
  • Iterative Development, What Does It Mean?
  • Overview of Various Agile Methods

Agile Project Estimation

  • Typical Scheduling Problems
  • From Plan to Measured Progress
  • Agile Estimation
  • Cone of Uncertainty
  • Estimation Techniques
  • Planning Poker
  • Scheduling Tips and Best Practices
  • Burn Down Charts
  • Team Velocity

Case Study 1

  • Hands-On Experience with Iterative Development
  • Hands-On Experience with Agile Scheduling

The Product Backlog

  • What is the Product Backlog?
  • How to Use the Product Backlog
  • Who can contribute?
  • When to Contribute

Extreme Programming

  • History
  • Activities in XP
  • The Planning Game
  • User Stories
  • Best Practices of XP Planning
  • Best Practices Writing User Stories
  • Pair Programming
  • Pair Programming Effect - Empirical Research
  • The Case against XP

Test-Driven Development

  • History
  • Test First Concept
  • TDD Activities
  • Requirements in TDD
  • External Design Using Executable Tests
  • Internal Design through Refactoring
  • Test Selection Strategies
  • Micro Increments
  • Build Strategies
  • Continuous Integration
  • Implementation Strategies and Patterns
  • Faking It
  • Triangulation
  • Obvious Implementation
  • Empirical Research into TDD, Does It Work?


  • What is a Sprint?
  • Initiation of a Sprint
  • Measuring Progress
  • Aborting a Sprint


  • History
  • Overview
  • Scrum Terminology
  • Product Backlog
  • Requirements Forms
  • Sprint
  • Sprint Backlog
  • Use of Burn Down Charts in Scrum
  • The Scrum Roles
  • Product Owner
  • Scrum Master
  • Team Member
  • Pigs and Chickens
  • Scum Meetings
  • Rules for the Sprint Planning Meeting
  • How to Plan a Sprint
  • Rules for the Daily Scrum
  • Keeping Scrums on Track
  • Rules for the Sprint Review Meetings
  • Rules for the Sprint Retrospective Meetings
  • Challenges with Scrum and Distributed Teams
  • Organization Forms for Distributed Teams
  • Distributed Communication
  • Dealing with Time Zones
  • Dealing with Cultural Differences
  • Dealing with Language Differences

Case Study 2

  • Applying Scrum

Lean Principles

  • Introduction to Lean Development
  • Eliminate Waste
  • Amplify Learning
  • Decide as Late as Possible
  • Deliver as Fast as Possible
  • Empower the Team
  • Build Integrity In
  • See the Whole

Comments are closed.