Breaking the Cylinders of Excellence (in the Australian Government)

YOW-Nights_Logo_stackedAt the recent YOW! Night in Brisbane (as well and Sydney and Melbourne), Lindsay Holmwood (the Head of Technology at the DTA) presented “Breaking the Cylinders of Excellence”. It was a rare experience to hear the story of how the DTA is using cutting edge development practices to help the government catch up with, and even exceed, the public sector. 

  • DTA – aid transformation in government, small agency
  • Delivery hubs in Sydney and Canberra – help identify and plug capability gaps in teams
  • Prototype of how government services could work  gov.au/alpha
  • Digital Service Standard – 13 characteristics on what good looks like in government, useful in organisations as well
  • Cloud.gov.au  – government cloud service, usage growing, continuous delivery pipeline (which is a major change for government who are used to 2 changes per year)
  • The unit of delivery is the team – not about individuals, but the team – borrowed from GDS
  • Government is slow, but government is designed to be stable, they cannot fail, they have characteristics that are resistant to change
  • Myth that organisations must choose between speed and reliability, high performing organisations deploy more frequently, have shorter lead times, fewer failures and recover faster, but they also have a greater profit
  • Want to deliver like a startup but be stable like a government
  • Not a lot of cross pollination between departments currently
  • Read the policy! – quite often the process is not mandated
  • Document what works and doesn’t so it becomes a repeatable pattern – ie. running a meetup inhouse, don’t tell me I can’t do it, tell me how I can run it without being thrown in jail!
  • Stick with technologies the government is comfortable with if you are changing the delivery engine
  • Security matters – prevention is a battle you will always lose, detection is your best defence – aggregate and log in one place, identify threat signatures, etc
  • Embed security people on big services so it is part of the architecture
  • Proactive testing between different governments around the world on similar platforms
  • Simplest security breaches make the most mess – infected excel macros, leaving free USB keys in the foyer that are malware infected
  • Need to put user needs first – alpha mockup using tools like Jeckyll, then beta then live
  • Lots of people strictly interpret the design and delivery guides – they are guides not rules!
  • Create a longer runway by pulling tech forward – turn down the volume of design, turn up the volume of tech
  • If it hurts, do it more often!
  • Fixed cost delivery with agile is a thing, agile is a way to de-risk in the government
  • Don’t put manual testing on the critical deployment path – have special skills on hand for accessibility, performance and security

Episode 119: Agile (Raccoon) is Dead with “Pragmatic” Dave Thomas

The Agile Revolution Podcast

davethomasCraig and Tony are at YOW! Conference and get the opportunity to sit down with Dave Thomas, signatory to the Manifesto for Agile Software Development and have a great discussion about:

  • Dave’s talk “Agile is Dead (Long Live Agility)
  • Agile as a word has become meaningless, don’t follow the off-the-shelf processes, apply small corrections to move forward
  • Story of Stone Soup is like Agile consultancies, the hard work is done by the companies
  • Scrum is a good starting point due to its simplicity
  • Raccoon is a noun, so not a good replacement name for Agile, because you can buy a pound of it
  • 1,000 working on one thing can never be Agile, you have to make enterprises agile before you can run an agile project
  • The values in the Agile Manifesto hold up well, would have been nice to have had more diversity, had no expectation they were…

View original post 203 more words

Episode 118: YOW! 2015 Brisbane Vox Pop

The Agile Revolution Podcast

yow_2015_conference_-stacked-pngCraig and Tony are once again roaming the lunch hall at YOW! 2015 in Brisbane, where they catch up with a number of people including:

View original post 27 more words

Episode 117: The Changing Role of a Tester with Mark Pedersen

The Agile Revolution Podcast

mpCraig is at the YOW! Connected conference and talks to Mark Pedersen, the CTO at KJR, and they talk all things quality and testing:

  • the changing role of a tester in an Agile environment, it clarifies the role rather than making it blurrier
  • in an Agile environment it does not make sense to have a Test Manager role anymore
  • the number of dedicated testing roles are decreasing, but becoming more important and valuable
  • most organisations say that they use both waterfall and agile frequently
  • build your skills in either a quasi analysis / product owner / acceptance criteria role or get up to speed with sensible technical automation tools for your tech stack
  • TDD – good idea but not many organsations practicing it in a dedicated way, unit testing in most industries is a luxury
  • BDD – does not make TDD obsolete, defining acceptance criteria upfront helps understand…

View original post 90 more words

