Once again The Times, in association with Raconteur, have run their eye over the world of Agile in their 'Enterprise Agility' supplement read by over 1 million Times readers.
Written by Alex Gray
When I am training Scrum courses, I often like to ask attendees: ‘Is anyone using Kanban’? More often than not, a number of people on the course will say ‘Yes we have Kanban boards’. So I say: ‘Great! Have you mapped your workflow on your board, and are you applying WIP (Work In Progress) limits?’ To which the answer repeatedly is ‘No, we just use a Kanban board’.
What follows next is that I am asked to explain the difference between Scrum and Kanban. Which is when I normally get the question: ‘Should we use Scrum orKanban?’
Let’s look at some of the possible deciding factors.
This is a blog post by Andy Hiles, adapted from his article originally published on InfoQ.
Water-Scrum-fall is a hybrid software development approach that aims to successfully combine Waterfall and Scrum approaches into a hybrid Agile way of working. This blog post takes a closer look at how Water-Scrum-fall originated, what benefits and disadvantages it brings to an organisation, and why ‘doing’ and ‘being’ Agile are two completely separate things.
I live near to Headingley Stadium in Leeds. It’s an arty, culturally diverse suburb which also happens to be the home of Yorkshire Cricket and the Leeds Rhinos Rugby league club. I’ve lived here for the last 15 years and have raised my three kids in the shadows of the floodlights and within earshot of the trumpeters, who can oft be heard heralding the arrival of the King of Yorkshire, Geoffrey Boycott, when he takes his seat on the Yorkshire throne room in Headingley pavilion.
However, I was born and raised in the Midlands, which, if you clumsily had to pin it as an UK geography of its own right to a ‘Northern’ or a ‘Southern’ mast, would probably fall into the category of the former. I think that is why I settled in Yorkshire so easily.
A white paper written by Peter Measey, CEO of Radtac, for BCS Enterprise, which discusses the integration of Agile with ITIL® (Information Technology Infrastructure Library).
Agile and ITIL® - And how they integrate
Within the world of method frameworks it is very easy to become polarised on one specific framework and become a ‘fundamentalist’ on that one single method. Method fundamentalism leads to people focusing on why all other method frameworks are wrong and theirs is right, rather than a focus on how integrated method frameworks can enable excellent delivery (which is the whole point of having them). Most method frameworks have something to offer and, via inspection and adaption, they can normally co-exist.
This white paper discusses the integration of agile with ITIL (Information Technology Infrastructure Library).
