So you are Post-Scrum?

11-07-2013 by Sebastian Schürmann

I hear a lot of teams are “POST-SCRUM”. That is not a bad thing, given one of the basic mechanics is “Inspect and Adapt”. This is constantly changing the process and it’s properties from sprint to sprint. So, basically you go “POST-SCRUM” after Sprint One (most times it’s the third in practice).

However, you want to take the principles in the agile manifesto into consideration and check if your changes collide with them For further reference, I added them here

  • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  • Welcome changing requirements, even late in development. Agile processes harness change for the customer’s competitive advantage.
  • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  • Business people and developers must work together daily throughout the project.
  • Build projects around motivated individuals. 
  • Give them the environment and support they need, and trust them to get the job done.
  • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  • Working software is the primary measure of progress.
  • Agile processes promote sustainable development. 
  • The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
  • Continuous attention to technical excellence and good design enhances agility.
  • Simplicity–the art of maximizing the amount of work not done–is essential.
  • The best architectures, requirements, and designs emerge from self-organizing teams.
  • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.

I don’t really care what you do. Really. No matter if you go for Scrum-Ban, Pure Kanban or join the #noestimates movement. These principles can help you to check your “POST-SCRUM” setup. Don’t go post beyond them without serious reasoning.

p.s. Don’t fall for marketing people. Scrum bashed waterfall for marketing reasons (and Crystal Clear, RUP for that matter) and was very successful with it. Yes, I am guilty as charged as well. We could get out of this cycle of adversative memes, out there to sell you the next method (and certificates, workshops that come with the new hot shit).

Upcoming Workshops

Pairprogramming Workshop

comments powered by Disqus