Tag Archives: Agile Coach

08.18.25
by

Scaling Collaborative Learning: Harnessing the Power of InnerSource for Courses with 250+ Students

After sharing a short article titled “Unlocking Innovation with InnerSource: Why Organisations Should Embrace” and a paper I co-authored that was presented at the HICSS conference titled “Agile and InnerSource: A Match made in Heaven and in Hell!“, my friend Nuno Seixas challenged me to share my thoughts on scaling collaborative learning with InnerSource in courses with over 250 students. I gladly accepted this challenge, and here are my insights.

Additionally, before starting, I would like to thank my colleagues Clare Dillon and Daniel Izquierdo Cortázar for their helpful review and feedback.

Scaling collaborative learning in large educational environments presents unique challenges, especially in courses with many students [1]. The InnerSource practices, inspired by open-source software methods, offer an effective strategy to address these challenges. InnerSource applies open-source principles such as transparent collaboration, shared development, and community engagement within an organisation or closed group. Based on my discussions with several professors and students, this approach is already being partially implemented in specific courses, such as Software Engineering, with promising outcomes.

In the current social media-driven world, there are noticeable gaps in communication and teamwork skills among students [2]. InnerSource can significantly narrow this gap by fostering a collaborative learning environment where students develop their soft skills, particularly in communication, teamwork, and problem-solving. These skills are highly valuable and essential for successful integration into professional organisational environments [3].

InnerSource versus Open-Source: Which is suitable for Education?

A key question when discussing InnerSource in education is: Why not opt for open source instead? Many educational initiatives encourage students to work on real-world projects, making their contributions visible to recruiters and aligning with open research and open science trends. While InnerSource and open source share benefits such as collaboration, transparency, and practical experience, there are situations where InnerSource (initially closed) proves to be more appropriate in educational settings.

  • Project Completion and Later Open-Sourcing: Some projects require a closed environment initially, before opening up once they reach maturity.
  • Private Practice Environment: Students may prefer a closed setting to experiment without exposing early-stage experiments or mistakes publicly.
  • Research Contexts: Proprietary or confidential research projects require controlled internal collaboration spaces.

These scenarios demonstrate that InnerSource serves as a safe, structured first step before transitioning students to open-source workflows.

How InnerSource Works in Education

InnerSource in educational settings involves creating shared repositories for larger, common projects accessible across all course disciplines and student groups. These repositories centralise materials such as documentation, code, assignments, and student projects, promoting transparency and collaboration. Students from various academic years are encouraged to participate by submitting pull requests, refining peers’ code, and engaging constructively in peer reviews. Professors and teaching assistants supervise this collaborative workflow, ensuring high standards of quality and consistency while helping students develop essential technical skills and critical soft skills needed for modern workplaces. Expanding this model further, courses could integrate InnerSource practices into a broader, unified educational framework, imagining the entire degree as one interconnected “mega-project”. Each course would contribute distinctly defined components, collectively forming a holistic, collaborative learning experience. Although ambitious, such integration could significantly improve interdisciplinary collaboration and student motivation [4].

Benefits of Adopting InnerSource in Large Courses

InnerSource offers several significant advantages for collaborative learning in large educational environments:

  • Increased Student Engagement and Participation: Students are more likely to engage with course material when they work on real-world projects. The collaborative structure of InnerSource mirrors professional environments, fostering intrinsic motivation and investment in the learning process [5].
  • Realistic Simulation of Industry Workflows: By adopting InnerSource practices, students follow processes similar to those used in real software development, such as shared repositories, code reviews, and issue tracking. This realistic simulation helps them become familiar with industry-standard tools and workflows, better preparing them for professional environments after graduation.
  • Improved Motivation and Accountability: InnerSource introduces structured mechanisms for recognition (e.g., contribution histories, visible pull requests, and peer feedback), which can boost motivation. Knowing that their work is visible to peers creates a natural sense of accountability and encourages students to produce higher-quality contributions.
  • Development of Soft Skills: Working within InnerSource practices helps students enhance key soft skills such as communication, collaboration, and problem-solving abilities that are invaluable in modern workplace settings and often overlooked in traditional academic courses.
  • Iterative Feedback: Peer reviews and continuous feedback loops allow students to refine their work over time. This not only enhances technical skills but also improves their ability to give and receive constructive feedback, which is an essential professional competency.
  • Enhanced Transparency and Consistency: A shared repository increases transparency and ensures consistency in course content, assignments, and evaluations. Everyone works from a common source of truth. That said, it’s essential to recognise that some students and professors may still prefer to keep detailed evaluations or grading discussions private.
  • Reduced Workload for Professors and Teaching Assistants: As students begin to mentor and support one another, the overall burden on faculty diminishes. While this model may require some upfront planning and setup, it can significantly ease the workload in the long run by leveraging structured peer mentoring.

