• Issue 74 - August 11, 2016


    How to build a Kickass Agile Team?

    Nothing is more rewarding than sharing the adventure of building something that truly matters with engaged team-mates. Most agile teams possess all the required skills, but sometimes it’s necessary to call on specialists for specific work. So how do you know whether your team is on the path to greatness? Read on.


    How to Avoid Two Teams in a Team

    You’re refining your backlog. During the session the entire team does not participate equally to offer up their points. UI developers participate on UI stories and are reluctant to chime in on backend work, and vice-versa. They’ve behaving like two teams in a team. They must work as one team. How do you do that?


    Looking for Team Growth? Try Mob Programming

    An entire team of up to eight people and only one keyboard. Solving one problem. That’s mob programming. It sounds  both exciting and a little too far out of our comfort zone for us to be ready to try it out instantly. Right?  Your team probably won’t mob all day, every day, but it’s a powerful way to explore new techniques and grow. Here’s how you can get started.


    How to Use Definition of Ready Correctly?

    Definition of Ready is like a big, burly bouncer standing at the door of the iteration. Just as a bouncer at a nightclub only lets certain people in —our Definition-of-Ready bouncer only allows certain user stories to enter the sprint. But it does have some potential downsides. It can lead to phases and gates. Here’s how to use the definition of ready correctly.


    5 Reasons You’re Getting to Done

    If you are not able to get to a done increment at the end of your sprint, you don’t have transparency over progress and quality.  You are not validating assumptions and learning. This is so important that people now use many terms to describe this.  Working.  Releasable.  Done.  Done done. But why are you not getting Done?


    How to Keep Your Customers Infatuated?

    You shouldn’t merely focus on providing your customers with a satisfying experience. Rather, you should aim to deliver them a string of experiences that keep them perpetually infatuated. Here are a few ideas.


    Avoiding Confirmation Bias in Testing

    When you meet a new person you immediately judge him or her based on stereotypes, what type of clothes the other person wears, his/her posture, etcetera. This happens so quickly that you cannot stop it. Same applies when we test systems. Our confirmation biases kick in. How to make sure we don’t fall into this trap? Read on.