Anthony is a master of tactful navigation when it comes to the ups and downs of corporate contexts. He can coach reluctant Agile appointees into a smoothly functioning dream team with his calm, pragmatic approach. He is a certified trainer of Lean Agile Procurement practices. Ant shares his enthusiasm and knowledge as a coach, facilitator and trainer with organisations and teams in Wellington.
Contact AnthonyJan 03, 2018
I got 'canvas envy' after seeing Jeff Patton's excellent Opportunity Canvas in late 2016, and have been using it in the field ever since. I've made a few changes to it, as people seem to like more structure, especially when it's run in a group. This version tells a 'story' to gain a shared understan... continue reading
Jun 20, 2017
There is a lot of talk right now about how agile product delivery teams should take ownership of customer discovery work, alongside their development activities. This is otherwise known as ‘dual-track development’ and is described in Jeff Patton’s excellent article In this blog I want to talk throug... continue reading
May 23, 2017
Understanding ‘why’ you do agile is important, and the agile manifesto is one of the first things we cover on any Agile Professional Foundation course. I have, however, found the wordiness of some of the principles a little daunting and let’s face it the website does look a bit like my Nan’s wallpap... continue reading
Jan 09, 2017
This post was originally published in Methods & Tools magazine as Breaking Bad: The cult of not giving bad news. I have updated it since then and re-published here as I have collected more learnings since then. It stemmed from something I kept observing, which really bothered me; why is it so ha... continue reading
Apr 05, 2016
I was asked to facilitate a session with a team of systems analysts who wanted to set their objectives for the next 6 months. This was a group of people who spent a large portion of their time embedded within project delivery teams. I wanted to use an approach that could address a number of question... continue reading
Dec 05, 2014
I recently worked with a team of content writers, where we had introduced Kanban to help with the flow and consistency of delivery. The cycle time of work had reduced, but it was still high and as a team they seemed a little flat. They knew ‘what’ they were doing as individuals, but not the context... continue reading
Sept 11, 2014
I have a problem where Agile maturity and benchmarking models are used for comparison of where a team should be in their agile practices adoption; a one size fits all approach where teams must conform or they aren’t doing ‘agile right’. This approach is a fixed repeatable answer that conveniently ig... continue reading
Oct 09, 2013
... or Team Closure within a Project Closure Why? Projects come to an end, which means that a team that has been working closely together, may well be torn apart. This can lead to a sense of loss associated with disbanding some strong team relationships; especially if the team has reached the fourth... continue reading
Oct 27, 2012
When breaking down a large user story to ensure it is sized appropriately, the default is to use Richard Lawrence’s excellent 9 Patterns for splitting a user story. I also use an additional approach; in the first instance I look to see whether it can be split along its acceptance criteria. Every goo... continue reading
Phone: +64 21 514 082
Email: [email protected]
© 2024 Nomad8 Ltd · This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Created by Pitch Studio