Structured Approach to Implementation

Given the scale of implementing InnerSource in large courses, a step-by-step approach is essential. Breaking it down into manageable phases allows for smoother adoption and effective scaling.

Phase 1: Training and Onboarding

  • Provide initial training sessions for students, professors, teaching assistants, and mentors (senior students) on the tools used for collaboration (GitHub, Slack, SonarQube, among others).
  • Set up shared repositories for course projects and assignments.

Benefit: This initial phase equips all participants with the tools and knowledge needed to start working collaboratively.

Phase 2: Small-Scale Collaborative Projects

  • Introduce smaller collaborative projects where students work together in teams. Begin integrating peer review and feedback loops.

Benefit: This offers a low-pressure introduction to collaboration, helping students build confidence and familiarity with the process.

Phase 3: Peer Mentoring and Iterative Reviews

  • Develop a system for peer mentoring, where students give feedback on each other’s work, using a structured peer review process.

Benefit: Peer mentoring helps lessen the workload for professors and teaching assistants while enhancing students’ communication and review skills.

Phase 4: Larger, Cross-Disciplinary Projects

  • Scale up to larger projects that span multiple courses, encouraging interdisciplinary collaboration. This step mimics the complexity of real-world projects, where different teams work on various components.

Benefit: Students gain experience in complex, interdisciplinary teamwork, reflecting industry-level project structures.

Phase 5: Evaluation and Recognition Systems

  • Create automated systems to track and assess individual contributions to the project (e.g., GitHub analytics, automated code reviews). Implement a structured recognition system for students who contribute significantly.

Benefit: This phase boosts motivation and accountability by clearly recognising individual efforts while ensuring fair, data-driven assessments.

Addressing Main Challenges

While the benefits of InnerSource are clear, several challenges must be addressed for successful implementation in academic settings:

Time and Workload for Professors and Teaching Assistants

  • Challenge: Implementing InnerSource demands significant time from instructors and TAS, especially when evaluating individual contributions across large, shared repositories.
  • Action: Automate parts of the assessment process using analytics tools like GitHub Insights or SonarQube, which can track contributions and support data-driven evaluation of student work. Structured onboarding and gradual adoption of InnerSource practices can help reduce workload.

Resistance to Collaborative Workflows

  • Challenge: Students may be reluctant to adopt collaborative workflows, particularly if unfamiliar with peer review or open contribution models.
  • Action: Provide clear guidelines, initial training sessions, and continuous support to help students transition to collaborative work. Regular development sprints, iterative submissions, and ongoing feedback can boost acceptance and foster a culture of open collaboration.

Managing Tool Access and Security

  • Challenge: Managing access to tools (e.g., GitHub, Slack) becomes more complex in large courses, especially when students need access to specific projects or repositories.
  • Action: Use integrated platforms that simplify access management and align permissions with project roles. Assign mentors to oversee project flow, ensure security, and help students use the tools effectively.

Maintaining Consistency and Quality

  • Challenge: Ensuring consistent code quality across contributions can be challenging when multiple students work on the same repository.
  • Action: Set clear coding standards and employ automated tools like SonarQube to maintain quality. Routine peer and instructor reviews reinforce best practices and encourage meaningful participation.

