• Issue 88 - November 21, 2016


    6 Types of Agile Coaches

    The term “Agile Coach” has become overloaded to mean many different things to different people. This overloading can create a lot of mismatched expectations and suffering for Hiring Managers, Agile Coaches and Agile Teams because each person may have a completely different interpretation of who an Agile Coach is. Here are 6 different types of Agile Coaches. Which type are you?


    Agile Design Prototype – Worth a 1000 User Stories

    It’s not far fetched to say that prototyping  is no longer just a nice-to-have. Once you build prototypes into your design process, you get a better feel for whether you are solving problems in the right way for your customers. It helps you align multi-disciplined team. But how do you embed this in your Agile workflow? Have a look.


    Team: Conflict and Chemistry

    How important is team chemistry? Does it matter more than the skillset of the team members. You have to look at competence for sure, but there’s an element of which you can also train some of the competence. But what if the team members don’t get along well? And there’s conflict. Too much of it. Here’s an interesting take on why team chemistry matters most.


    How Google Builds Test Infrastructure?

    Core part of the work that tester engineers do at Google is building and improving test infrastructure to make engineers more productive. That enables, cutting time to run tests from 30 mins to 3 mins sometimes, and making sure that verification tests are not flaky.  How do they do it? Have a look.


    How to Make Customer Feedback Actionable?

    How do you transform customer feedback into something you can act on as a company? How can you take a jumble of open-ended feedback and use it to inform your product roadmap? How do you get to a prioritised list of customer insights you can act upon with confidence? Read on.


    Fundamentals of Pair Programming

    Next to TDD, Pair Programming is probably one of the most controversial of XP practices. Most people who criticise Pair Programming have never done it or, if they did, don’t have too much experience with it. Where does the critique come from? Comfort zone. How do you get started? Here’s a primer.


    How to Make it Work?

    Starting something new is difficult. “We are not sure about the best way to do it”, is a common problem. When you get started, you struggle the amount of choice. The analysis paralysis. Over-thinking kills productivity. How do you avoid it? Here are a few thoughts.