• Issue 65 - June 9, 2016

    AGILE

    The Spotify Rhythm

    How do teams at Spotify future proof their products and skills? They place bets. How do they define bets? They use a framework called DIBB – data-insight-belief-bet. How do they prioritise bets using stack-ranking based on company beliefs and north star goals? How different parts of the company visualise their own bets and align with higher level bets? Read on.

    blog.crisp.se

    Business Capability Centric Teams

    In the last issue we saw how outcome focussed teams are better than activity based teams. What if we take this one step further to business capability centric teams. A business-capability centric team is one whose work is aligned long-term to a certain area of the business. Business-capability centric teams are “think-it, build-it and run-it” teams. What are some characteristics of such team and how long do they live? Have a look.

    martinfowler.com

    Avoid These 10 Scrum Mistakes

    As they say, Scrum is simple in concept but can be difficult to do really well. Scrum is the most widely used, and arguably, the most abused Agile framework. What are some most dangerous and common Scrum mistakes? And how do you avoid them? Have a look.

    dzone.com/articles

    When Cross Cultural Communication Breaks Down

    Cross cultural teams are commons place, and we’re not talking about offshore and remote team only. A high percentage of co-located teams are very likely to be cross cultural teams. The strength of cross-cultural teams is their diversity of experience, perspective, and insight. But what are some most common scenarios when communications break down? And what can you do? Read on.

    hbr.org

    Critical Rule of Prioritisation

    One of the easiest way to improve return on investment, and reduce waste is to avoid doing low value and low impact work. But they keep coming back. Teams and Product Owners keep making this mistake. Here’s how you can avoid it.

    blog.intercom.io

    Software Development Trends

    How has software development changed during last two decades or so? What changes do we see in development practices, architecture, and how software is deployed? Here’s what 8 senior executives from 15 companies have to say about these changes.

    dzone.com/articles

    Who Should Facilitate the Retrospective?

    Can any team member (including the Scrum master) facilitate the retrospective next to their team member role? Does it depend on the maturity of the team? Should the  news teams use an independent facilitator, now and then? Or should it always be the Scrum Master? Here are a few options.

    benlinders.com

    Inquiry Method for Test Planning

    Creating a good test plan isn’t easy. A solid test plan balances principles of cost-benefit analysis and risk analysis. How to bring these two together? Here’s how teams at Google do it.

    googletesting.blogspot.com