Fair Assessment of Individual Contributions

  • Challenge: Accurately evaluating each student’s input within collaborative projects is a common issue.
  • Action: Use clear metrics and regular assessment checkpoints supported by analytics from version control systems and peer reviews. Implement recognition systems to reward significant contributions, effective code reviews, or valuable suggestions.

InnerSource can replicate real-world development environments in academic courses. Students may work in specialised teams (e.g., backend, frontend, testing, among others) and collaborate to integrate their work into a larger product. Submitting and resolving issues, maintaining documentation, and participating in regular sprint cycles develop technical communication skills, promote proactive behaviour, and improve team dynamics. A structured recognition system for high-quality contributions further enhances engagement and motivation.

My Thoughts on the Future of Education

The future of education is collaborative, interdisciplinary, and closely connected to real-world challenges through strong industry partnerships. To prepare students for a swiftly changing world, institutions need to go beyond traditional lectures and encourage interactive, digitally integrated learning environments. Professors and teaching assistants will become mentors and facilitators, helping students develop critical thinking, creativity, and adaptable problem-solving skills while fostering genuine teamwork. Students, in turn, must adopt self-directed exploration, collaboration, and ongoing learning as essential 21st-century skills.

One practical approach to this transformation is implementing InnerSource practices, inspired by open-source software development. By working on shared projects, whether within a single course or strategically across multiple courses, students gain not only technical knowledge but also critical soft skills such as communication, coordination, and peer review. InnerSource offers a structured, safe environment for collaborative learning, which can later expand into open-source participation, allowing students to engage with global communities, showcase their work, and build professional portfolios.

Scaling these initiatives, especially in large courses, requires careful planning, clear guidelines, effective communication, and collaborative tools to monitor progress and ensure quality. Pilot programmes or integration with existing innovation projects can quickly demonstrate value without overwhelming participants.

As AI, remote collaboration, and rapid technological change continue to reshape how we work and learn, adopting innovative educational models like InnerSource is no longer optional; it is essential. A collaborative mindset is not just a bonus; it is a fundamental competency for the modern workforce. By adopting and integrating methods beyond Agile, such as InnerSource, institutions can expand collaborative learning, develop industry-relevant skills, and better prepare students to succeed in interconnected, agile, and dynamic environments. Now is the moment to lead this change, empowering students, professors, teaching assistants, and institutions to co-create the future of learning and work.

References:

[1] P. Dillenbourg, Collaborative Learning: Cognitive and Computational Approaches. Elsevier Science Ltd, 1999.

[2] OECD, Skills for Social Progress: The Power of Social and Emotional Skills. OECD Publishing, 2020.

[3] World Economic Forum, The Future of Jobs Report 2020. World Economic Forum, 2020.

[4] D. W. Johnson and R. T. Johnson, “An educational psychology success story: Social interdependence theory and cooperative learning,” Educational Researcher, vol. 38, no. 5, pp. 365-379, 2009.

[5] M. Prince, “Does active learning work? A review of the research,” Journal of Engineering Education, vol. 93, no. 3, pp. 223-231, 2004.

11.15.24
by

Thought of the Day: SpaceX’s Journey – Transforming Agile Claims into Real-World Success

🚀 4 years ago vs today! Let’s see what agility truly looks like in action. 💥

Lately, I’ve heard plenty of claims that “Agile is dead” or that it “failed.” 🙄 But maybe it’s time to rethink what agility can deliver when applied correctly—even in safety-critical fields.

Image from an unknown source.

If you think agility is past its prime, take a look at what SpaceX has achieved in just 4 years. 🛠️ It’s not that Agile is dead—it’s just that you might not be using it right. 😉

10.21.24
by

Unlocking Innovation with InnerSource: Why Organisations Should Embrace

Organisations increasingly turn to InnerSource to transform their software development processes and boost collaboration in today’s fast-paced, innovation-driven world. However, what exactly is InnerSource, and why is it gaining traction?

What Is InnerSource?

