Do teams truly grasp the power of applying Scrum professionally? This is a challenging and somewhat contentious question. In my experience, many teams I’ve encountered operate more like amateurs than professionals. This isn’t necessarily their fault; it’s often a reflection of the expectations set by their organisations. Too frequently, companies don’t demand professionalism; instead, they push for speed and output, which leads us, as software engineers, to adopt shortcuts that prioritise the easy, fast, and cheap over the right way of doing things. This environment fosters unprofessional behaviour and ultimately undermines the potential of Scrum.
Understanding Professional Behaviour
Most teams lack a clear understanding of what professional behaviour looks like. I recall an enlightening experience with an organisation a few years back. We conducted an exercise aimed at defining what requirements should look like for the engineering team. This wasn’t about the engineers themselves; it involved the product management group.
We gathered everyone in a room, broke them into cross-functional groups, and tasked them with dissecting a user interface from their product. They were to outline the requirements they would have liked to have had, with the benefit of hindsight. The results were eye-opening. They crafted detailed requirements, highlighting the myriad questions they had and the information they lacked. The realisation hit them: “Holy moly, that’s a lot of stuff.”
Then came the second part of the exercise. We asked them to take something from their backlog that hadn’t been built yet and apply the same level of detail. Just as they were getting into it, the head of product management halted the workshop. He candidly admitted that his team wasn’t equipped to create or work with such detailed requirements. This moment of realisation was profound; it illustrated the gap between the professionalism we aspired to and the current capabilities of the product management team.
The Role of Scrum in Professionalism
This scenario is not unique; it reflects a broader issue within many organisations. One of Scrum’s core purposes is to foster transparency. A fundamental expectation for any software team is to deliver a usable, working product at the end of each iteration, including the very first one. This product should be production-ready, this is the minimum standard for Scrum. If your team isn’t achieving this, then you’re not truly practising Scrum; you’re missing the level of transparency required for a professional Scrum team.
Many teams come to a stark realisation: “We’re so far away from that.” This can be a tough pill to swallow. As teams strive to meet this standard, they often uncover gaps in their processes. For instance, they might find themselves reliant on a third-party testing team, which complicates their ability to ensure production readiness. I remember a time at Merrill Lynch when we submitted our websites for third-party penetration testing. We had no insight into the tools they used, and the process cost us a hefty sum. The result? Our product was not ready for deployment because we lacked understanding of the testing tools and processes involved.
Embracing a Professional Work Ethic
The true power of applying Scrum professionally lies in cultivating a professional work ethic. This means creating products that deliver real value to our customers, products they can use and appreciate. Many teams only begin to understand this concept as they embark on their Scrum journey. They start to recognise their knowledge gaps and gradually build the capabilities necessary to evolve into professional teams.
In conclusion, the journey to professionalism in Scrum is not an easy one, but it is essential. It requires a commitment to transparency, collaboration, and a willingness to confront the uncomfortable truths about our current practices. If you’re interested in discussing this further or exploring other topics related to Agile, Scrum, or DevOps, I invite you to book a coffee chat with me through Naked Agility. Let’s work together to elevate our understanding and application of Scrum to truly professional levels.