Agile Periodization Manifesto [Part 1]
uac-books-banner

Agile Periodization Manifesto [Part 1]

“The only way to win is to learn faster than anyone else.”

This article is my attempt to create workable principles and guidelines of Agile Periodization. I have written extensively about the idea in numerous posts and I let the idea to simmer for some time in my head – now I think I have MVP (minimum viable product) that could be used as a starting point to be adjusted and updated over time (I will come back to MVP when I discuss sprints phases).

how-to-build-a-minimum-viable-product

There are NO given set and reps schemes, block/phases, terminology, progressions and so forth associated with Agile Periodization – what is there are defined processes that you can use with your own planning and your own approaches. Agile Periodization is about learning and finding the best possible solution(s) for your own problems while taking into account risks and uncertainties.

The main difference between agile periodization and “traditional” (let’s call it waterfall) approach is acknowledging the uncertainty and risk ahead and taking that into account when planning. That means avoiding over planning, where the yearly plan is laid out in detail and later followed to the letter. This does not mean Agile Periodization is against long term planning – we still need some elements of “waterfall” planning, but Agile implements iterative planning over time using shorter cycles.

agile-waterfall

Agile Periodization is mainly influenced by SCRUM and Agile/Lean approaches in software development, production and project management in general.

Main cycles of Agile Periodization

The two main cycles of Agile Periodization are:

  1. Release plans or blocks (consists of 2 or more sprints)
  2. Sprints (usually 1-4 weeks long)

In other way, these two cycles are what Mike Tuchscherer refers to as Planned Strategy and Emergent Strategy (click HERE to read Mike’s great article)

Release plans or blocks

“As complexity raises, meaningful statements lose precision and precise statements lose meaning”
Lofti Zadeh

Release plans or training blocks are longer and more generally defined training periods. These periods have elements of “waterfall” planning and are laid out in advance. Training blocks hence represent Strategic Planning.

Most “traditional” approaches in planning represent waterfall method – see for example picture from Set and Reps article:

Needs - objectives - parameters

This is not to say that waterfall is bad or not needed, but it is not enough in managing risk and uncertainty of training process. This process of planning needs to be re-iterated numerous times (and that is the purpose of the sprint phases). Anyway, we still utilize some elements of waterfall in devising block phases, but we deal with the most certain elements, constraints and objectives.

Having said that, the first step in devising a training plan is to lay out the most stable/certain elements, like competition dates (if they are known), holidays, breaks and so forth. Then we lay down training blocks in most general way.

Members Only! Join Us Today and Get Instant Access to All Protected Content Become Member

I am a physical preparation coach from Belgrade, Serbia, grow up in Pula, Croatia (which I consider my home town). I was involved in physical preparation of professional, amateur and recreational athletes of various ages in sports such as basketball, soccer, volleyball, martial arts and tennis. Read More »
free-memeber-button

Home Forums Agile Periodization Manifesto [Part 1]

This topic contains 2 replies, has 2 voices, and was last updated by  Mladen Jovanovic 11 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • 08/01/2016 at 01:04 #17124

    I like this theory on planning and preparation. Mainly, because as each juncture passes it leaves you with many “outs”, the ability to change direction without wreaking havoc on your program. In my case, games are penciled into the season plan, then depending on results of these games the sprints can take different forms or direction. This type of planning allows you to manipulate risk in a safer fashion, rather than all eggs placed into the one/two baskets! I’m currently working in a situation where in the coming weeks we have two games approaching- win both of them and we can proceed with a low risk high reward strategy, win 1 lose 1 and we must go with a medium risk strategy and lose both and we must take a higher risk strategy. These three different scenarios will produce three very variant “sprints”. The beauty of agile periodization is that it allows you to change direction with seamless efficiency which is perfect for team sports IMO. Really like the way you are modelling this Mladen!

    10/01/2016 at 06:01 #17137

    Thanks for commenting Trevor. Yes, in-season sprints could/should be time between games (e.g. 1 week) and game should considered MVP. The blocks preceding season should have similar structure with in-season where some type of MVP needs to be delivered at the end (i.e. friendly game or in-house game) that could be used to help planning the next sprint.

    The only thing to keep in mind is to still have the big picture in mind and not jump bandwagons based on game outcomes/performances. Just use it to “adjust” the big picture. 🙂

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.

Are you ready? Get it NOW!

Increase more than 700% of Email Subscribers!

Your Information will never be shared with any third party