InnerSource refers to the practice of applying open-source software development principles within an organisation. It means creating an internal environment where teams across the company can contribute to software projects, regardless of their direct responsibilities or departmental affiliations. This model encourages collaboration, knowledge sharing, and dynamic problem-solving, much like public open-source communities, but internal.

InnerSource Value

The value of InnerSource lies in its ability to break down silos and foster a culture of transparency, creativity, and collaboration. Key benefits include:

  • Accelerated Innovation: Teams can tap into a broader talent pool within the organisation, driving faster development and more creative solutions.
  • Improved Code Quality: Cross-team contributions lead to more eyes on the code, which can uncover bugs and improve overall quality.
  • Talent Development: Developers gain exposure to a variety of projects, enhancing their skills and broadening their expertise.
  • Increased Agility: Teams and organisations can quickly adopt and iterate on internal solutions, reducing dependency on external vendors or slower traditional processes and increase delivered value.

My InnerSource Journey

My journey with InnerSource intensified this year (2024) during an international conference in Italy, where I had the pleasure of meeting some incredible and skilled professionals, including Clare Dillon and other thought leaders in the field.

Our discussions, idea exchange, and brainstorming sessions sparked exciting new perspectives and a strengthened understanding of InnerSource’s transformative potential. These conversations culminated in a research paper, which has been accepted for publication and paved the way for ongoing collaborations, further pushing the boundaries of innovation.

InnerSource Challenges

While InnerSource offers significant advantages, adopting it can pose challenges, particularly for organisations highly regulated and accustomed to traditional hierarchical structures:

  • Cultural Resistance: Teams that are used to working in isolation or maintaining proprietary control over their code may resist shifting to an open collaboration model.
  • Governance Issues: Without clear guidelines, InnerSource can lead to conflicting coding practices or duplicated efforts across teams.
  • Maintaining Consistency: Ensuring code standards and compatibility across contributions from various teams requires additional coordination.
  • Regulatory and Compliance Challenges: In highly regulated environments, such as safety-critical domains (e.g., healthcare, aerospace, and finance), ensuring compliance with industry standards and regulations can be complex. InnerSource must adhere to strict controls to prevent breaches of regulatory frameworks, which can add layers of governance and oversight.

Why and How Should We Adopt InnerSource?

To overcome these challenges and maximise the value of InnerSource, organisations should consider:

  • Leadership Buy-In: Organisational leaders must champion the value of InnerSource, promoting a culture of openness and trust.
  • Clear Governance: Establish well-defined contribution guidelines, code review processes, and ownership responsibilities.
  • Training and Onboarding: Ensure developers are well-equipped to participate in this new collaborative environment through training and regular engagement.
  • Supporting Tooling: Organisations should also invest in the right tools to support InnerSource initiatives. This includes platforms to track InnerSource projects, make them discoverable across the organisation, and facilitate contributions. Proper tooling is essential for managing contributions, ensuring code quality, and enabling easy collaboration across teams.

Looking Ahead to 2025

As organisations look for innovative ways to start the new year strong, InnerSource should be a key consideration. To further support this transition, I’m excited to share that a research paper on InnerSource, developed in collaboration with international researchers, will be presented at an international conference and published in Q1 2025. This research will provide deeper insights into the value, challenges, and best practices of InnerSource adoption. Stay tuned for more details soon!

10.04.24
by

Reflecting on AI and the Future of Work : Agile Thinking Matters

Lately, I’ve noticed a recurring theme in my conversations with friends, colleagues, and even organizations: the impact of AI on our jobs. It’s a question that keeps coming up: Should we be worried about AI taking over our jobs and careers?

Recently, during my experience at the XP 2024 Conference in Bolzano, where I presented one of my research papers (which, interestingly, wasn’t related to AI), I found myself in a very cool library-coworking space at Bolzano University. There, I came across two striking images that sparked thoughtful reflection.

The first image humorously depicts a robot teaching a younger robot about the original processor—a human brain. It made me think about how, just like the brain, AI is an incredible tool that can enhance our abilities rather than replace them.