Agile Brisbane – Agile Coaching Nightmares: Lessons We Can Learn From Gordon Ramsay

AgileBrisbaneMy presentation from the Agile Brisbane meetup called “Agile Coaching Nightmares: Lessons We Can Learn From Gordon Ramsay” is available on Slideshare.

When you look for inspiration in the Agile Coaching community, the name Gordon Ramsay is probably not the first name to come to mind. He has been known to be belligerent, condescending and downright rude, but underneath this brute facade is a treasure trove of skills and talents that influence change.

In this presentation we will draw insights from his ‘Kitchen Nightmare’ escapades and draw parallels with how much his work aligns with that of an Agile Coach and the goal to successfully drive change and introduce a number of models and techniques that are indispensable in the coaching toolkit.

Some pictures:

Here are some tweets and feedback from the talk:

First time to Agile meetup, exceeded expectation, will be back – Steve S

Awesome presentation. Thanks very much Craig! – Emi

This was my first Agile meetup. A great presentation and a well run event. – David Wilkinson

Excellent presentation. Some great reminders! – BronwynSC

This was my first time and it was a great presentation – Arthur

Always a pleasure hearing you speak Craig. I’ll be sharing your slides with the Elabor8 team! – Ryan McKergow

Thanks for a great presentation – Rob Lawes

 

 

Episode 116: The Heart of Modern Agile

The Agile Revolution Podcast

heartmodernagileCraig and Tony are sipping a sarsaparilla or two on a balcony in Brisbane and start trying to dissect the state and heart of modern agility:

View original post 92 more words

Episode 115: Connecting Developers & Designers with Chris van Raay & Tom Brodhurst-Hill

The Agile Revolution Podcast

115At the YOW! Connected conference, Craig sits down with Chris van Raay and Tom Brodhurst-Hill and talks about bridging the gaps between developers and designers:

  • Chris van Raay talk “Bridging the Designer – Developer Divide
  • Tom Brodhurst-Hill talk “Design Driven Mobile Development
  • Typically most organisations have separated development and design teams which results in a very linear process
  • Need simple design documentation as a “single source of truth” because you shouldn’t need to specify styles more than once and it helps reduce effort and obtain a consistent design
  • Use tools such as PaintCode to create a colour palette which serves as documentation as well as a static analysis test
  • Need leadership to ensure there is an agreed approach, set the standards and create discipline
  • When building features need to decide when to leave work that is consistent across features, in relation to design, this should be…

View original post 59 more words

Agile 2016 Keynote: Modern Agile

InfoQAt the recent Agile 2016 conference in Atlanta, Joshua Kerievsky, CEO of Industrial Logic and author of ‘Refactoring to Patterns’ gave a thought provoking keynote around the idea of Modern Agile.

Modern Agile WheelSource: Agile 2016 Keynote: Modern Agile

Agile Alliance Elects 2017 Board of Directors (and I am one of them!)

Agile AllianceI was honoured to be elected to the Agile Alliance Board of Directors at the recent Agile 2016 conference in Atlanta. My term commences in January 2017. I have always been a supporter of the many initiatives that are run by the Agile Alliance and I am looking forward to continuing the great work of building the Agile community.

This is the press release from the Agile Alliance:

Slate overwhelmingly approved at annual member meeting during Agile2016 conference

Portland, Ore, August 4, 2016 — Agile Alliance, a global nonprofit organization committed to advancing Agile development principles and practices, today announced that it has overwhelmingly approved the slate of candidates put forth for the 2017 Board of Directors. The board — comprised of Agile thought leaders from a variety of backgrounds — shares its passion to deliver software better every day with Agile professionals around the world.

Results for the 2017 election were reported to the Agile Alliance membership by Board Secretary Shane Hastie at the annual membership meeting held July 27 at Agile2016, the organization’s annual North American conference at the Hyatt Regency Hotel in Atlanta, Georgia.

The Agile Alliance membership elected three members to two-year terms on the Board of Directors – Juan Banda (Bolivia) was re-elected, and Ellen Grove (Canada) and Craig Smith (Australia) were newly-elected. All three will assume their board seats on January 1, 2017.

  • Juan Banda founded Percella, an Agile consulting and training company headquartered in Cochabamba, Bolivia. He is passionate about serving his team, clients and community by building beautifully crafted software. Banda has served on the board since 2013.
  • Ellen Grove hails from Canada. She is an Agile coach and trainer at Agile Partnership in Montreal where she helps teams to do better work by coaching them to create the circumstance in which they can work most productively and effectively.
  • Craig Smith is an Agile coach and director at Unbound DNA, a consulting company in Brisbane, Australia. An Agile practitioner for more than ten years, he is one of his country’s heaviest contributors to the local Agile community. Craig was on the program team for last year’s Agile Alliance Technical Conference.

 

