In my last blog post, The most badly implemented, yet most critical, technique in agile projects, I briefly mentioned discipline as being important. In this post I explore this further and dispel a couple of myths associated with Agile development.
How is your Agile or Scrum project going? Is it truly delivering agility to your organisation in the way that the Agile Manifesto or Scrum Guide intends?
We know that DevOps is about combining development and operations into shared multi-disciplinary teams to help organisations become more Agile as software can be built, tested and released in highly iterative and rapid ways.
We also know that Bimodal IT is a Gartner term describing the organisational practice of running a traditional, stable IT mode (mode 1) in parallel with a separate Agile, change-oriented IT mode (mode 2).
In this Blab we explore how these approaches can be used by addressing the question 'How do New Zealand organisations maximise the opportunities from DevOps and Bimodal IT?'.
In the previous posts in this series we have discussed What does DevOps mean in a New Zealand context? and What does Bimodal IT mean in a New Zealand context? Both subjects are topical at the moment and in this Blab we address the question 'How do DevOps and Bimodal IT play together?'.
'Bimodal IT' is a term that Gartner have coined to describe the practice where organisations run two separate modes of IT delivery in parallel. Mode 1 is the traditional approach to IT, focusing on stability, safety and accuracy. Mode 2 uses agile approaches to IT, focusing on change, flexibility and speed. In this Blab we address the question 'What does Bimodal IT mean in a New Zealand context?'.