The second image from the MIT Technology Review showcases a future where robots are integrated into our daily lives, helping us with everything from childcare to play. While AI may assist in many aspects of our lives, it’s essential to recognize that human interaction is critical for children’s growth in childcare. AI will take many years to approach the nuanced understanding and emotional support a human caregiver provides. Regarding play, I still remember my first archaic Tetris machine, a reminder that even before AI, machines have always played a role in our lives, often enhancing our play experiences rather than replacing the human touch.

One important point to note is that “AI” is a term that is often too vague. Perhaps we should start narrowing it down to facilitate discussions on how it can genuinely help us. Generative AI and Large Language models (LLMs) essentially identify patterns in language statistically without truly understanding the words they process, which, in some cases, is quite useful.

Additionally, the issue of accountability regarding these tools remains a significant concern. However, I won’t delve into that here, as it is a complex topic deserving of its own focused discussions in the future.

Here’s my take on it, I don’t believe AI is here to “steal” our jobs and careers. Like the Industrial Revolution before it, AI will undoubtedly bring changes. Some jobs may become obsolete, while new opportunities will emerge. Predicting exactly which jobs will be affected is tricky—I don’t have a crystal ball; if I did, I’d be playing the lottery!

I foresee AI enhancing our capabilities, allowing us and organizations to focus on tasks that require critical thinking, creativity, human interaction, craftsmanship, and more—areas where human touch and ingenuity are indispensable. AI isn’t just a replacement; it’s a knowledge multiplier, providing us with faster analyses, more information, and data to support innovative ideas and decisions.

However, it’s crucial not to blindly trust AI—at least not yet. We must review its outcomes to ensure accuracy and relevance. The future isn’t about humans versus machines; it’s about how we can collaborate effectively with AI to unlock new potential.

As we navigate this evolving landscape, embracing and maintaining Agile thinking is essential. We must keep cultivating a mindset of continuous inspection and adaptation to remain relevant in our fields. This approach will allow us to evolve alongside technological advancements, ensuring we leverage AI’s potential while staying true to our unique human skills and creativity.

Let’s embrace this journey with curiosity and readiness to adapt. Together, we can utilize AI’s potential to create a future where human creativity and technological advancement coexist.

07.29.24
by

Thought of the day: “The journey of a thousand miles begins with one step.” – Lao Tzu.

It’s easy to feel overwhelmed by the scale and complexity of our daily challenges. Whether we are working on routine tasks, pursuing professional or personal goals, or tackling complex problems, the initial step is crucial.

We often become paralyzed by what can lie ahead, forgetting that meaningful progress starts with a single small action. Remember, the key is to start. No matter how daunting the task may seem, taking that first step sets the momentum in motion.

This principle also applies to any organizational change. Implementing change within an organization can seem overwhelming due to its complexity and potential resistance. However, initiating small, manageable actions can create a ripple effect that drives larger transformations. Each small step taken collectively by individuals contributes to the overall progress and success of the organization. We build the momentum needed to achieve significant and lasting change by starting with one step.

So today, let’s focus on making that first move towards our goals. Each subsequent step will bring us closer to success.

02.10.24
by

Thought of the day: Embrace Imperfection and Pursue Excellence

Recently, while reading Adam Grant’s enlightening book, “Hidden Potential,” I stumbled upon the term “wabi-sabi” (侘び寂び), which encapsulates the beauty found in imperfection, impermanence, and incompleteness.
 
Reflecting on this, I have realised the importance of setting challenging rather than perfect goals. In an Agility mindset, adapting and evolving based on constant feedback is crucial. By not striving for perfection, we open ourselves to rapid learning and growth, taking more risks and embracing imperfections.
 
In a fast-paced world of constant change, individuals and organisations must keep this mindset at the forefront. Instead of aiming for flawless solutions, let us focus on crafting workable ones with unwavering quality. Pursuing perfection can be a trap, hindering our progress by fostering a false sense of completion and stagnation.
 
Embracing imperfection fuels our journey toward excellence. Let’s remember that perfection is not the destination but a continuous learning and growth process.

07.30.20
by

Business Transformation Trinity