Other 2017 board members include Rebecca Parsons (Chair, USA), Linda Cook (Treasurer, USA), Declan Whelan (Canada), Stephanie Davis (USA), Victor Hugo Germano (Brazil), Paul Hammond (England), and Phil Brock (Managing Director, USA). The board wishes to thank outgoing members Ola Ellnestam (Sweden) and Shane Hastie (Secretary, New Zealand) for their years of service in furthering Agile Alliance’s goals.

About Agile Alliance

Agile Alliance is a nonprofit organization dedicated to promoting the concepts of Agile software development as outlined in the Agile Manifesto. With nearly 33,000 members and subscribers around the globe, Agile Alliance is driven by the principles of Agile methodologies and the value delivered to developers, organizations and end users. Agile Alliance organizes the annual North American Agile20xx Conference, the industry’s premier event that attracts practitioners, academia, business and vendor-partner community members worldwide.

Media Contact

Pam Dyer
Marketing Chief, Agile Alliance

This was my candidate statement for the slate:

Craig Smith (Australia)

I have been active in the IT industry for over 20 years covering many roles within software development and testing lifecycle. I have been an Agile practitioner for over 10 years as an Agile Coach and accredited trainer. I am an organiser of the Agile Brisbane Meetup Group, a long-term advisor to the Agile Australia conference, director of the YOW! development conference in Australia, co-host of the Agile Revolution podcast and an Agile Editor for InfoQ, I have contributed to a large number international conferences as both a speaker as well as behind the scenes in numerous program committee roles. I have spent many years contributing to the growth of the Agile community in Australia with a primary aim of helping teams deliver quality outcomes.

The role of the Agile Alliance is to support those who explore and apply Agile principles and practices to make the software industry productive, humane, and sustainable. I believe that we need to continue to encourage new and innovative ways to help the worldwide Agile community grow whilst helping spread the values, principles and practices to other disciplines that wish to learn and adapt approaches to agility in their respective domains.

Agile has continuous improvement at its heart and a core challenge for the Agile Alliance is to bring the combination of process and technical practices closer together whilst looking further left and right to the upstream business and downstream users. As a board member, I hope to represent the thoughts and direction of the worldwide Agile community in all of its forms and continue to ensure that the original values and principals are upheld.

Agile Coaching Institute Competency Cohort – Learning and Reflections

In August 2015 it was great to have Lyssa Adkins and Michael Spayd from the Agile Coaching Institute back out in Australia to run their full three day  Coaching Agile Teams course. I had successfully been able to lure them out in 2013 for the YOW! Conference where they ran their 2 day course, so when they were out again I was honoured to be invited to be an assistant (alongside Victoria Schiffer) for their Melbourne class. That class was memorable for many reasons, including the great bunch of Agile Coaches that attended it (but that is another story for another day).

During that class, Lyssa had mentioned a new program called the Competency Cohort and mentioned that she would live me to be a part of it. One of the selling features for me was the pathway to the ICAgile Coaching Expert certification that I had been pondering for over a year. In typical fashion I mulled on the program for a number of weeks until the last responsible moment (about 48 hours before tickets closed) I mafe the decision to join.

This decision was not one that I took lightly. Firstly it is not a cheap program (not helped by the conversion rate to the Australia dollar and being a freelancer) and an initial 9 month commitment was going to be difficult with my workload, but I decided that a program with ACI and the opportunity to be part of something and new groundbreaking, along with the certifications that would be gained was worth the investment of time and money.

Here is the outline of the initial program:

Competence Cohort for Agile Coaching Mastery

A Rigorous Practice-Based Program for Building Competence and Confidence

The Agile Coaching Institute (ACI) creates transformation agile coaches who can shift individuals and whole teams to leverage agile to its best benefit.  To do this, we strive to build real world competence and confidence in those we teach and coach.

The Competence Cohort paves the way to proficiency, culminating in ACI’s first-ever certification, Certified Transformation Coach – Teams™ (CTC-T).   It is the next step after taking ACI’s classroom learning for those ready to radically expand their capabilities, build solid competence and achieve industry certification recognition.

