Agile Software Development (Scrum)

We can teach you Agile/Scrum, fix your current challenges or help you merge existing best practices into your Scrum framework.

What is Agile & Scrum?

Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams.

Scrum is an Agile process for software development and consists of predefined milestones and events that scope, estimate, plan and status the project.

Select, combine and customize the help you need

  • Learn and practice Agile/Scrum (2-day workshop)
  • Address common challenges & frustrations — get a lot more result from your existing Agile investment, e.g.,
    • Fix ambiguous 1-line user stories, sloppy backlogs and projects that drag on 2 weeks at a time with no end in sight
  • Get hands-on assistance to merge Scrum with existing company best practices, PMBOK, or CMMI into an efficient workflow
  • Learn skills to coordinate multiple Scrum teams
  • Learn skills to find defects efficiently — clean up the backlog and code

Tell us what you need and we will build an agenda to fit. Contact us.

2-day workshop

Scrum is a software development methodology based on Agile principles. Agile methodologies promote a project management process that encourages frequent inspection and adaptation, a leadership philosophy using teamwork, self-organization and accountability, with strong customer involvement.

Organizations usually get into a mess with Scrum because of the following reasons: a) requirements in the backlog are sloppy or non-existent, b) release planning has been skipped so there is no end point, c) practices such as risk management, CM, design and cross-team coordination have been forgotten about.

This workshop teaches Scrum and addresses head-on the challenges you face.

After Scrum has been practiced, a team can optionally learn more advanced skills to implement each step. Our other workshops, such as requirements, project planning and peer reviews, are natural extensions to the initial skills learned in Scrum.

Learning objectives

At the conclusion of this workshop, participants will be able to use Scrum to manage their work.


Agenda Details
  • Definition of Agile and Scrum
  • Agile Manifesto
  • Agile Principles
  • Definition of Scrum and Scrum Terms
  • Scrum Details
  • Backlog and Requirements
  • Sprint Planning and Release Planning
  • Sprint Order and Length
  • Tracking Project Progress
  • Sprint Review
  • Sprint Retrospective
  • Exercise: Implementing Scrum

Optional Scrum Additions

  • Risk Management
  • Practices to Add to Scrum (CM, Design, Quality)
  • Dealing with Fixed-Price Contracts (as a Vendor & with Suppliers)
  • Scaling Scrum for Large / Complex Projects
  • Product Owner and Backlog for Large / Complex Projects
  • Coordinating Multiple Scrum Teams
  • Release and Sprint Planning for Large / Complex Projects
  • The Need For Component Integration
  • Documentation and Time Zones for Distributed Teams
  • Steps to Deploy Scrum
  • Merging with Existing Life cycles (Waterfall, Gates and Governance)
  • Implementing with PMBOK and/or CMMI
  • Appendix
  • Optional: Comparison to CMMI
  • Tools
  • Certification options
  • References

Common challenges addressed in workshop

Backlog, user stories, details and grooming

  • Do you have a great product? Causes?
  • Ambiguous 1-line user stories
  • Eliciting requirements — questions to ask
  • User stories vs. Use cases — when and where to use
  • Adding and organizing details
  • Dealing with existing specs
  • Calling everything a user story (requirement, task, bug, to-do)

Release and sprint planning

  • How to make velocity numbers work
  • Factoring in sprint capacity
  • Ongoing surprises and risk mitigation
  • Managing dependencies across teams

Sprint execution, order and engineering activities

  • Speed can be mistaken for progress (many components developed that don’t work together)
  • Architecture/design flaws
  • Time for final system test/validation
  • What version of __ are you working on?
  • ScrumBut: What Scrum steps are really being done and how to raise the bar

Tracking project progress

  • Ignoring burn down data because it is too painful
  • Addressing symptoms and not causes
  • No thresholds set when to replan. How bad is bad? Can you really catch up?

Your next step

  • What to add because there is a problem to fix
  • What to simplify because it is big and cumbersome
  • What to delay because people are not ready for it
  • Getting organized — your next steps


A complete project team (e.g., developer, QA/test, project manager and requirements roles).

Read related Scrum articles

© The Process Group