I was reading the article “Digital Transformation Success Depends on Agile Approach to Change” by Peter Bendor-Samuel, where the author says that companies are rushing to apply digital transformation to gain competitive advantage. Furthermore, driving the digital transformation often requires changing the company’s operating model through multiple iterative steps known as journeys. Peter Bendor-Samuel explains the benefits of using an agile approach and how this can support companies to move forward with the digital transformation. The author also states that corporate culture is the key element missing that make an organisation struggle to support the agile environment while driving their digital transformation. These ideas were so interesting that made me think deeply about the importance and strength of the relationship between digital transformation, agile and culture.

Due to its content, I decided to share it together with my thoughts on the topic. Surprisingly, as soon as I started to write my input, I realised I started writing this article. I hope you enjoy reading it the same way I enjoyed writing it. As always, it would be great to hear your thoughts on this subject.

Nowadays, companies already realised that in order to achieve a successful agile transformation, they should not limit this change to engineering departments but all business departments, including HR, finance, sales, marketing, customer support, among all others. More and more, we observe that digital transformation is becoming the new trend, leaving many people talking about this topic alongside agile transformations while companies try to achieve both. Clint Boulton states in his article “What is digital transformation? A necessary disruption” published in CIO.com that digital transformation is a basal change for how organisations deliver value to their customers. In other words, we can say that digital transformation is a revolutionary rethinking of how organisations use technology, reorganise people and processes to challenge and improve their current status quo.

Taking into consideration Peter Bendor-Samuel and Clint Boulton thoughts, we realise that agile and digital transformation are not the same. Agile focuses on how organisations deliver value iteratively to the customer while digital transformation focuses on how organisations use technology to support how value is delivered. Still, one supports the other to achieve the same goal that is delivering value. However, both authors agree that culture is so crucial that its core to achieve a successful transformation. The reason I say this is because, in traditional organisations, executives and managers are given targets that they are held accountable for, and which they cannot fail. I genuinely believe that to succeed with any transformation following the agile approach experimentation must be allowed so we can absorb the learnings from the failures and keep going forward.

During my career, agile transformation and digital transformation initiatives were driven separately, or their touchpoint was high-level. However, people started to realise that the relation between these two transformations is more substantial than initially thought — one cannot work correctly without the other. In his article Peter Bendor-Samuel Bendor-Samuel, states that companies use an agile approach to minimise risks and validate if their efforts meet the desired outcome as they move forward in their journey. Furthermore, the authors say that the key element for any digital transformation supported by an agile approach is the corporate culture. Many times, at the heart of the cultural change, we have the long-established practise of penalising failure. We should understand that there is no perfect or one solution fits all, meaning that experimentation is an essential element to understand what works or not and what can we do differently to make things work and keep improving. Therefore, companies need to celebrate their failures, that they do things to learn and test, rather than penalise failure.

All this make us think and realise that any transformation can be at risk if we take into consideration how failure is managed within the organisation by the leadership.

On a similar note, Tabrizi, Behnam et al. article “Digital Transformation Is Not About Technology” published in HBR says that digital transformation does not come in a box — or a cloud. The authors share the five key lessons that help them lead their organisation through a successful digital transformation:

  • Lesson 1: Figure out your business strategy before you invest in anything;
  • Lesson 2: Leverage insiders;
  • Lesson 3: Design customer experience from the outside in;
  • Lesson 4: Recognise employees’ fear of being replaced;
  • Lesson 5: Bring Silicon Valley start-up culture inside.

What is interesting to note is that culture is again mentioned as a key factor in these five lessons.

After having read them, these are my thoughts on each of those lessons:

  • Lesson 1: Is focused on business strategy. Leadership should first understand the problem and what is the broader business strategy instead of following the old habit of selecting a tool they have in mind to implement digital transformation.
  • Lesson 2: Many times, organisations that seek transformations (digital or otherwise) frequently bring in outside consultants who tend to apply one-size-fits-all or differently known as silver-bullet solutions. Maybe our approach should instead rely on insiders — staff who have intimate knowledge about what works and what doesn’t in their daily operations.
  • Lesson 3: Often, organisations believe they know what the customers want and need when, in reality, they should ask them.
  • Lesson 4: The organisation needs to have or coach true leaders, so they recognise and work with employees’ to overpass their fear of change and being replaced.
  • Lesson 5: Start-ups are acknowledged by their agile decision making, rapid prototyping and flat structures.