Proficiency in the skills of agile coaching requires practice. This rigorous 10-month program places an emphasis on practice and feedback opportunities through skill drills, peer coaching, ongoing group work, and one-on-one supervision of actual agile coaching, mentoring, teaching and facilitation sessions.  In addition, upon successful completion of four supervision sessions in the program, you will be eligible to attain the ICAgile Expert in Agile Coaching Certification (ICE-AC), an important milestone and cause for celebration during the program.

Outcomes of the Competence Cohort Program

  • Close the gap between learning and application of agile coaching competencies and skills through modeling, in-cohort practice, real-life practice and graded supervisions.
  • Integrate agile coaching skills into your everyday real-world situations, including professional coaching, facilitating, teaching, and mentoring.
  • In-depth personalized assessment and feedback about your agile coaching from ACI’s top-notch faculty.
  • Achievement of two industry certifications: Certified Transformation Coach – Teams™ (CTC-T) and ICAgile Expert in Agile Coaching (this certification is optional, and requires an additional, significantly discounted fee payable to ICAgile).  If you opt out of the ICAgile Expert certification process, ACI will conduct a competency check to ensure your level of skill meets what’s needed to participate in the rest of the program (an additional fee of $250 applies).  Our philosophy: Competence is the product; certification is the byproduct.
  • Belong to a powerful network of professional agile coach change makers who are achieving the highest standard of competence in the industry.

Prerequisites

  • Classroom Learning. Complete The Agile Facilitator (2 day course) and Coaching Agile Teams (3 day course).  Acceptance based on completing other ICAgile-accredited facilitation or agile coaching courses on a case-by-case basis.
  • Experience. 1-2 years agile coaching experience, having been the ScrumMaster or coach of 3 or more teams, at least one of which you started up.
  • Intention. A strong desire and intention to significantly expand your agile coaching competence and confidence.
  • Intrinsic Motivation. An internal motivation to attain a significant level of professionalism in agile coaching. A drive that yields the stick-to-it-ness needed to complete the program’s rigorous requirements and achieve a significant rite of passage.

Components of the Program

The Competence Cohort is divided into two phases.

Phase one is six months long and focused on practice and skill building up to (and beyond) the level of skill needed to achieve the ICAgile Expert in Agile Coaching.

Phase two is four months long; including a 3-day residential that catapults the agile coach into the deeper skills and knowledge of transformational agile coaching and the chance to apply them to the difficult agile coaching situations we call Quests.

Competence Cohort Phases

Phase One: Competence up to the level of ICAgile Expert in Agile Coaching

Components of Phase One the program are:

  • 12 Group Coaching Calls. The program includes twelve 90-minute group coaching sessions where we will focus on a monthly theme (see below). The group calls will be held twice a month and will vary in format to include skill drills, case studies, triad coaching, and group supervisions. Prior to each call there will be required pre-work. The pre-work will be sent out a week ahead of time and may include reading, reflection, journaling, or preparation of a case study. Calls will be every other Monday 5:30 – 7:00p Eastern.
  • 4 Supervisions. The program includes 4 hours of Individual (one-on-one) Supervision, where you bring a video (or audio) showing your skills in facilitating, teaching, coaching or mentoring. The Supervisor will assess your Agile coaching against a set of open, transparent competencies and provide feedback and growth opportunities.
  • 20 Hours of Peer Coaching and Mentoring. During the program, participants must complete at least 20 hours of peer coaching and mentoring. Ideally, this will come from at least 2 colleagues/peers with whom the participant establishes an explicit coaching relationship.
  • 20 Hours of Team Coaching and Mentoring. During the program, participants must complete at least 20 hours of coaching and mentoring with individuals on a team or a whole team.
  • 24 Hours of Facilitation and Training. During the program, participants must complete at least 24 hours of facilitation and training practice. Participants should identify at least one opportunity per month to either facilitate and/or teach with a team.
  • Reading and Journaling. Developing the skills of an agile coach requires attention to your own development first. Participants will complete reading and journaling assignments designed to expand knowledge and self-awareness and help prepare for the group calls and individual supervision calls.

