3 ms·

Agile should also be subject to Agile. I like to think of it in terms of the Viable System Model in which the system has the potential to change itself based up

• gutnor 14y ago
  Agile is a toolbox of best practices and tricks. You need to use the ones that make sense. That is formalised in methodologies like SCRUM by doing a retrospective after each sprint. For inexperimented teams, it is a good idea to start with out-of-the-box scrum and remove/replace bits that are not working out for team after a while. For experimented teams, you just start with just a daily scrum end of day and add bits as you go along. (effectively start with 1 day iteration)
• adrianhoward 14y ago
  Agile should also be subject to Agile It is (or should be). For example: * XP folk very explicitly state that you shouldn't be "doing XP" N months down the road. You should be optimising your process * The Kanban/Lean folks whole method is about having a process for process improvement * Scrum very explicitly has Sprint retrospective and reviews aimed at looking what happened and changing the process to improve results next time. * Crystal is all about aligning the amount of process you do to the working context you're in. Of all the agile processes Scrum is really the only one that says you must do certain things in a certain way - and even there it's a very light framework of five events and three artefacts) that gives you a space to figure out your own process in.