Brainstorming in front of a whiteboard helped me to have a better understanding of the relationship between agile transformation, digital transformation, leadership and culture.

After a while, an image started to become clear—the image of Business Transformation Trinity, as shown below.

Business Transformation Trinity

Business Transformation Trinity by Eduardo Ribeiro, July 2020

As we can see:

  • Leadership is not Agile;
  • Agile transformation is not Digital Transformation;
  • Digital Transformation is not leadership;
  • Culture is the centre of everything.

The triangle edges are independent, and the edges are connected by the vertices (relationships), which support each other to achieve any transformation. Furthermore, culture is the key to make transformation a success. We know that change creates discomfort since people are getting out of their comfort zone and without a proper culture in place, we will face resistance and setbacks where the worst scenario could be giving up our transformation and returning to the old ways.

In conclusion, when we are driving an agile and/or digital transformation, we need to keep in mind that all triangle edges need to be worked on iteratively. We need to do this so we can measure the impact of our implemented change, and understand if it was a success or if we need to do it differently. Last but not least, we need constant collaboration with leadership so we can learn from these small failures and not return to the long-established practise of penalizing failure.

Once more, culture is key; it needs to be in our centre of attention and addressed appropriately since even a minor change can be the trigger for the change not being accepted and ultimately not working. Following Peter Bendor-Samuel suggestion in his article, maybe what we need to do is rename the term “failure” to something else that does not create a negative impact like “learnings”. Otherwise, people can misunderstand that the transformation journey failed when actually, we have learned.

In the end, I would like to send a special “thank you” to Anett Stoica for helping me to unblock during my brainstorming moment. For the received feedback about the article, Margarida Carvalho, Mike Sousa and once again Anett Stoica thank you!

#agile #agilty #digitaltransformation #leadership #culture

07.20.20
by

Food for thoughts… “Dealing with psychopaths during Agile change” by Erich R. Bühler!

Sometimes we see Agile Coaches and Agile Consultants trying to use the same coaching techniques with different types of people. They believe if they have successfully applied a coaching technique, the same will work with most of the people.

During my career, I realised that it is not the case. There is no universal recipe for an Agile Transformation/Change. Moreover, besides first understanding what is the problem we want to solve, it is key to keep in mind that we have to address a multitude of people and roles with different needs and level of resistance to change. While we can get some people on board from the early stages, depending on role, seniority or personal traits, we might need to adapt our coaching style to communicate our message better. After all, change means stepping out of our comfort zone.

Flowing my thoughts, today I’ve come across Eric´s article “Dealing with psychopaths during Agile change” in which he explains how to deal with Psychopathic or Narcissistic people during Agile change.

Thanks Erich R. Bühler, for sharing your thoughts on the matter.

#lean #agile #agility #continuousimprovement #highperformaceteams #change

05.19.19
by

Agile during the time of WAR and PEACE

When dealing with the methodologies of working, we hear a lot of interpretation and opinions.
Much of this feedback is constantly shared by members of our community, talking about the success or failure rates when adopting an agile methodology in their companies.

One of the much-discussed topics amongst us professionals is the reason why some companies are able to achieve success in transformation and others can’t. More importantly, what causes the initial enthusiasm and desire for improvement to quiet down and revert to the initial disbelief in the effectiveness of the methodology.

Having said that, a while ago I decided to write an article on this topic. I gathered all my thoughts and inputs collected both from businesses as well as from individuals with the desire to adopt an Agile Mindset and keep improving their way of working.

The moment has come to shed some light on what I think about this phenomenon.

I don’t remember who started this saying, but we all hear this quite often, “Agile is not the Silver Bullet”.