Group Coaching Call Topics:

  • Designing the Alliance and Program Overview
  • Team Development and Your Approach
  • Facilitation: meeting design practice
  • Facilitation: supervision example using a participant’s facilitation video
  • Facilitation: quandaries and hold-backs
  • Professional Coaching: listening and powerful questions skill drill
  • Professional Coaching: quandaries and hold-backs, supervision example using a participant’s coaching video/audio
  • Professional Coaching: arc of the coaching conversation skill drill
  • Mentoring + ICAgile Gate Preparation Q&A: expert demo, information questions vs powerful questions
  • Mentoring: arc of the mentoring conversation skill drill
  • Teaching: adult human learning and teaching about (and safely altering) the agile practices
  • Articulating your Agile Coaching Stance

Phase 2: Competence up to the level of ACI Certified Transformation Coach – Teams™ (CTC-T)

Phase Two goes beyond the foundations and deepens the skill to transformational agile coaching. Phase Two is four months in duration and includes the following components:

  • 3 Day Residential. You will attend an intense, fun and transformational three-day Residential Training with your cohort colleagues. Topics include professional coaching, human systems attunement, large group facilitation and transformation mastery.  (Held in the US. Travel expenses not included.)
    • Deep dive into more professional coaching skills such as Articulating What’s Going On, Curiosity, Intuition, Designing an Alliance, Acknowledgement, Clearing, Requesting, Accountability and, of course, more Self-Management.
    • Transformation mastery models and applications (ie Integral Agile, constellations)
    • Large group facilitation techniques and practice
    • Revealing the system (observation vs. evaluation)
  • 4 Agile Coaching Quests. After the residential, you will apply your new knowledge and sharpened skills to the more challenging situations. We call them Quests. You must complete four Quests of your choosing. The main criterion of a Quest is that it is a significant challenge and something you have never done before (and something you’re a little afraid to do). Sample Quests:
    • Coaching a manager with more organizational power than you on their role transition
    • Coaching someone with resistance
    • Facilitating a conflict conversation
    • Applying coaching skills at the team level (listening, PQs, self-mgmt, revealing the system to itself)
  • 8 Post-Residential Colleague Calls.  You will take part in bi-monthly support and accountability calls to help you integrate what you learned at the residential. ACI will provide the structure/accountability, you will be leading the calls with your colleagues!
  • 8 Professional Case Consultation Calls. A bi-monthly case consultation call will be held, post-residential, with an ACI faculty member. These calls will continue the path towards transformation and focus on a monthly ‘quest’ case that a participant brings to the call.
  • Community Contribution. Agile coaches support and grow other agile coaches. The Community Contribution allows you to apply your agile coaching knowledge skills to benefit others’ growth. It can be a new tool, a new blog post, a user group presentation, or many other things.  It just needs to be something more than you contribute today, and ideally begin charting your course as an important voice in the agile coaching world.
  • Completion Presentation. Create and deliver a Completion Presentation: of your portfolio, your unique contribution to the agile field, your “my model” for doing agile coaching work. It’s a self-evaluation. It conveys your now-evident competence and confidence in your own authentic and professional Agile Coaching Stance. Delivering this presentation results in the formal acknowledgement of your accomplishment and attainment of the CTC-T™.

To successfully complete the program, complete all program components, including:

  • 64 hours of real-life Coaching, Facilitation, Training and Mentoring.
  • 4 Agile Coaching Quests.
  • Coaching journal entries.
  • Calls. Make the commitment to yourself and your colleagues to attend group coaching calls, colleague calls and consultation calls.  If unavoidable, you may miss up to 3 of these calls during the program, but will need to make up the session by listening to the session recording and completing a make up assignment. (Note: You may only miss 1 of each type of call.)
  • 4 one-on-one supervisions.  Submit at least one video each of live facilitation and teaching sessions for supervisions. Submit at least one audio or video each of coaching and mentoring sessions for supervisions.  (or do a combined supervision of facilitation/teaching and then your 4th supervision is a “make up” in case you do not pass the first time).
  • Create and submit facilitation guides for facilitation and teaching sessions.
  • Be currently coaching at least one agile team. (Please note: you will need to show experience of coaching a total of 3 teams for the ICAgile gate, and coaching one team through a start-up.)

