Skip to main content

agile mandate

XYZ were a digital agency and over the years had done many software projects for their customers with varying degrees of success. After learning that many companies were having great success with Agile processes and noticing that even the UK government had decided to adopt those ways of working, the directors had realised the use of these new techniques would improve the performance of their own company. To that end, they had issued a mandate to the project team that by the end of the financial year, they had to have performed at least one Agile project. By this time next year, all projects needed to be Agile.

So it was that Colin, our intrepid consultant, found himself in the office of Richard ‘RJ’ Jones, head of XYZ’s Project Office. RJ had contacted Colin so he could get the training and coaching he needed for his team before they started their pilot Agile project.

“Tell me,” said Colin opening the conversation, “how big is your team?”

RJ though a bit before responding, “We have a team of about fifteen project managers, maybe twenty or so business analysts and half a dozen architects”

Colin looked at him quizzically, “but what about the engineers, the coders, and the test analysts? How many of those do you have?”

“Ah! I see your confusion,” he replied, “We don’t have any engineers of our own. We outsource all our development and testing work to best-of-breed suppliers in India. We haven’t done any of our development for years.”

He continued, “Three of the developers for this project are an outsourcer’s head office in Chennai; the other two are in a subsidiary office. Again, they’re in Chennai but they’re about forty-five minutes apart. The two-man QA team is in Mumbai but they work for a separate supplier company and, again, have their own office.” He looked at Colin, “Is not having our own engineers a problem?”

“It’s not so much that you don’t have your own team, although, admittedly, that is a problem. The bigger issue is where everybody is located,” said Colin, “Agile is based on a set of principles and one of the most important of those principles is that face-to-face communication is the most effective. You’re not going to be able to carry out face-to-face conversations with people halfway round the world.”

RJ had a frown on his forehead, “I hope this isn’t going to be a big problem. There is no way I will be able to get everybody on the same continent, never mind in the same room. I just don’t have the authority; I have no say at all in the working practices of our outsourcing partners. I was hoping you would be able to just give us some training and maybe follow that up with some coaching.”

Colin smiled at him, “It’s not quite that simple. Agile isn’t something where you can just attend a class, get a certificate and all of a sudden you become Agile. Agile demands real change.”

RJ looked worried now, “Hold it a minute, are you saying we won’t be able to do Agile at all?

“In a sense I am,” said Colin nodding seriously, “Agile is a binary thing; either you are, or you aren’t. Having said that, the intent of Agile is to uncover better ways of doing software, so why don’t we start by looking at the things we can improve by bringing in some Agile practices?”

RJ sighed with relief, “So we will be able to do some Agile then?”

Colin agreed with him, “You can do some Agile practices and you can use some Agile techniques. You won’t be Agile you’ll be what we call ‘AgileBut’ In other words; you’ll be doing what you can to be Agile but you won’t be upholding all of the principles. For example, you don’t have a co-located team.”

“I should also tell you that responsibility without authority is one of the most common recipes for stress. You have the responsibility for making your projects Agile but you don’t have the authority to make your team uphold the Agile principles. It’s a no-win situation for you and you might want to have a conversation with your boss about that.”

“I’ll do that,” said RJ, “Thanks very much for your help today, it’s really put things into perspective for me.”

Colin left, wondering how many HR complaints this current trend of issuing Agile mandates might bring.

Popular posts from this blog

The Death Knoll for the Agile Trainer

The winds of change blow fiercely, propelled by AI-driven virtual trainers, and I can't imagine for a minute that certification organisations have not already recognised the potential for a revolution in training. They may even already be preparing to embrace technology to reshape the Agile learning experience. Traditional face-to-face training and training organisations are on the verge of becoming obsolete as virtual tutors take the lead in guiding aspiring Agile practitioners through immersive digital experiences. The future of training and coaching lies in AI-driven virtual trainers and coaches. Trainers, powered by artificial intelligence engines such as ChatGPT, are set to revolutionise the learning experience. With AI-powered virtual trainers, learners can engage in immersive virtual environments, actively participate in simulations, collaborate with virtual team members, and tackle real-world scenarios. These trainers automatically analyse progress, provide instant feedback

Embracing AI - Augmented Intelligence

There is no denying that artificial intelligence (AI) has made significant strides over recent years, becoming more advanced and capable than ever before. With this progress, many have begun to wonder whether AI poses a threat to humanity, particularly our jobs, privacy, security, and overall well-being.  Some may argue that the rapid advancement of AI could lead to a dystopian world where machines rule supreme and humans become obsolete. However, it is important to remember that at its core, AI exists to serve us, not replace us. Instead of viewing AI as competition for human intelligence, we should consider it as an augmentation of our abilities.  This idea of 'Augmented Intelligence,' instead of Artificial Intelligence, highlights how powerful technology can enhance rather than impede human potential. Augmented Intelligence recognizes that humans and machines each possess their unique strengths, making them better together than apart. Humans excel in creativity, intuition, a

Integrating UI/UX Design Into Your Sprints

Integrating UI/UX design work into the Sprint and aligning it with your Scrum process can be challenging but not impossible. Here’s a few suggestions on how a Scrum Master can handle this situation : 1. Encourage close collaboration between the UI/UX designers, developers, and QA team members. Create an environment where they can work together and understand each other's perspectives. Encourage them to pair and/or mob to help bridge the gap between design and development. 2. Educate the team about the value of UI/UX design: Help the developers and QA team members understand the importance of good design and how it impacts the overall user experience. This will help them appreciate the design work and its role in creating a successful product. 3. Include design-related tasks in the Sprint: While design work may not be easily quantifiable in the same way as development tasks, you can still include design-related tasks in the Sprint backlog. These tasks could include activities