“Let’s migrate to Agile!” we said. Step one: Learn about scrum. Wrong! let’s learn about Agile!
When we talk about “Agilizing” anything, I think about mindset transformation. If we start thinking about tools and processes adoption, we skip two steps from the begining. Would it work? Perhaps, but at some point we would have to take care of mindset or we will continue thinking (and acting) in plain work lifecycle mode, no matter the meetings naming, or the profile titles, or the tools we config.
If you already started your Agilizing this way, don’t worry, just add some sessions to integrate mindset discussions. Be agile! fail fast learn faster! Ask your team what they think about this change, its benefits and challenges. Adjust! The feedback you get will certainly guide you towards the topics you need to follow up closely, in terms of mindset and any other.
The reason why I encourage people to start with overalls and mindset, is because then you let them to decide what agile framework best suits to their current project situation. If so, because in some cases, there is no need to put a name on this new work “strategy”.
By leaving a blank space in the name of the improvement innitiative, we let everyone feel free to share ideas. Listening their complaints while collaborating with solutions will provoke a stronger sense of commitment. That is what Agile frameworks have in common, they are not a static procedure set in stone but a flexible draft for processes and agreements that fits as a tailored suit to each team.
As a coach, you must identify the framework that best suits the team and confidently recommend its best practices to align with their brainstorming. Ultimately, the adoption of any agile framework should feel organic rather than forced.
Once you have your team’s attitude focused, convinced, and committed to their idea, you can assertively share the framework principles that will boost our quality and productivity. This way, we can avoid uncertainties, fear, and resistance to change and move forward effectively.
The adjustment and customization flows naturally whether they fit more in a kanban or a scrum frame (or any other), because the mindset is clear and agile mindset embrace continuous adaptations to boost improvements. If we first start by jumping into an initial framework, let’s say scrum, and then attempt to switch to kanban, XP, or any other, it will result in ‘another’ change to question, adopt, and accept (or not), even if we are still under Agile umbrella.
It is not about Scrum, it is not about Kanban, or FDD, or XP, or whatever, it is about Agile, and agile is, step one: a mindset.
Do you want to know more about habits?/ ¿Quieres saber más sobre hábitos?
| Build powerful habits that drive your professional and personal growth. | Identifica la raíz detrás de esas emociones conflictivas, redirecciona toda esa frustración con acciones más conscientes. Llibera tu potencial! Identify the root cause of those conflicting emotions, and redirect all that frustration with more conscious actions. Unleash your potential! | Construye hábitos potentes que impulsen tu crecimiento profesional y personal. |
Agile & Productivity Strategies 
Leave a comment