So after almost twelve months and two certifications later what did I learn?

  • The big one is the power of a coaching community. On this journey with other Agile Coaches who have a bond around learning and improving has been an incredible privilege.  I have watched relationships grow and empathy for learning, and my only hope is that this little group continues its relationship well past the completion of the cohort. I would like to personally thank each of my cohort colleagues for their support and friendship throughout the program
  • Doing a program like this via audio really sucks! In the beginning of the program I felt extremely isolated and whilst the facilitation of the program was all about bridging the gap, it really wasn’t until the residential and introduction of video that I truly felt part of the group. Partly this was due to the timing of the calls in Australia (often at 7am or 8am when I was either in transit of preparing for a class and partly as prior to the program I did not have any relationship with the other attendees (whereas many of the North American attendees had met each other during other ACI classes or bootcamps)
  • The fact that the cohort inspected and adapted all the way through – from tools to determining what was adding value for the group, the group certainly lived by the Agile values
  • If you are using audio, you need a virtual circle and need to announce who is speaking. The virtual circle is simple but something I now introduce to virtual teams all the time!

  •  A recap on some of the important parts of Agile Coaching and the opportunity to practice – presence, powerful questions and active listening and all three levels
  • A recap and ability to practice the coaching arc in 10 minute coaching sessions; create the environment, what’s their agenda, explore the topic, narrow down actions, commit to action. The big lesson was not to own the coachees actions, but to ask what sort of accountability they need from me
  • The importance of a designed alliance between the coach and the coachee (something I have always believed in as a coach, a concept that was introduced to me by Johanna Rothman many years ago
  • The clear differences between mentoring and coaching and an observation that you often are doing both in your conversations
  • The importance of a facilitator guide, which is something I still need to get better at moving forward (especially when I have time to prepare)
  • Holding space and making the space safe
  • Teaching design, the hero’s journey and the importance of 24 hour reviews (I have always done these but give them much more importance now)
  • Probably my main takeaway, especially after Michael convinced me it is much more useful than the simplistic Tuckman model, is the Drexler-Sibbet Team Performance Model

The residential was held outside Washington, DC in February and was 3 day immersive retreat. For me I had to cut into a European holiday to attend (flew out of Venice and back to Rome), and some standouts (apart for physically meeting my cohort colleagues) were:

  • Observing what happens when a coach or a coachee gets to their edge
  • the power of giving and, more importantly, receiving acknowledgements (“I want to acknowledge your…”)
  • resistance and how the coach needs to make the shift, not the client and the skills of articulation and making a request
  • the power of clearing when dealing with resistance
  • a better understanding of the Integral Agile Roadmap, fully understanding the “I”, “It”, “We” and “It’s” quadrants and thinking about the team as a system

  • The case consultation process and the interesting insights of observing this process directly and the role of a system scout observing the system
  • a different approach to constellations in how you can learn more about your relation and the relationships of others to the system. This one was very interesting in how you can actually feel the system, something I would not have believed until I tried it
  • the simple joy of tossing a football with friends (even if it was American football)

ICE-ACAfter completing the calls, the residential and completing my two assessments (coaching and mentoring which I was able to do live at the residential and teaching and facilitation which was done with video evidence remotely), plus a final call with ICAgile, I then obtained my ICAgile Agile Certified Expert in Agile Coaching (ICE-AC).

The final part of the program consisted of Case Consultation calls and Sapphire Colleague calls.

  • The case consultation calls consisted of an ACI faculty member leading a session using the Integral Roadmap with one of the cohort members as the coachee. The rest observed with someone taking the role of a system scout.

  • The Sapphire Colleague calls I really enjoyed as different members of the cohort brought different exercises and discussions to the cohort.

The last part of the program, in order to get the ACI Certified Teams Transformation Coach™ (CTTC) certification, was the completion of four personal quests. My quests were:

  • Confidence to speak on Agile Coaching – I delivered a coaching talk at Agile Australia 2016 (with my colleague Renee Troughton) and solo at Agile 2016 conference around Agile Coaching skills and katas
  • Move from teaching and coaching teams to more of an enterprise level – Have started doing this at a client site, through the delivery of Agile Portfolio training and now helping them make changes up to the executive management level
  • Coaching for conflict – be more aware of conflict, mine for it, and facilitate the discussion
  • Blog experiences rather than just learning – you are seeing this now and I have committed to do this more in the future
  • My community contribution was probably my desire to bring Agile back to technical mastery, so I agreed to be part of the organising committee for the Agile Alliance Technical Conference. This as well as my other contributions that include Agile Australia, reviewing for Agile 2016, co-organising Agile Brisbane and running YOW! Conference with a desire to continue building the Agile community but more importantly delivery quality solutions that make a difference

So finally, if you are an Agile Coach should you join the Cohort? The answer, absolutely – as a coach it has been a year long learning experience and one I am so glad I committed to, despite numerous times questioning whether I had the time to do the pre-work and the regular calls, The final question is what next on my coaching learning pathway.