• Issue 89 - November 28, 2016


    A/B Testing for Effective Decision Making

    What should we do (build and release) next? How should we go about building it (design and development)? How much of a feature should we build? Most crucially, how should we make these decisions? Should we try to reach consensus? Does that mean we’ll end up with a good decision? Not necessarily. So what should we do then? Have a look how key product decision are made at King.


    Should Product Owners be Servant Leaders?

    Servant-leadership encourages us to reflect on our motivation to be product leaders. Why do we want to lead others? Is it to gain power, status, success, or money? Is it to succeed together and help the people we lead grow and develop? Should Product Owners be the servant leaders?


    How Domino’s Reinvented Itself?

    How organisations and leaders can do extraordinary things, even if they operate in pretty ordinary fields. You don’t have to be a programmer in Silicon Valley or a gene splicer in biotech to unleash exciting innovations and create huge value. How about a pizza chain? How can transform itself from a legacy company into a technology-enabled, nimble, category-disrupting machine? Have a look.


    How to Make Retrospective Actions Stick?

    What makes change stick? Malcolm Gladwell talks about the tipping point, and the stickiness factor. You need people with a diverse set of social gifts, connectors, mavens and salesman as Malcom calls them, to have lasting change. What can we do to make Retrospective decision stick? Here’s an option.


    Iterations and Increments

    Agile is iterative and incremental development and frequent delivery with cultural change for transparency. What do the words iterative and incremental mean? Here’s a good explanation.


    Why Use Story Points?

    Why should we bother using story points, when we know how to use time based estimation already? Estimating in man hours is one of the most widespread approaches for estimating the amount of work in a team. What are the benefits of using story points then? Here are three key benefits.


    How to Write Clean Code?

    The process of writing good programs that are easily readable and understandable and that facilitate ease in maintenance is what we call writing clean Code. What are some good practices? Here’s a good primer on the foundation of Clean Code, a few very practical rules of thumb.