If the development of open source Scrum tools was in vogue some years ago, a lot of these projects have now been abandoned. Some are still active, but this is because their development is sponsored by a commercial hosted option. There is however an alternative to manage your Agile software development projects if you have a low budget… and a small team. Some providers of commercial Scrum tools provide a free version of their software, often with some limitations.
Even if for some Agile and Scrum practitioners, checklists can have the bad reputations as being on the wrong side of the “Individuals and interactions over processes and tool ” Agile Manifesto preferred values, it doesn’t always mean that it contains “items you should always check”. They can be also considered as a good practice that allows to capitalize and share experience when they are used as guidelines to assess the different aspects of a situation.
The two presenters explore the misunderstandings and usages of Scrum roles using examples of what they have seen in organizations. They witnessed these dysfunctions not only in companies who are new to these roles, but also in organizations that were already applying Scrum for a while.
The ScrumMaster role is certainly the most original addition of Scrum to the concept of software development teams. How and how much the ScrumMaster should be involved with the teams is a topic for debates in the Agile community. Isn’t the Scrum team supposed to be self-organized in the first place? In this article, Zuzi Šochová, author of The Great ScrumMaster, shares her opinion on some of the common mistakes made by ScrumMasters.
Many people, even the people supposedly using Agile, have too much work to do. You have project work. You have support work, formal for customer support or sales, and informal for your colleagues. You have reports to write or file, time cards to fill out, or other periodic events. You know your multitasking is slowing down your work, making you crazy, and making it difficult to deliver your best work. You need a way to say no to more work.
Scrum.org and Age of Product have released recently the 2019 Scrum Master Trends Report. This report is a follow-up to the 2017 Scrum Master Salary Report. The 2019 Scrum Master Trends Report is based on a 2018 survey of more than 2100 participants, with a focus on trends useful to both new and experienced Scrum Masters. The survey results reveal salary trends and agile adoption patterns, while also exploring gender equality within the Scrum Master role.
Agile approaches are used to generate quicker feedback that supports continuous improvement. Giving proper feedback is important between Scrum team members or with other project stakeholders. This is however hard and this article provides some hints on how to make it easier.