It would be so easy if everyone at our companies just used Scrum or at least Agile. No one would lean on the team for dates and deadlines, and everyone would know that change is a good thing. It’d be one great big happy project management family. But let’s face it: an all-Agile organization isn’t always possible.
This article by Badri Srinivasan discusses the important notion of team leadership in Scrum and how the ScrumMaster should be a Servant Leader for the Scrum team. The article presents the principles of Servant Leadership. This is a philosophy and practice of leadership that is defined as “a management philosophy which implies a holistic view of the quality of people, work and community spirit. A servant leader is someone who is servant first and who contributes to the well-being of people and community.”
If Scrum provides the project management framework used in a majority of Agile projects, eXtreme Programming (XP) is the main source of technical practices for Agile software development. This book written by Alan Shalloway, Scott Bain, Ken Pugh and Amir Kolsky is focused on these technical aspects. The first part deal with the coding and testing activities and the second part discusses how to handle the software design activity with an Agile perspective.
In this article, Vaidhyanathan Radhakrishnan discusses about the value of release planning in Scrum. This is the tool to schedule timelines for a project or a product in a complex environment where the outcome of one team is required for the other teams. The article proposes an approach to produce a release plan. This approach is based on the finding primary and secondary features in the product backlog. You can then determine whether the resources are adequate and what interdependencies exist to adjust the feature layout. The article presents the advantages of a release plan and the common disadvantages of this situation, like including ongoing or generic activities spread across the timelines which dilutes the focus of the plan.
In this blog post, Gunther Verheyen discusses how he quit the “ScrumBut” expressions to move to a “ScrumAnd” status. He shares with us a nine questions test to determine if you are doing Scrum, but beyond the mere crossing the line of ‘yes/no’ doing Scrum there is a myriad of possibilities to play Scrum, but he explains that the core practices presented in the test are at the core of the Scrum framework and that doing less is not doing Scrum. He suggests to use Scrum as a framework for Continuous Improvement and look for ways to measure it.
In this article, Steve Hunton explains that, even if people expect that the shift to Agile practices includes a wholesale shift of roles,, the ScrumMaster does not play the part of the traditional project manager. He thinks that the project manager role is more filled by the product owner. The project manager is a decision maker accountable to the business for accomplishing the project objectives. The ScrumMaster is a coach and facilitator that sits between the project and the customer. He isn’t responsible for the project or managing the development team. If you have questions about the product, then you should ask it to the product owner. He concludes that if the ScrumMaster is making decisions about a product, then Scrum has not been properly implemented and there’s going to be confusion and conflict about who does and owns what.
The early agile literature was adamant about two things: stick with small teams and put everyone in one room. However, in the years since the Agile Manifesto, the increasing popularity of agile and the dramatic improvements it brings has pushed it onto larger and larger projects. Additionally, having an entire team, especially on a large project, in one room, or even one building is a luxury no longer enjoyed by many projects.