• Issue 6 - April 3, 2015


    Is This Time for Scrum to Die?

    Giles Bowkett says it’s time for Scrum to die. He has some concerns to say the least. Ron Jeffries looks into the case put forward by Giles, and provides a powerful counter narrative. A must read.


    Can Chaos be More Productive?

    Would removing traffic signs make traffic flow more smoothly? Sounds counter intuitive, right? Some European cities are actually looking into removing traffic signs to improve traffic flow. There’s some evidence that this lead to more self organisation and better traffic flow. Can chaos be more productive? Risk creates engagement, and engagement leads to better decisions. Kevin Meyer thinks aloud in this article.



    How Much Should the Managers Really Know?

    Do you need to know the work you team members do to become a good manager? If the answer is yes, how much should you know? Do you need to be an expert, or just know enough to understand the work and related issues? A tough question, that has arguments for and against. Here’s one perspective.


    HOW TO

    Remember these 5 Open Spaces Principles?

    Open spaces allow participants to discuss things that matter to them. As long as they remain exactly that – open spaces. Here are five quick tips to help you keep it simple, open and yet very effective.


    3 Things to Consider Before Release

    Releases are not about the software only. You need to consider other factors that come into play to ensure that your release achieves the intended business goals. What other factors should you consider while planning for your releases? It sounds like a cliche, but think end-to-end. How to engage with marketing and sales? Do you know how to get your customers to help you in making your release a success?



    How to Get Rid of Technical Debt?

    For most projects that’ve been running for a while, technical debt is a dark reality. Most teams tend to accumulate technical debt.Even if they’ve been using mostly Scrum based approach,  Why is so? Scrum is a framework, kept light weight on purpose. It doesn’t prescribe many practices, rather encourages team to adopt any practices it finds suitable based on inspection and adaptation. If teams are not careful, and don’t adopt careful practices on top of Scrum, they tend to accumulate technical debt. How can you get rid of technical debt, or better avoid having technical debt? Here are some ideas.



    Don’t Use These Excuses for Not Testing

    Rather, you shouldn’t any excuses for not testing. Why do most teams suck at testing? Team members seems to be very creative when coming up with “reasons” they are not testing or not testing enough. Most if not all of these stem from misunderstanding and lethargy. Here are a few tips to help you overcome common excuses and blind spots.



    What’s the Ultimate Goal of Devops?

    Do you achieve devops nirvana after a while and live happily ever after? Is it more like a continuous improvement journey? Or does it end once you’re able to achieve continuous delivery and once you’ve automated your release delivery to the nth level? Lot of questions. Here are the answers.



    Does Scrum Turn Active Developers to Passive Developers?

    Does Scrum turn active developers, who are always looking to find the best solution possible, into passive developers? Does it let them get away with minimum effort possible, so that they can just finish the damn thing and move on to the next shiny thing?