Photo by Velizar Ivanov on Unsplash.

The bullet concept reminded me of Lev Tolstoy´s famous novel, War and Peace. While we are not building here a literary commentary of the Russian masterpiece, we cannot overlook some similarities between Tolstoy’s characters and our modern-day corporate employees. Although situated in different centuries, both categories characters struggle with problems unique to their era, their history, and their culture in the process of adapting to the new times and changes.

What I’ve been observing is that two moments that can define weather adapting agile will be a success or a failure. In my experience, I call these moments the Time of War and time of Peace.

Photo by Vitor Pinto on Unsplash.

The Time of Peace…

Time of peace is what I consider to be the moment of engagement, specially buy-in from all stakeholders. Teams are split between being reluctant or enthusiastic about the change. At this point, the focus is on the benefits: predictability, transparency, empowerments, delivery at a faster pace. Potential challenges are acknowledged as being part of the journey until the moment of full transformation occurs. Even so, everybody is doing their best to take up the principles and values of Agile. The collective energy level is high, and this improvement process creates a new opportunity for people to build something together and become better at what there are doing while becoming a united and more autonomous team.

Photo by Eddie Kopp on Unsplash.

Teams are committed to making this work. Often times they repeat the mantra “Others did it, so why couldn´t we?”.

What amazes me is that they truly believe in the concept and are in fact doing all the work. Obstacle after obstacles, they are adapting and making it work!

Until…

The Time of War…

Photo by Specna Arms on Unsplash.

As so often specific for human behaviour, when the going gets tough. Everything is going well until this moment, the moment doubts or non-existing doubts appear.

What could happen to create this momentum?

Like most things having to do with human behaviour, this question does not have a single and ultimate truth as an answer. Environment, faulty processes and human nature all factor in.

From what I observed so far, it all gets down to pressure, the catalyst for a time of War.
Corporate environment can often times be a major influence. Pressure from upper management to see quick outcomes or ROI (return on investment), constant nudges from stakeholders powered by the fear of failure push the teams in untested waters too fast.
Broken processes leading to lack of transparency and communication on what, why and how to do will create further confusion and isolation.

Ultimately, the natural resistance to change, pushing too hard will lead to team burnout. And as always, not people but the concept will be to blame. An exhausted group of people will prefer to go back to what they know instead of spending more energy on fixing or adapting the “unknown evil” – this being in our case, the use of the agile methodology.

So, what is there to do?

I consider the breaking point of an adapting process to be when I hear the words “This doesn’t work for me”. Beyond this, there is no point of return. This is the moment that can make the difference between making this work or not.

I am a true believer of step by step, incremental changes. A Big bang approach puts far too much pressure on people and allows no real time for the mind to perceive and adapt to the new requirements. With small steps and iterative improvements “Time of War” moments can be dismantled, like a ticking bomb.

Across our adapting, we will have many “Times of War and Peace” but we need to keep our eye on the ball and remember that each “Time of War” it’s just one more obstacle we need to pass before getting over the finish line and make these principles and values part of our DNA.

With every obstacle passed, it gets easier.

Don’t stop here. This is just the beginning of the continuous improvement path.

Would be great to hear your thoughts on this topic.

Last but not least, we’d like to give a special “thank you” to Anett Stoica for the help with the article revision and all her feedback. Thank you!

04.07.19
by

My Podcasts at Scrum Master Toolbox Podcast

A few months ago I was challenged by my good friend Eddie Kenny and Vasco Duarte to participate in the Scrum Master Toolbox Podcast – A daily podcast for Scrum Masters and Agile Coaches.

I have accepted the challenge to be part of a podcast production while never having done anything similar before. It was not a simple as I have imagined, but with preparations and the guy´s support,  I was very happy with the final result.

To make it easier for you to follow, I’ve combined all 5 days content in one post below. To access the podcasts click the links bellow.

Hope that you enjoy listening as much as I enjoyed making them.

As always, feel free to share your feedback.

– Day ONE –

– Day TWO –

– Day THREE –

– Day FOUR –

– Day FIVE –