Nerdic by nature I started my career as a software engineer in the area of hard real time operating systems where direct access to hardware and inavailability of usual debugging tools is the rule. One has to focus on a high level of software maintainability since the most effective tool for debugging in this context is a glance at the source code. With that attitude I started as backend developer at ImmobilienScout24 responsible for the business critical backend systems. With the company growth it took a team to handle the development load on these systems so I became team lead. Back at that time the organisation was more tayloristic than agile. In 2008 another team lead in the development department and me changed the working mode of our teams to Scrum, initiating a change that quickly transformed the whole company. We experienced a huge gain in quality of work, life and product. That was a so amazing experience that I felt the urge to spread the word - and I stuck to it. Since then I worked in various roles in different companies always helping my employers or clients to maximise their chances to become and stay economically successful by adopting agile values, procedures and best practices.
My Mentoring Topics
- Agile Coaching
- Agile Leadership
- Agile Product Ownership
- Project Management at the edge between tayloristic and agile organisations
- Software Crafting
You need to be logged in to schedule a session with this mentor. Please sign in here or create an account.
The Five Dysfunctions of a Team - A Leadership Fable
Patrick M. Lencioni
Key Facts and Insights: The fundamental premise of the book is that teams often fail due to five common dysfunctions, which are: Absence of Trust, Fear of Conflict, Lack of Commitment, Avoidance of Accountability, and Inattention to Results. The book uses a business fable approach to convey the message, following a fictional company and its new CEO who identifies and resolves these five dysfunctions. The first dysfunction, Absence of Trust, is rooted in the team members’ unwillingness to be vulnerable and open with each other. This leads to a lack of trust and a fear of making mistakes. The second dysfunction, Fear of Conflict, arises from the team's inability to engage in unfiltered, passionate debate about things that matter, leading to inferior decision-making. Lack of Commitment is the third dysfunction, where team members, due to lack of clarity or buy-in, fail to fully commit to decisions, causing ambiguity about direction and priorities. Next is the Avoidance of Accountability, where team members hesitate to call out peers on their actions and behaviors that can potentially harm the team. The final dysfunction is Inattention to Results, where team members put their individual needs (such as ego, career development, or recognition) above the collective goals of the team. Through the fable, Lencioni provides practical advice for overcoming these dysfunctions. He suggests building trust through vulnerability, encouraging constructive conflict, gaining commitment through clarity and buy-in, holding team members accountable, and focusing on collective results. The book is not just about identifying the dysfunctions but also provides a model and actionable steps to overcome these dysfunctions and build a cohesive and effective team. At the heart of the book lies the idea that success in any team is dependent on overcoming these dysfunctions and working together towards a common goal. An In-Depth Summary and Analysis: "The Five Dysfunctions of a Team - A Leadership Fable" by Patrick M. Lencioni is an insightful book that unveils the reasons why teams often fail and offers practical advice on how to overcome these issues. Lencioni uses a business fable, a unique approach that combines storytelling with business principles, to illustrate his points and make the book relatable and engaging. The first dysfunction, Absence of Trust, is linked to the unwillingness of team members to be vulnerable and open with each other. This lack of transparency creates a culture of fear, where team members are afraid to make mistakes or take risks. As a long-standing academic in this field, I've seen how this lack of trust can paralyze a team, stifling creativity and innovation. Overcoming this dysfunction requires creating a safe environment where individuals feel comfortable expressing their thoughts, ideas, and potential misgivings. The second dysfunction, Fear of Conflict, stems from the team's inability to engage in meaningful, passionate debate about things that matter. This fear of conflict often leads to artificial harmony, where team members pretend to agree even when they have differing opinions. This avoidance of conflict can result in poor decision-making, as not all perspectives are considered. I believe that constructive conflict is a crucial component of a high-performing team. Encouraging open, honest debate ensures that all viewpoints are heard and considered, leading to better, more informed decisions. Lack of Commitment is the third dysfunction, where team members don't fully commit to decisions due to lack of clarity or buy-in. This lack of commitment can lead to ambiguity about the team's direction and priorities. In my experience, clear communication and the inclusion of all team members in the decision-making process can help overcome this dysfunction. The fourth dysfunction, Avoidance of Accountability, occurs when team members hesitate to call out peers on their actions and behaviors that could potentially harm the team. This avoidance often stems from a desire to maintain personal relationships and avoid conflict. However, holding each other accountable is crucial for maintaining high standards and achieving the team's collective goals. The final dysfunction, Inattention to Results, happens when team members prioritize their individual needs above the collective goals of the team. This can lead to a lack of focus on the desired results and a failure to achieve the team's objectives. Focusing on collective results and rewarding team success rather than individual achievements can help overcome this dysfunction. In conclusion, "The Five Dysfunctions of a Team - A Leadership Fable" is an insightful book that provides practical advice on overcoming common team dysfunctions. It highlights the importance of trust, constructive conflict, commitment, accountability, and a focus on results in creating a successful team. As a professor with years of experience in this field, I can attest to the effectiveness of Lencioni's methodology in transforming dysfunctional teams into high-performing ones. This book is an essential read for anyone looking to build or improve their team.
ViewNonviolent Communication: A Language of Life - Life-Changing Tools for Healthy Relationships
Marshall B. Rosenberg, Deepak Chopra
Key Facts and Insights from the Book Nonviolent Communication (NVC) is a process that facilitates understanding and empathy between individuals. NVC focuses on human needs and feelings rather than judgments and accusations. It involves four key steps: observation, feelings, needs, and requests. NVC encourages empathetic listening and honest expression. NVC can be applied in various contexts and relationships, including personal, professional, and social. Conflict resolution is a significant application of NVC. It helps in transforming conflicts into mutually satisfying outcomes. NVC is an effective tool to promote peaceful interactions and healthy relationships. NVC promotes self-empathy and compassionate giving. NVC helps in overcoming cultural conditioning and promotes genuine human connections. It encourages personal growth and emotional healing. NVC is a powerful tool in educational settings for fostering effective communication and understanding. In-Depth Analysis and Summary "Nonviolent Communication: A Language of Life - Life-Changing Tools for Healthy Relationships" by Marshall B. Rosenberg is a highly insightful book that presents a transformative approach to communication. It introduces the concept of Nonviolent Communication (NVC), a process rooted in principles of nonviolence and compassion. Rosenberg's work is underpinned by the belief that all human beings have the capacity for compassion and empathy, and that conflicts arise when strategies for meeting needs clash. NVC is not just a method of communication; it's an approach to living that cultivates respect, attentiveness, and empathy. It is a four-step process involving observation, feelings, needs, and requests. The first step, observation, involves stating what we are observing that is affecting our sense of wellbeing. The next step, feelings, involves sharing our feelings in relation to what we observe. The third step, needs, is about communicating what needs, values, or desires are causing our feelings. Finally, the request step involves making a clear, concrete request for action to meet our expressed needs. The book emphasizes that NVC is about empathetic listening and honest expression. It encourages us to listen empathetically to others and express ourselves honestly, without blame or criticism. This approach allows for a deeper understanding and connection between individuals, fostering healthier relationships. One of the significant applications of NVC, as Rosenberg points out, is conflict resolution. By focusing on the underlying needs and feelings instead of accusations and judgments, NVC can transform conflicts into mutually satisfying outcomes. Whether it's a personal disagreement, a workplace conflict, or even a social or political dispute, NVC provides a framework for peaceful resolution. NVC also promotes self-empathy and compassionate giving. It helps individuals to connect with their own feelings and needs, fostering self-understanding and personal growth. At the same time, it encourages compassionate giving, where we respond to the needs of others not out of obligation, but out of a genuine desire to contribute to their well-being. Rosenberg's work is particularly relevant in today's world, where communication often gets mired in misunderstandings and conflict. NVC offers a way to overcome our cultural conditioning that promotes competitive and judgmental interactions, and instead, cultivate genuine human connections. Conclusion "Nonviolent Communication: A Language of Life - Life-Changing Tools for Healthy Relationships" by Marshall B. Rosenberg is a powerful guide to promoting understanding, empathy, and compassion in our interactions. By shifting our focus from judgments and accusations to feelings and needs, NVC enables us to build healthier, more satisfying relationships. It is an invaluable tool for personal growth, emotional healing, and peaceful interactions in various contexts, including personal, professional, educational, and social. Whether you're seeking to improve your personal relationships, resolve conflicts, or simply communicate more effectively, this book offers profound insights and practical tools to guide you.
ViewClean Code - A Handbook of Agile Software Craftsmanship
Robert C. Martin
Key Insights from Clean Code - A Handbook of Agile Software Craftsmanship The importance of writing clean code and its impact on software maintenance and scalability. The principles of SOLID design: Single Responsibility, Open-Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion. How to correctly use comments in code and when to avoid them. The significance of meaningful names for variables, functions, classes, and modules. The concept of functions: how they should be small, do one thing, and do it well. The art of error handling and the importance of throwing meaningful exceptions. The principles of Test Driven Development (TDD) and the importance of writing tests first. The importance of keeping the codebase clean through continuous refactoring. The idea of code smells and how to identify them. How to manage system dependencies to ensure loose coupling. Analysis and Summary of the Book "Clean Code - A Handbook of Agile Software Craftsmanship" is a comprehensive guide that provides a deep dive into the principles and practices of writing clean, readable, and maintainable code. The book is grounded in the author's deep experience and understanding of software development and its challenges. The book opens with an emphasis on the importance of writing clean code. It asserts that code quality is a fundamental aspect of software development that directly impacts the maintenance, scalability, and overall health of software projects. It argues that code is read far more often than it is written, making readability a key quality attribute. The book introduces the SOLID design principles, a set of guidelines for object-oriented design and architecture. These principles aid in the development of software that is easy to manage and maintain, with a focus on avoiding code smells, reducing complexity, and improving readability. Comments are a double-edged sword. While they can provide important context and explanation, the book argues that they are often used as a crutch to justify complex or confusing code. Comments should not replace clear and concise code. Naming conventions are another crucial aspect of clean code. The book explains the importance of choosing meaningful and descriptive names for variables, functions, classes, and modules. Names should convey intent and make the code self-documenting. The book also provides detailed guidance on how to write functions. Functions should be small, do one thing, and do it well. This aligns with the Single Responsibility Principle, one of the SOLID principles. Error handling is another key topic. The book stresses the importance of throwing meaningful exceptions and managing errors in a consistent and predictable manner. It also covers Test Driven Development (TDD), a software development process that promotes writing tests before writing the actual code. TDD helps in ensuring that the code is working as expected and leads to modular, flexible, and bug-free code. The book emphasizes the need for continuous refactoring to keep the codebase clean. Refactoring is not just about rewriting code; it’s about improving the design of existing code while preserving its functionality. Code smells are certain structures in the code that suggest the possibility of a deeper problem. They are indicators of poor design and coding practices that need to be refactored. The book concludes with a discussion on how to manage system dependencies to ensure loose coupling, which makes systems more manageable and less prone to bugs. In summary, "Clean Code - A Handbook of Agile Software Craftsmanship" is a must-read for any serious software developer or engineer. It goes beyond teaching specific techniques or practices, instead instilling a mindset and philosophy towards writing code that is clean, understandable, and maintainable. To master the art of writing clean code, one must not only understand these principles but also incorporate them into their daily coding practice.
ViewManagement 3.0 - Leading Agile Developers, Developing Agile Leaders
Jurgen Appelo
Key Facts and Insights: Complexity Science: The book utilizes complexity science to illustrate how management can be seen as a complex adaptive system. Agile Methodology: It provides a detailed overview of Agile methodology and its application in software development and leadership. Management 3.0: The concept of Management 3.0 is introduced as a modern-day approach to leadership that involves managing the system, not the people. Empowerment and Responsibility: The book emphasizes the importance of empowering team members and fostering a culture of responsibility. Intrinsic Motivation: It discusses intrinsic motivation and how it leads to higher productivity and employee satisfaction. Competence Development: The book provides methods for competence development, including 360-degree feedback, peer feedback, and coaching. Change Management: It provides strategies for effective change management, including how to deal with resistance to change. Delegation Poker and Delegation Board: The book introduces tools like Delegation Poker and Delegation Board to help determine the level of authority and decision-making. Merit Money: The concept of Merit Money is discussed as a way to reward team members based on peer feedback. Management is too important to leave to the managers: The book promotes the idea that everyone in the team should be involved in management decisions. An In-Depth Analysis: The book "Management 3.0 - Leading Agile Developers, Developing Agile Leaders" by Jurgen Appelo is a comprehensive guide that explores modern management practices in the context of software development and agile leadership. The book challenges traditional management theories and proposes a new approach that is better suited to today's complex, rapidly changing environments. Complexity Science forms the theoretical backbone of the book. It suggests viewing organizations not as static hierarchies but as complex adaptive systems. This perspective allows us to better understand and manage the dynamics within teams and organizations. Agile Methodology is at the heart of the book. It delves into the principles and practices of Agile, a methodology originally developed for software development but now widely applied in various fields. Agile emphasizes adaptability, collaboration, and delivering value to customers. In the context of Agile, the book introduces Management 3.0, a novel approach to leadership that emphasizes managing the system, not the people. This approach recognizes that managers cannot control people or predict their behavior. Instead, they should focus on creating conditions that enable people to work effectively. Empowerment and Responsibility are two key themes in the book. Appelo argues that team members are more productive and motivated when they feel empowered and when they share responsibility for the team's success. This concept aligns well with the Agile principle of self-organizing teams. The book discusses Intrinsic Motivation, which refers to motivation that comes from within the individual. According to research, intrinsically motivated people are happier, more creative, and more productive. The book suggests ways to foster intrinsic motivation, such as providing autonomy, mastery, and purpose. Competence Development is another significant topic in the book. Competence refers to the ability to perform tasks effectively. The book provides practical tools and techniques for competence development, such as 360-degree feedback, peer feedback, and coaching. In the context of Change Management, the book provides valuable insights on how to manage change effectively, including dealing with resistance to change. Change is inevitable in today's fast-paced environment, and the ability to manage change is a critical skill for leaders. The book introduces innovative tools like Delegation Poker and Delegation Board to help leaders and teams determine the level of authority and decision-making. These tools enable teams to make decisions more effectively and efficiently. The concept of Merit Money is introduced as an alternative to traditional reward systems. In this system, rewards are based on peer feedback rather than top-down appraisal. This approach promotes a more collaborative and supportive environment. Finally, the book advocates for the idea that "Management is too important to leave to the managers". This means involving everyone in the team in management decisions. This approach fosters a sense of ownership and responsibility among team members. In conclusion, "Management 3.0" provides a fresh perspective on management and leadership, grounded in complexity science and Agile principles. It provides practical tools and techniques that can help leaders and teams navigate the complexities of today's work environment.
View
T.
23.March 2023Hi Lorenz, thank you for the open and lively conversation with me, it helped me with better understanding of the agile coach role and gave me clear ideas of the next steps I could take to advance my expertise in this direction. 🌱🌳