Shane Ross introduced Daniel Scott-Raynsford of IAG New Zealand at our client event a couple of weeks ago, and in the process he provided some context on why we approached IAG to speak. Many examples of successful DevOps, Agile and Cloud adoption focus on start-up and high-growth companies who are able to bake in these approaches from the start, unencumbered by legacy technology, strict regulatory controls and deep-rooted structures and ways of working.

We often are asked about the roles of Project Manager and Scrum Master for Agile projects. Are they both needed? What are the boundaries? Should they be combined?

So, last month Equinox IT Principal Consultant Carl Weller deliver the 'Agile leadership roles - let's clear up the confusion between PM & Scrum Master' presentation twice for some of our clients. Carl identified that there can be a role for both Project Managers and Scrum Masters on many Agile initiatives...

A couple of weeks ago we hosted a fascinating executive event where Simon Bennett presented on 'Why the Responsibility Process® is the key to succeeding with Agile'. He concluded that when organisations adopt Agile, either top down or bottom up, it often doesn't work because it is an 'outside in' approach of people trying to control other people. The alternative is 'inside out' where people change themselves. Simon positioned the Responsibility Process as an 'inside out' approach for achieving Agile with responsible individuals having responsible interactions.

Every year, each one of us embarks on a new journey into the unknown. Technology, our organisations, market conditions, social expectations, government policies, and many other things continuously change, and each year we need to adapt as individuals to remain relevant and add value in our professional roles. We're here to help you on that exciting journey in 2018. In this blog post we share what our consultants are learning as they adapt and ensure they add value in 2018.

Sprints, user stories, definitions of done, daily stand-ups, backlog grooming, sprint planning, retrospectives, burn-down charts, pair programming, technical spikes, continuous integration, test driven development, specification by example, refactoring…