Corporate Scrum is a term I use for companies that do traditional Waterfall in 30 day sprints.


Instead of blurring the roles, and making things like quality a team responsibility:

  • analysts analyze
  • testers test
  • programmers program
  • and PMs project manage

There’s nothing inherently wrong with Corporate Scrum. For many it’s a big improvement, and a necessary first step into Agile.

But once teams get the basics of Scrum planning, they should look for opportunities to broaden their skills, and discover their natural abilities, and play more than just one role on projects (for example The Automated Tester).