• Issue 93 - January 23, 2017


    Art of ScrumMastering – 12 Core Skills

    Scrum Master is more than a leadership role, as they lead the team by example and are adaptive to the changing environment, like chameleons respond to changes. Becoming a great Scrum Master is a journey, and it could take years to reach to a stage of a leadership role. The sooner the ScrumMaster gets the teams self-organising, the better they can watch out for things beyond the team level. Here are 12 skills that can help you master the art of ScrumMastering.


    How to Embody Slack?

    You can’t be creative when you are overworked or overburdened. Stress kills innovation as does business. Little slack leads to little time to look around leads to little improvement. To be creative, your mind needs to feel free and unallocated, uncluttered even. What do Agile leaders (please feel free to replace manager with leader in the article) need to do? Have a look.


    Continuous Integration Certification

    Continuous Integration tools are common in most development organisations. But we all know that any decent technique needs a certification program — and fortunately one does exist. Are you ready to be certified for Continuous Integration? And how will you deal with the shocking truth that taking the test will reveal?


    Too Many Meetings in Scrum?

    Every heard things like, since the introduction of Scrum, all I do is attend meetings. I didn’t become a developer to attend meetings all day long or with Scrum I hoped we would get a team culture, but instead it feels more like a meeting culture or I thought Scrum meetings we’re time boxed, but for example our daily Scrum takes at least 30 minutes and afterwards we still don’t have a solid plan as a team. Does it really happen, though?


    How to Help People Collaborate?

    Most of us assume that if we want to change people’s behaviour, we need to change their incentives. Let’s say you want to help you team members in becoming more collaborative, but you don’t have any control over their salary and compensation. How do you transform a competitive, star-driven culture into a collaborative one when they had no power to juggle financial rewards and no influence over promotion decisions?


    Outcome Driven Innovation for PO

    Innovation is the process of producing solutions which satisfy unmet needs. Traditional innovation is ideas-led and Tony argues this is a guessing game of fail-fast, pivot-often. Here’s how  how jobs-to-be-done theory and the Outcome-Driven Innovation (ODI) process can help organisations in at becoming significantly more effective at creating customer value and creating breakthrough products and services?


    5 Common Code Smells

    Developers hate errors. Logical errors, or bugs or issues. Whatever you call them. Such errors will range from forgotten edge cases that have not been handled to logical bugs that cause entire systems to crash. But what about the more subtle issues that don’t affect the way the system works? Here are 5 common code smells that you should look out for.