<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alexandre Claus on Medium]]></title>
        <description><![CDATA[Stories by Alexandre Claus on Medium]]></description>
        <link>https://medium.com/@alexandre-claus?source=rss-7f62c60a9ee4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*SzSYv1Bac9pMK1aY.jpg</url>
            <title>Stories by Alexandre Claus on Medium</title>
            <link>https://medium.com/@alexandre-claus?source=rss-7f62c60a9ee4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:25:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexandre-claus/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Prompt Chaining: A Step‑by‑Step Guide for Smarter AI Results]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://alexandre-claus.medium.com/prompt-chaining-a-step-by-step-guide-for-smarter-ai-results-d74a541e0f01?source=rss-7f62c60a9ee4------2"><img src="https://cdn-images-1.medium.com/max/2048/1*zS9IoIxETGUHAVTfwh9X2A.png" width="2048"></a></p><p class="medium-feed-snippet">Some projects are too large to complete in a single attempt, so you naturally break them down into steps. With generative AI, the same&#x2026;</p><p class="medium-feed-link"><a href="https://alexandre-claus.medium.com/prompt-chaining-a-step-by-step-guide-for-smarter-ai-results-d74a541e0f01?source=rss-7f62c60a9ee4------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://alexandre-claus.medium.com/prompt-chaining-a-step-by-step-guide-for-smarter-ai-results-d74a541e0f01?source=rss-7f62c60a9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/d74a541e0f01</guid>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[prompt-engineering]]></category>
            <category><![CDATA[generative-ai]]></category>
            <dc:creator><![CDATA[Alexandre Claus]]></dc:creator>
            <pubDate>Thu, 19 Feb 2026 15:12:28 GMT</pubDate>
            <atom:updated>2026-02-19T15:12:28.662Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Techniques for Creating User Stories and Features in Agile]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://alexandre-claus.medium.com/techniques-for-creating-user-stories-and-features-in-agile-0414d7311238?source=rss-7f62c60a9ee4------2"><img src="https://cdn-images-1.medium.com/max/600/1*vHNLCtdT7wIzK7TupUjYDQ.png" width="600"></a></p><p class="medium-feed-snippet">Introduction</p><p class="medium-feed-link"><a href="https://alexandre-claus.medium.com/techniques-for-creating-user-stories-and-features-in-agile-0414d7311238?source=rss-7f62c60a9ee4------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://alexandre-claus.medium.com/techniques-for-creating-user-stories-and-features-in-agile-0414d7311238?source=rss-7f62c60a9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/0414d7311238</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[business-analysis]]></category>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <dc:creator><![CDATA[Alexandre Claus]]></dc:creator>
            <pubDate>Wed, 10 Sep 2025 17:43:31 GMT</pubDate>
            <atom:updated>2025-09-10T17:43:31.575Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Supercharge Your Azure DevOps Workflow with the Feature Deliverable Extension]]></title>
            <link>https://alexandre-claus.medium.com/supercharge-your-azure-devops-workflow-with-the-feature-deliverable-extension-2fda01477f42?source=rss-7f62c60a9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2fda01477f42</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[azure-devops]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Alexandre Claus]]></dc:creator>
            <pubDate>Fri, 07 Mar 2025 11:23:34 GMT</pubDate>
            <atom:updated>2025-03-07T11:23:34.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*SDNwVejj6_35VX87" /><figcaption>Generated by ChatGPT based on the article.</figcaption></figure><p>Sometimes, even in an Agile environment, we need to assess the risks that a development requires.</p><p>Usually, during the Software Development Life Cycle, some questions must be asked, especially at the Epics and Features level.</p><p>In most cases, an Excel questionnaire is presented. The product owner or project manager must evaluate the impact of the changes.</p><p>As projects grow more complex, teams can struggle to track and organize each feature effectively. That’s where the Feature Deliverable Extension by Agile Coaching Solutions steps in — helping you transform complexity into clarity within Azure DevOps.</p><p>This post is not about the technical aspect of the extension. However, the source code is under MIT Licence, so it is free, and you have some technical elements explained on the <a href="https://marketplace.visualstudio.com/items?itemName=AgileCoachingSolutionsFeatureAddon.feature-livrable-extension"><strong>Feature Deliverable Extension page</strong></a><strong>.</strong></p><h4>What is the Feature Deliverable Extension?</h4><p>The <strong>Feature Deliverable Extension</strong> is a specialized add-on for Azure DevOps designed to enhance work item management. It introduces a new tab that displays deliverables associated with each work item. This extension is handy for teams that need to track the progress of features and epics, ensuring that all deliverables are accounted for and completed on time.</p><p>The initiative was to track specific deliverables, such as Test Plans, Test Cases, Architecture reviews, solution blueprints, etc., depending on the complexity of the project or changes to the Risk Assessment questionnaire.</p><p>To follow these steps in Excel, I have written this extension to have the questionnaire inside the different work items in Azure DevOps.</p><h4>Key Features</h4><ol><li><strong>Deliverables Tracking</strong>: This extension&#39;s primary function is to provide a clear and concise view of the deliverables linked to a work item. This feature is invaluable for project managers and developers who need to keep track of multiple tasks and ensure that nothing slips through the cracks.</li><li><strong>Integration with Azure Boards</strong>: The extension seamlessly integrates with Azure Boards, allowing teams to manage their backlogs, sprints, and work items more efficiently. Adding a dedicated tab for deliverables enhances the existing functionality of Azure Boards, making it easier to monitor progress and identify bottlenecks.</li><li><strong>Customizable Views</strong>: Users can customize the views to suit their needs, ensuring that the most relevant information is always at their fingertips. This capability is crucial for teams with unique workflows that require tailored solutions.</li><li><strong>Enhanced Collaboration</strong>: The extension fosters better collaboration among team members by providing a centralised location for deliverables. Everyone can see the status of deliverables in real time, reducing the need for constant updates and meetings.</li></ol><h4>Let&#39;s see how it works</h4><ul><li>Set up a new custom field, “AnswersField” (Will hold the questionary answers) &amp; “RoleAssignmentsField” (Will have the role &amp; responsibilities for the RACI table) in a process; this field can be hidden from the work item type.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZC9UjCK-yPWpXdsH.png" /><figcaption>Update the ad-hoc process accordingly to your organisation</figcaption></figure><ul><li>I have also created three new pages in the sample below that will use the ad-hoc contribution.</li></ul><ol><li>SDLC, which will present the questionnaire inside the work Item form</li><li>RACI will be used to assign roles and responsibilities to each deliverable.</li><li>RACI table, which will show the actual RACI Table</li></ol><p>The custom fields that need to be added to <strong>AnswersField </strong>will hold the answers related to the questionnaire in the format JSON.</p><p><strong>RoleAssignmentField</strong> keeps track of the roles and responsibilities related to the questionnaire, which is also stored in JSON format.</p><p>Custom fields are a convenient way to store information. In our case, they can be set as non-visible, as they should not be updated manually. However, the advantage of using custom fields is that they can be retrieved later via APIs or collected through the OData protocol and used, for example, in PowerBI reporting.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tn1PqccN0xdoTQO7.png" /></figure><p>For each page, select the corresponding contribution:</p><p>So, the extension comprises several contributions supporting the different areas.</p><p>Under the SDLC page, I have added the <strong>Deliverable Control</strong> and under a second group, the <strong>Progress Indicator.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*qL0GsfCEVPp_eg4f.png" /><figcaption>Adding Deliverable control and Progress Indicator</figcaption></figure><p>Under the RACI page, as you can imagine, you will need to add the <strong>RACI Control</strong> shown below</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iMdjPcSE3UDdQATW.png" /><figcaption>The RACI control in the Page</figcaption></figure><p>The same applies to the <strong>RACI table contribution to </strong>the RACI TABLE page.</p><p>When done, you must set your first list of deliverables related to the Azure Project inside the Project Setting in Azure DevOps, as shown below.</p><p>You can set the answer for each deliverable as a path to a folder or URL, a work ID for the test case, or a boolean value, such as &quot;done&quot; or &quot;not done.&quot;</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/586/0*SoAjZn5ScmEjGfuU.png" /></figure><p>Next, a set of questions will be assigned to those deliverables. Please note that some questions may require any deliverable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/690/0*ycHJq4DWJ3J3toCX.png" /><figcaption>Questionary</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/0*x8bfkVH5al9mveQx.png" /><figcaption>Assign deliverable to questions</figcaption></figure><p>People might be lazy, especially developers. ☺️<br>I also decided to provide the possibility of creating a hierarchy of work items with one click. Below is a sample of a possible setup, and I will explain how it is used later.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/593/0*utrlui_JCgUqXAAj.png" /></figure><p>Finally, the last step is to define a list of Roles that might be involved</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/631/0*BxUB_3HiOjx2doSz.png" /></figure><p>Case study, or how do we use it now?</p><p>Usually, when a new change is requested, especially if it is relatively significant, it is a good practice to set an Epic work item.</p><p>This is where the One-click to create the hierarchy could actually be used.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/0*lQP60kD8Vf3b21iW.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/807/0*pA9Q8hu-Cwg7W93_.png" /><figcaption>Use the one click to create Feature as a child of an Epic</figcaption></figure><p>Now that the initial feature as a child of Epic has been created, you can go to the SDLC TAB.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HvwxKCY3JU8dDr3G.png" /></figure><p>In this case, the first question, called in my case “Default Control”, is the minimum requirement that needs to be provided.</p><p>So, when checked, it is expected to provide the path to the Solution Blueprint, ensure that component tests have been done, etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LZzdr-hMh0h1tz_1.png" /></figure><p>Now, it is time to assign roles and responsibilities for each deliverable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/709/0*NP8UOpbdw6ofxYQy.png" /><figcaption>Role Assignments</figcaption></figure><p>Once this is done, you can click on the “RACI TABLE” tab to see the effective RACI Table.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8yX-bydf1Nmqejog.png" /><figcaption>VISUAL RACI TABLE</figcaption></figure><h4>Benefits of Using the Feature Deliverable Extension</h4><ul><li><strong>Improved Visibility</strong>: The extension offers improved visibility into the status of deliverables, helping teams stay on track and meet their deadlines.</li><li><strong>Efficient Project Management</strong>: Project managers can streamline their processes and reduce administrative overhead by integrating deliverables tracking into the work item form.</li><li><strong>Better Decision-Making</strong>: With real-time data on deliverables, teams can make more informed decisions, prioritize tasks effectively, and allocate resources more efficiently.</li><li><strong>Enhanced Productivity</strong>: The extension eliminates the need for manually tracking deliverables, freeing up developers&#39; time to focus on their strengths: writing code.</li></ul><h4>How to Get Started</h4><p>Installing the <strong>Feature Deliverable Extension</strong> is straightforward. Here are the steps to get you up and running:</p><ol><li><strong>Visit the Visual Studio Marketplace</strong>: Navigate to the <a href="https://marketplace.visualstudio.com/items?itemName=AgileCoachingSolutionsFeatureAddon.feature-livrable-extension"><strong>Feature Livrable Extension page</strong></a> on the Visual Studio Marketplace.</li><li><strong>Install the Extension</strong>: Click the “Get it free” button to install the extension. If you don’t have the necessary permissions, you can request an administrator install it.</li><li><strong>Configure the Extension</strong>: Configure the extension to suit your team’s needs once installed. Add the deliverables tab to your work item forms and start tracking your deliverables more efficiently.</li></ol><h4>Conclusion</h4><p>The <strong>Feature Livrable Extension</strong> is a game-changer for teams using Azure DevOps. Providing a dedicated space for tracking deliverables enhances visibility, improves collaboration, and streamlines project management. Whether you’re a project manager looking to optimize your workflows or a developer aiming to stay on top of your tasks, this extension offers the tools you need to succeed.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2fda01477f42" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Practical Steps for Cultivating an Agile-Supportive Culture]]></title>
            <link>https://alexandre-claus.medium.com/practical-steps-for-cultivating-an-agile-supportive-culture-6c801af34bc8?source=rss-7f62c60a9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/6c801af34bc8</guid>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[culture-change]]></category>
            <dc:creator><![CDATA[Alexandre Claus]]></dc:creator>
            <pubDate>Thu, 28 Mar 2024 11:25:37 GMT</pubDate>
            <atom:updated>2024-03-28T11:25:37.504Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vs0ILV9SVMadk3eaaxKoPQ.jpeg" /></figure><h3>The Tool</h3><p>As stated in my first <a href="https://medium.com/@alexandre-claus/shaping-agile-futures-integrating-barrett-and-lalouxs-insights-into-corporate-culture-evolution-f393e3e38fd7">article</a>, I have compiled the tool created by Jean-Francois Helie-Shilov, which I learned during my ICP-ENT training, into a Klaxoon board. But it could be a physical or any other digital board, like a Mural, Miro, etc.</p><p>So, you understand that it is used to support the facilitation of a workshop about an organisation&#39;s culture.</p><p>You will, of course, need to introduce the context, and I hope that my posts on the topic provide enough guidance and inspiration😁</p><p>Therefore, I would introduce the following subject: What is culture about?</p><p>It might be interesting to describe the colours coded by Frederic Laloux, below is my introduction page.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HTJfaoTF2lPbYpUSjTjkRw.png" /><figcaption>Introduction</figcaption></figure><p>Once you have discussed the different evolutions, show the board below and let the audience consider their current organizational culture.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QFGjVYp0nBViBl4WPm67tA.png" /><figcaption>Cultural diagnosis survey</figcaption></figure><p>Creating enough space between the current and target cultures may be necessary depending on the number of participants.</p><p>Introduce the list of keywords presented below, and discuss the<br>characteristics of the colour. Are they relevant?<br>We can increase the numbers and make some adjustments.</p><p>Explain that the exercise is for each participant to choose a couple of characteristics, write them on a Post-it and, based on the colour, place them on the board at the respected level.</p><p>The matrix of characteristics:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/947/1*t_Kh45EuKwwIwpB6MBdY2A.png" /><figcaption>Keywords</figcaption></figure><p>Once the current culture has been set, ask the group if they agree.</p><p>It might be necessary to challenge them, as working at a multinational fast food chain or a carmaker manufacturer doesn’t involve the same needs.</p><p>In the second stage, you must let them think about the ideal vision of the culture they want to target.</p><p>What would help them align with their cultural vision for the organisation?</p><p>Repeat the exercise, but represent the targeted culture this time.</p><p>Below is a result of a specific case to show you what it looks like.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NW-w8sqnDUHLHvvoMpDylg.png" /><figcaption>Feedback from employees of Company X</figcaption></figure><p>The idea is to seek the employees&#39; limiting factors. Limiting factors are characteristics which, for example, demotivate the spirit of the cultural environment or are not in line with the ethics accepted by the group.<br>Mark those characteristics on the Post-it; the letter ‘L’ is represented in the above example.</p><p>Then, ask the group which elements they have today and wish to keep. Mark them with a ‘K’.</p><p>Now, it is time to look at the ones that will be motivating and be used as a driver, discuss their practicality, and see if some of them could easily be implemented.</p><p>In conclusion, the ultimate goal is to decide on an action plan that could be established to move from the current situation to the targeted one.</p><p>In IT change management, we refer to the AS-IS situation vs the To BE.</p><p>Action Plan:</p><ul><li>Work on limitations first, seeking a consensus.</li><li>Reinforce base values (capitalise on these). Some companies have specificities or trademarks on which they have been built; over time, these could be eroded and need to be re-enforced.</li><li>Develop drivers for the changes, look for the ultimate goal, and consider how we can reach the driving element for the well-being of all.</li></ul><p>This discussion could not be one-time only; it should be part of a review and discussed over time as the organisation and its people evolve.</p><p>- Additional Resources</p><p>- Suggest further reading, including Barrett’s books (“The Values-Driven Organization”), Laloux’s (“Reinventing Organizations,”) and Peter M Senge’s (“The Fifth Discipline”) for more in-depth insights into developing a culture that supports Agile transformation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6c801af34bc8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Evolution of Organisational Consciousness: Barrett & Laloux.]]></title>
            <link>https://alexandre-claus.medium.com/evolution-of-organisational-consciousness-barrett-laloux-1a04ef49d323?source=rss-7f62c60a9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/1a04ef49d323</guid>
            <category><![CDATA[evolution]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[change-management]]></category>
            <dc:creator><![CDATA[Alexandre Claus]]></dc:creator>
            <pubDate>Thu, 14 Mar 2024 15:14:34 GMT</pubDate>
            <atom:updated>2024-03-28T11:29:23.248Z</atom:updated>
            <content:encoded><![CDATA[<p>2/3, a continuation of my <a href="https://medium.com/@alexandre-claus/shaping-agile-futures-integrating-barrett-and-lalouxs-insights-into-corporate-culture-evolution-f393e3e38fd7">previous article</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UwOyI-Rq-6ku2nh1AQwzfw.jpeg" /><figcaption>AI-generated image based on title &amp; introduction</figcaption></figure><p><em>Richard Barrett’s organisational consciousness model categorises organisations’ cultural evolution into seven levels in his book “The Values-Driven Organization”, each reflecting a distinct focus, set of values, and stage of development. This model can provide a valuable framework for understanding and guiding the cultural shifts necessary for a successful Agile transformation. Here’s an outline of each level and how it can motivate and support the objectives of Agile transformation:</em></p><p><strong>Level 1: Survival</strong></p><p>- Focus: Financial stability and securing resources to ensure the organisation’s survival.</p><p>- Agile Connection: At this level, the emphasis on quick adaptation and efficient problem-solving in Agile methodologies can help organisations more effectively manage resources and respond to immediate market pressures, enhancing their survival capabilities.</p><p><strong>Level 2: Relationships</strong></p><p>- Focus: Building strong relationships and internal cohesion among team members.</p><p>- Agile Connection: Agile practices encourage collaboration, open communication, and trust, crucial to developing strong interpersonal relationships. This level supports the creation of cohesive, high-performing teams crucial for Agile success.</p><p><strong>Level 3: Self-Esteem</strong></p><p>- Focus: Achievement, performance, and excellence to build reputation and competitive advantage.</p><p>- Agile Connection: Agile frameworks foster a culture of continuous improvement and recognition of team achievements. This aligns with the drive for excellence and can motivate teams to strive for high performance.</p><p><strong>Level 4: Transformation</strong></p><p>- Focus: Adaptability, innovation, and embracing change.</p><p>- Agile Connection: This level directly supports the Agile principle of responding to change over following a plan. Cultivating a culture that values adaptability and innovation is essential for Agile transformation, enabling organisations to pivot quickly in response to new opportunities or challenges.</p><p><strong>Level 5: Internal Cohesion</strong></p><p>- Focus: Alignment around shared values and a sense of purpose beyond survival or financial success.</p><p>- Agile Connection: Agile transformation requires a shared vision and values that align with Agile principles, such as customer focus and team collaboration. This level of consciousness fosters a unified culture that supports the deeper implementation of Agile methodologies.</p><p><strong>- Level 6: Making a Difference</strong></p><p>- Focus: Contributing to the community and positively impacting society.</p><p>- Agile Connection: Agile methodologies emphasise delivering value to customers and stakeholders. Organisations at this level are well-positioned to leverage Agile practices to innovate and create products or services that make a meaningful difference.</p><p><strong>Level 7: Service</strong></p><p>- Focus: Service to humanity and the planet, transcending organisational boundaries.</p><p>- Agile Connection: At the pinnacle of Barrett’s model, the focus on service aligns with the Agile spirit of creating solutions that serve broader societal and environmental needs. Organisations operating at this level are driven by a purpose that the Agile mindset can help fulfil through their emphasis on sustainability, adaptability, and engagement.</p><h3>Application to Agile Transformation</h3><p>Barrett’s model provides a roadmap for cultural evolution that can significantly facilitate an Agile transformation. By understanding the current level of organisational consciousness, leaders can identify the specific cultural shifts needed to support Agile values and practices. Moving up through the levels involves fostering a culture that progressively aligns more closely with Agile principles, from enhancing flexibility and collaboration to ultimately serving a higher purpose through innovative and responsive business practices.</p><p>Incorporating Barrett’s model into the Agile transformation process can help organisations adopt Agile methodologies and ensure these changes are deeply rooted in values and purposes that drive long-term success and fulfilment for employees, customers, and the broader community.</p><p>***</p><p><em>Frederic Laloux’s work, particularly in his book “Reinventing Organizations,” presents a compelling evolution of organisational paradigms through different stages, colour-coded as Red, Amber, Orange, Green, and Teal. Each colour represents a distinct stage in the organisation’s consciousness and operational style, moving from traditional and mechanistic to more soulful, purpose-driven entities. Here’s an outline of each paradigm and its relevance to Agile transformation:</em></p><p><strong>Red: Impulsive</strong></p><p>- Characteristics: Power-oriented, led by a strong leader. This paradigm is typical of tribal cultures and early forms of organisation.</p><p>- Agile Relevance: While not directly related to Agile principles, understanding the Red paradigm helps identify the roots of power dynamics and command-control structures that Agile seeks to move away from.</p><p><strong>Amber: Conformist</strong></p><p>- Characteristics: Highly structured and hierarchical, focusing on stability, order, and control. Organisations in this stage operate through rigid roles and centralised authority.</p><p>- Agile Relevance: Moving beyond the Amber paradigm is crucial for Agile transformation, as Agile requires flexibility, decentralised decision-making, and empowerment of individuals and teams.</p><p><strong>Orange: Achievement</strong></p><p>- Characteristics: Goal-oriented and competitive, with innovation and success as core drivers. The Orange paradigm introduced the concept of meritocracy and accountability in organisations.</p><p>- Agile Relevance: The Orange stage focuses on innovation and efficiency with Agile. However, Agile transformation encourages shifting from solely achievement-focused to a more holistic view that values collaboration, sustainability, and well-being.</p><p><strong>Green: Pluralistic</strong></p><p>- Characteristics: Focused on empowerment, consensus, and values-driven culture. Green paradigm organisations prioritise community, stakeholder engagement, and egalitarian practices.</p><p>- Agile Relevance: The Green stage aligns closely with Agile principles, emphasising people over processes, collaboration, and a shared purpose. Agile transformations thrive in environments where the Green values of empowerment and community are prevalent.</p><p><strong>Teal: Evolutionary</strong></p><p>- Characteristics: Defined by self-management, wholeness, and a purpose-driven approach that views the organisation as a living entity. Teal organisations foster environments where employees are encouraged to bring their whole selves to work and where the organisation’s direction is shaped by its evolutionary purpose.</p><p>- Agile Relevance: Teal is the most aligned with Agile, embodying adaptability, autonomy, and a focus on delivering value. The move towards Teal represents a significant shift in organisational culture and structure, enabling a truly Agile way of working where teams are self-organising, and the organisation is responsive to change.</p><h3>Application to Agile Transformation</h3><p>Laloux’s model offers a framework for understanding the cultural and operational shifts required for an Agile transformation. It highlights the journey from traditional, hierarchical models to more flexible, inclusive, and purpose-driven forms of organisation. This journey mirrors the Agile transformation process, which seeks to create environments prioritising human potential, adaptability, and a shared sense of purpose.</p><p>By recognising the characteristics of each paradigm, leaders can better assess their current organisational culture and identify the changes needed to support Agile principles. Moving towards a Teal organisation, emphasising self-management, evolutionary purpose, and wholeness, can serve as a guiding vision for Agile transformation, motivating organisations to adopt practices that enable more significant innovation, resilience, and fulfilment for all stakeholders.</p><p>Incorporating insights from Laloux’s work into the Agile transformation process can help organisations navigate the complex cultural shifts involved, ensuring that changes are not just superficial adjustments in methodology but are deeply rooted in a transformative approach to work and organisational life.</p><p>As Frederic Laloux described in “Reinventing Organizations,” Teal organisations are characterised by self-management, wholeness, and an evolutionary purpose. These core principles align closely with Agile methodologies, prioritising flexibility, collaboration, and continuous value delivery. Below are key areas where Teal organisations and Agile principles intersect, along with examples of practices and structures that reflect this alignment:</p><p><strong>Self-Management</strong></p><p>- Agile Alignment: Agile methodologies encourage autonomy and empower teams to manage workloads, make decisions, and solve problems independently.</p><p>- Teal Practices:</p><p>- Cross-functional teams: Teal organisations often use cross-functional teams that combine various skills and perspectives. These teams operate without traditional hierarchical structures, like Agile teams that plan, execute, and review their work collaboratively.</p><p>- Decentralised decision-making: Teal organisations decentralise decision-making, allowing decisions to be made at the level of work rather than by top management. Agile teams are empowered to make project-related decisions, enhancing responsiveness and efficiency.</p><p><strong>Wholeness</strong></p><p>- Agile Alignment: Agile principles emphasise people over processes and encourage teams to bring their whole selves to their work, fostering a holistic work environment.</p><p>- Teal Practices:</p><p>- Open spaces and communal areas: Many Teal organisations design their workspaces to encourage collaboration, openness, and a sense of community, much like Agile teams, which typically work in open spaces that facilitate accessible communication and cooperation.</p><p>- Personal and professional development programs: Teal organisations support employees’ personal growth and development, aligning with Agile’s focus on team members’ well-being and continuous improvement.</p><p><strong>Evolutionary Purpose</strong></p><p>- Agile Alignment: Agile methodologies focus on delivering customer value by responding to changing needs and fostering continuous improvement. This resonates with the Teal principle of allowing the organisation’s purpose to evolve based on internal and external influences.</p><p>- Teal Practices:</p><p>- Feedback loops and adaptation mechanisms: Teal organisations implement systems for regular feedback from employees, customers, and other stakeholders. Agile practices such as sprint reviews and retrospectives serve a similar purpose, enabling continuous refinement and adaptation.</p><p>- Innovation labs or hackathons: To stay aligned with their evolutionary purpose, Teal organisations may create spaces for innovation, such as labs or regular hackathons. This mirrors Agile’s emphasis on innovation and experimentation to meet changing customer needs and market conditions.</p><p>***</p><p>Assessment and Awareness: It is recommended that the current corporate culture and its preparedness for Agile be honestly evaluated. Tools like Barrett’s and Laloux’s Cultural Transformation Tools can provide valuable insights.</p><p>Leadership and Vision: Leaders must model Agile values and create a vision aligned with higher organisational consciousness levels.</p><p>- Training and Support: Comprehensive training and ongoing support are recommended for teams to adopt Agile practices effectively.</p><p>- Iterative Improvement: Encouraging a continuous learning and improvement culture by seeking feedback and making necessary adjustments.</p><p><strong>Conclusion</strong></p><p>- Long-Term Commitment: Developing a culture that supports Agile transformation is a long-term commitment, requiring persistent effort, leadership buy-in, and a willingness to evolve.</p><p>- Transformational Impact: Finally, it’s important to note the transformational impact that cultural evolution can have on various aspects of an organisation, such as employee engagement, customer satisfaction, and overall success.</p><p><a href="https://medium.com/@alexandre-claus/practical-steps-for-cultivating-an-agile-supportive-culture-6c801af34bc8">Next</a>, I will describe the tool that might be used to assess the culture in your organisation. — Enjoy!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1a04ef49d323" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Shaping Agile Futures: Integrating Barrett and Laloux’s Insights into Corporate Culture Evolution.]]></title>
            <link>https://alexandre-claus.medium.com/shaping-agile-futures-integrating-barrett-and-lalouxs-insights-into-corporate-culture-evolution-f393e3e38fd7?source=rss-7f62c60a9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/f393e3e38fd7</guid>
            <category><![CDATA[change-management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[organizational-culture]]></category>
            <category><![CDATA[evolution]]></category>
            <dc:creator><![CDATA[Alexandre Claus]]></dc:creator>
            <pubDate>Wed, 13 Mar 2024 09:28:05 GMT</pubDate>
            <atom:updated>2024-03-28T11:27:55.880Z</atom:updated>
            <content:encoded><![CDATA[<p>1/3</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wtzDiQPBAyZ-Wd9C2fOfhw.jpeg" /><figcaption>Generated by AI based on my title</figcaption></figure><p>During my professional coaching training, I delved deeply into the dynamics of organisational transformation, mainly through the lens of Agile methodologies. My background in IT naturally inclined me towards understanding Agile principles and their pivotal role in addressing resistance to change — a common obstacle in organisational development. Consequently, the role of an Agile Coach becomes indispensable in guiding organisations through this transformative journey. In this post, I aim to share insights that emerged from my final dissertation and were further enriched during my ICP-ENT training. This tool, created by Jean-Francois Helie-Shilov, stimulates reflection on corporate culture. Initially crafted in French and drawing upon Barrett’s work, I have chosen to adapt and present it through the insightful perspectives of Frederic Laloux. This approach bridges language barriers and offers a nuanced understanding of organisational culture and its evolution in Agile transformation.</p><h3>Introduction to Corporate Culture and Agile Transformation</h3><p><strong>Corporate culture</strong></p><p>Corporate culture refers to the collective values, beliefs, behaviours, and norms that shape an organisation’s social and psychological environment. The underlying essence influences how an organisation operates and interacts internally and externally. This culture is manifested through various elements, including:</p><p>- Values: The core principles and ethical standards that guide the organisation’s decisions, actions, and priorities. Values are the moral compass that helps employees determine right from wrong and set the direction for the organisation’s goals and practices.</p><p>- Beliefs: The shared convictions or perceptions held by members of the organisation about how the world works and their place within it. These beliefs influence how employees interpret challenges and opportunities and inform their responses.</p><p>- Behaviours: Employees’ observable actions and practices at all levels reflect the organisation’s values and beliefs. Behaviours are the tangible expressions of culture, seen in how people collaborate, communicate, and solve problems.</p><p>- Social Environment: The atmosphere created by the employees’ collective behaviours, interactions, and relationships. This environment can be supportive and inclusive, fostering collaboration and innovation, or it can be competitive and siloed, hindering cooperation and growth.</p><p>Corporate culture is the foundation of how work gets done and how employees interact with each other and stakeholders outside the organisation. It influences everything from strategic decision-making to day-to-day operations, impacting employee morale, productivity, and retention. A positive and robust corporate culture aligns with the organisation’s goals, enhances employee engagement and satisfaction, and contributes to achieving business objectives.</p><p>***</p><p>Agile transformation is a comprehensive process wherein organisations adopt Agile methodology to enhance their project management and product development practices. This methodology, rooted in the <a href="https://agilemanifesto.org/">Agile Manifesto</a>, prioritises flexibility, rapid delivery, customer satisfaction, and high employee involvement. Here’s a closer look at what Agile transformation entails and the cultural shift it necessitates:</p><p><strong><em>Agile Methodology at its Core</em></strong></p><p><em>Agile methodology is a set of principles for software development, but not only today, under which requirements and solutions evolve through the collaborative effort of self-organising and cross-functional teams. It advocates adaptive planning, evolutionary development, early delivery, and continual improvement and encourages flexible responses to change.</em></p><p><strong>Key Focus Areas of Agile Transformation</strong></p><p>- Flexibility: Agile transformation emphasises adapting quickly to market changes, customer needs, and new information. This flexibility allows organisations to pivot their strategies, ensuring they remain competitive and relevant.</p><p>- Customer Satisfaction: Central to Agile is the focus on delivering value to the customer early and continuously. By involving customers throughout the development process, Agile methodologies ensure that the final product is more closely aligned with customer needs and expectations.</p><p>- Employee Involvement: Agile transformation requires a high level of employee involvement, where teams are empowered to make decisions, self-organize, and collaborate closely. This approach leverages the diverse skills and perspectives within the team, leading to more innovative solutions and a greater sense of ownership among team members.</p><p><strong>The Cultural Shift Required for Agile Transformation</strong></p><p><em>Achieving a successful Agile transformation involves more than just changing processes and tools; it requires a fundamental shift in corporate culture. This cultural evolution must embrace the following:</em></p><p>- Openness to Change: The organisation must foster a culture where change is not only expected but welcomed as an opportunity for improvement and innovation.</p><p>- Collaboration and Communication: Agile thrives in environments with open communication and collaboration within teams and across the organisation. Silos need to be broken down, and information must flow freely.</p><p>- Empowerment and Trust: Employees should feel empowered to take initiative and make decisions. This requires trust from leadership that teams will deliver their best work when given autonomy.</p><p>- Learning and Continuous Improvement: A culture that values learning from successes and failures is crucial. Continuous improvement should be an ongoing goal, with regular reflections and adjustments being part of the process.</p><p>- Customer-Centric Approach: The entire organisation needs to align with a customer-centric approach, understanding that delivering value to the customer is the goal of any project.</p><p>Agile transformation is a strategic effort that impacts all aspects of an organisation. It’s not just about adopting new methodologies but about embracing a new culture that supports the Agile principles of flexibility, customer focus, and employee engagement. This transformation can significantly improve how projects are managed and products are developed, ultimately contributing to the organisation’s success.</p><p><strong>The Role of Corporate Culture in Agile Transformation</strong></p><p><em>Agile transformation fundamentally reshapes an organisation’s operations, emphasising speed, flexibility, and responsiveness to change. For this transformation to be successful, it necessitates a supportive culture that embodies collaboration, adaptability, and continuous learning. However, cultural barriers, particularly resistance to change, can significantly impede the adoption and effectiveness of Agile practices. Here’s how these elements interact:</em></p><p><strong>Collaboration</strong></p><p>- Agile Necessity: Agile methodologies thrive on teamwork and the collective efforts of cross-functional teams. Collaboration is vital to Agile’s iterative approach, enabling rapid problem-solving and innovation.</p><p>- Cultural Support: A culture that supports collaboration encourages open communication, shared responsibilities, and mutual respect among team members. It breaks down silos and promotes a unified effort towards common goals.</p><p>- Impact of Resistance: In a culture where individual achievement is prioritised over teamwork or where departments are isolated, the collaboration essential to Agile cannot flourish. This resistance to collaborative practices hinders the flow of information and reduces efficiency.</p><p><strong>Adaptability</strong></p><p>- Agile Necessity: The Agile framework accommodates change, allowing organisations to pivot quickly in response to new information or market demands. Adaptability is a core component, ensuring that projects remain aligned with client needs and business objectives.</p><p>- Cultural Support: A supportive culture views change positively as an opportunity for improvement rather than a threat. It fosters an environment where experimentation is encouraged, and failure is considered a learning opportunity.</p><p>Impact of Resistance: Cultures resistant to change are rigid, with established processes and mindsets predominating. In such environments, the agility to adapt to new challenges or iterate based on feedback needs to be improved.</p><p><strong>Continuous Learning</strong></p><p>- Agile Necessity: Continuous learning underpins the iterative nature of Agile methodologies, where teams regularly reflect on their performance to identify improvements. This learning mindset ensures that processes are constantly refined and optimised.</p><p>- Cultural Support: Cultures prioritising learning and development create an atmosphere where employees are encouraged to acquire new skills, share knowledge, and challenge existing ideas. This openness to growth is essential for sustaining Agile practices.</p><p>- Impact of Resistance: A culture that is resistant to learning — one that punishes mistakes rather than viewing them as growth opportunities — can limit innovation and discourage the experimentation necessary for Agile. Employees in such cultures are less likely to propose new ideas or approaches, reducing the organisation’s ability to evolve.</p><p><strong>Overcoming Cultural Barriers</strong></p><p>To overcome these cultural barriers, organisations must actively work to cultivate an environment that aligns with Agile values. Leadership plays a critical role in this process, modelling the desired behaviours and setting the tone for the organisation. Initiatives include training programs to develop collaborative skills, creating forums for cross-departmental communication, and establishing feedback mechanisms that encourage continuous improvement.</p><p>Empowerment and Ownership: Agile methodologies thrive in environments where employees feel empowered and take ownership of their work. This requires shifting from traditional hierarchical cultures to more flat and open structures.</p><p>***</p><p><a href="https://medium.com/@alexandre-claus/evolution-of-organisational-consciousness-barrett-laloux-1a04ef49d323">Next Article</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f393e3e38fd7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Create a team Agreement.(Part 2)]]></title>
            <link>https://alexandre-claus.medium.com/create-a-team-agreement-part-2-2c58f891f2c4?source=rss-7f62c60a9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c58f891f2c4</guid>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[coaching]]></category>
            <category><![CDATA[team-agreements]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Alexandre Claus]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 15:50:41 GMT</pubDate>
            <atom:updated>2023-12-03T15:50:41.276Z</atom:updated>
            <content:encoded><![CDATA[<p>Creating an Agile team agreement is pivotal for shaping a high-performing team. This guide includes questions to facilitate the process effectively.</p><h4><strong>1. Understanding the Purpose</strong></h4><p><strong>— Why a Team Agreement?</strong><br> * Sets clear expectations.<br> * Enhances communication.<br> * Builds trust and accountability.</p><h4><strong>2. Preparation</strong></h4><p><strong>— Who Should Be Involved?</strong><br> * All team members and, optionally, a facilitator.</p><p><strong>— What Materials are Needed?</strong><br> * Whiteboard or digital collaboration tool, sticky notes or their digital equivalents.</p><h4>3. Facilitating the Meeting</h4><p><strong>—Setting the Stage</strong><br> * Explain the purpose and importance.<br> * Create a safe, open environment for discussion.</p><p><strong>—Brainstorming Session</strong><br> * Encourage each member to list their expectations, concerns, and goals.</p><p><strong>Questions for Consideration:</strong><br> — “What do you need from this team to perform at your best?”<br> — “What are your expectations for communication and feedback?”<br> — “How do you handle conflicts and disagreements?”</p><h4>4. Drafting the Agreement</h4><p><strong>—Key Components</strong><br>* Communication norms, quality standards, conflict resolution methods, work hours, and availability.</p><p><strong>— Creating the Draft</strong><br> * Use clear, simple language.<br> * Ensure it’s realistic and achievable.</p><p><strong>Facilitator Questions:</strong><br> — “How do we want to communicate as a team?”<br> — “What does a successful outcome look like for us?”<br> — “How can we effectively resolve disagreements?”</p><h4><strong>5. Review and Agreement</strong></h4><p><strong>— Group Review</strong><br> * Adjust the draft based on team feedback.</p><p><strong>—Final Agreement</strong><br> * Formalize the document once consensus is reached.<br> * Have all team members acknowledge it.</p><p><strong>Questions for Final Review:</strong><br> — “Does this agreement reflect our collective values and goals?”<br> — “Are there any points that need clarification or adjustment?”</p><h4>6. Implementation and Follow-up</h4><p><strong>—Making It Visible</strong><br>* Display the agreement where the team can regularly see it.</p><p><strong>— Regular Check-ins</strong><br>* Use retrospectives to review the agreement.<br>* Update it as the team evolves.</p><p><strong>Check-in Questions:</strong><br> — “Is our agreement still serving us well?”<br> — “What changes or updates should we consider?”</p><h4>7. Conclusion</h4><p>A team agreement is more than a document; it’s a commitment to shared working standards, fostering a transparent, respectful, and efficient environment.</p><h4>8. Takeaway</h4><p>The team agreement is dynamic, evolving as the team grows. Regular revisits ensure its relevance, driving continuous improvement and sustained high performance. Always ask, “How can our agreement better support our growth and performance?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/401/1*xKK8299BxJ8yiLq5JV40Yg.png" /><figcaption>Team members signing the Team Agreement.</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c58f891f2c4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile team agreement (part 1)]]></title>
            <link>https://alexandre-claus.medium.com/agile-team-agreement-part-1-560fc200156f?source=rss-7f62c60a9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/560fc200156f</guid>
            <category><![CDATA[coaching-skills]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[leadership-development]]></category>
            <dc:creator><![CDATA[Alexandre Claus]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 15:49:11 GMT</pubDate>
            <atom:updated>2023-12-03T15:49:11.586Z</atom:updated>
            <content:encoded><![CDATA[<p>Explaining the purpose and importance of a team agreement, especially in the context of an Agile team, involves highlighting its role in fostering collaboration, clarity, and efficiency. Here’s how you might approach it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/405/1*BH12A1CapXtzN5Qp8u613w.png" /><figcaption>Image representing a team agreement in a professional setting</figcaption></figure><p>1. Clarifying Expectations<br> —Purpose: A team agreement helps to set clear expectations about how team members will work together. It covers aspects like communication, decision-making, and responsibility allocation.<br> — Importance: When expectations are clear, it minimizes misunderstandings and conflicts, leading to a more harmonious and productive team environment.</p><p>2. Enhancing Communication<br> — Purpose: The agreement outlines how and when team members should communicate. This includes meeting etiquette, response times, and preferred communication channels.<br> — Importance: Good communication is the backbone of Agile teamwork. It ensures that information flows smoothly and efficiently, keeping everyone on the same page and enabling quick responses to changes.</p><p>3. Building Trust and Accountability<br> — Purpose: Trust is built when team members adhere to agreed-upon norms and hold each other accountable. The agreement sets the stage for mutual respect and dependability.<br> — Importance: Trust and accountability are crucial for a high-performing team. They foster a safe environment where members feel valued and responsible for the team’s success.</p><p>4. Facilitating Conflict Resolution<br> — Purpose: The agreement should include guidelines for managing disagreements and conflicts, ensuring they are handled constructively.<br> —Importance: Conflicts are inevitable in any team, but how they are handled can make or break team dynamics. Effective conflict resolution strengthens team cohesion and learning.</p><p>5. Aligning Towards Common Goals<br> — Purpose: It helps align the team’s efforts towards common objectives, ensuring everyone understands and commits to shared goals.<br> — Importance: Alignment is key in Agile teams, where adaptability and quick decision-making are vital. A shared understanding of goals keeps the team focused and efficient.</p><p>6. Supporting Agile Principles<br> —Purpose: The agreement embodies Agile principles such as collaboration, customer focus, and responsiveness to change.<br> — Importance: Embracing Agile principles through a team agreement reinforces the methodology’s strengths, leading to better outcomes and more satisfying work experiences.</p><p>7. Adapting to Change<br> — Purpose: Agile teams operate in dynamic environments. The agreement provides a framework for adapting to changes while maintaining team stability.<br> — Importance: The ability to adapt while staying cohesive is a hallmark of successful Agile teams. The agreement supports this by providing a consistent reference point amidst change.</p><p>In conclusion, a team agreement in an Agile context is not just a formality but a foundational tool for creating a strong, cohesive, high-performing team. It serves as a guide for how team members interact, work together, and adapt to challenges, ultimately contributing to the overall success of the team and the projects they undertake.</p><p>I will present how it could be facilitated in a separate post.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=560fc200156f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Focus on common interest.]]></title>
            <link>https://alexandre-claus.medium.com/focus-on-common-interest-2ae60f902e55?source=rss-7f62c60a9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2ae60f902e55</guid>
            <category><![CDATA[coaching-and-consulting]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <dc:creator><![CDATA[Alexandre Claus]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 15:43:48 GMT</pubDate>
            <atom:updated>2023-12-03T15:43:48.837Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Interest-Based Approach focuses on common interests.</h3><p>The “Interest-Based Approach” is often used in negotiation, conflict resolution, and collaborative problem-solving. It focuses on identifying and addressing the underlying interests of all parties involved rather than just their stated positions. This approach fosters mutual understanding and helps find more satisfying and sustainable solutions for everyone involved. Here’s a general outline of how to build and implement an interest-based approach:</p><figure><img alt="Here is an image of an iceberg, showing both the visible part above the water and the larger submerged part below the surface. This illustrates the concept of ‘the tip of the iceberg’." src="https://cdn-images-1.medium.com/max/940/1*qJQN4Tzamlw6BUrgIy3ICw.png" /></figure><p><strong>1. Identify the Interests:</strong></p><p>Distinguish Between Positions and Interests: Positions are what people say they want; interests are the underlying reasons, needs, or concerns that motivate these positions. For example, in a workplace dispute, a position might be “I want a raise,” but the underlying interest could be financial security, recognition, or career advancement.</p><p>Probe Beneath the Surface: Use open-ended questions and active listening to understand the motivations behind stated positions. This involves hearing the words and paying attention to non-verbal cues and emotions.</p><p><strong><em>Typical questions could be:</em></strong></p><p>“What are your main concerns in this situation?”</p><p>“Can you help me understand why this is important to you?”</p><p>“What underlying needs or values drive your position on this matter?”</p><p><strong>2. Effective Communication:</strong></p><p>Active Listening: This is not just about hearing words but fully concentrating, understanding, responding, and remembering what is being said. It’s essential for building trust and understanding.</p><p>Empathy: Show genuine concern and try to understand the situation from the other party’s perspective. This doesn’t mean you agree, but that you acknowledge their feelings and viewpoints.</p><p>Express Your Interests Clearly and Respectfully: Share your interests and concerns in a way that is honest and clear, without being confrontational or aggressive.</p><p><strong><em>Typical questions could be:</em></strong></p><p>“How do you feel about the current situation?”</p><p>“What are we missing in our understanding of your perspective?”</p><p>“Can you explain more about your standpoint?”</p><p><strong>3. Generating Options:</strong></p><p>Brainstorming: Encourage a creative and open environment where all parties can suggest solutions without criticism. The goal is to generate as many options as possible, which can later be refined and evaluated.</p><p>Focus on Mutual Gains: Look for solutions that benefit all parties. It’s not about winning or losing but finding a resolution everyone can accept.</p><p><strong><em>Typical questions could be:</em></strong></p><p>“What possible solutions might work for both of us?”</p><p>“Can we think of alternatives that meet your needs and address mine?”</p><p>“What haven’t we considered yet that might be a viable option?”</p><p><strong>4. Negotiating Fairly:</strong></p><p>Objective Criteria: Use fair standards or precedents to evaluate options. This could include legal standards, industry norms, or ethical guidelines.</p><p>Avoiding Biases: Be aware of and avoid common negotiation biases, like anchoring on a specific number or being influenced by irrelevant factors.</p><p><strong><em>Typical questions could be:</em></strong></p><p>“What objective standards should we consider in evaluating these options?”</p><p>“How can we ensure the solution is fair and balanced for all parties involved?”</p><p>“Are there any precedents or benchmarks we can use as a reference?”</p><p><strong>5. Reaching a Mutual Agreement:</strong></p><p>Consensus Building: Work towards a solution that is acceptable to all parties. It doesn’t have to be perfect, but it should be something everyone can live with.</p><p>Clarify and Document: Clearly outline the agreed terms and document them in a written agreement if appropriate.</p><p><strong><em>Typical questions could be</em></strong><em>:</em></p><p>“Which of these options do you feel most comfortable with?”</p><p>“Can we summarise the key points of our agreement?”</p><p>“What are the specific steps we mutually agree to take following this agreement?”</p><p><strong>6. Implementation and Follow-up:</strong></p><p>Action Plans: Develop clear steps on who will do what and by when. This helps in translating the agreement into action.</p><p>Review and Adapt: Set up times to review how the agreement works and be open to making adjustments as needed.</p><p><strong><em>Typical questions could be:</em></strong></p><p>“What actions will each of us take to implement this agreement?”</p><p>“How and when should we review the progress and effectiveness of this solution?”</p><p>“What adjustments might be needed if circumstances change?”</p><p><strong>7. Relationship Building:</strong></p><p>Build and Maintain Trust: Honesty, consistency, and follow-through are crucial for building and maintaining trust.</p><p>Long-Term Perspective: Even if the immediate issue is resolved, maintaining a good relationship can be valuable for future interactions.</p><p><strong><em>Typical questions could be:</em></strong></p><p>“How can we work together more effectively in the future?”</p><p>“What can we do to maintain and build trust in our relationship?”</p><p>“What lessons have we learned from this process that we can apply moving forward?”</p><p>Using the Interest-Based Approach encourages a more collaborative and less adversarial method of resolving disputes or negotiating agreements. It’s about understanding each other’s needs and working together to find a solution that satisfies them to the greatest extent possible.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2ae60f902e55" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scrum Master, adopt your leadership.]]></title>
            <link>https://alexandre-claus.medium.com/scrum-master-adopt-your-leadership-63730973c232?source=rss-7f62c60a9ee4------2</link>
            <guid isPermaLink="false">https://medium.com/p/63730973c232</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[coach]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[management-and-leadership]]></category>
            <dc:creator><![CDATA[Alexandre Claus]]></dc:creator>
            <pubDate>Sun, 03 Dec 2023 15:39:31 GMT</pubDate>
            <atom:updated>2023-12-03T15:39:31.650Z</atom:updated>
            <content:encoded><![CDATA[<p>“<em>A leader is best when people barely know he exists. When his work is done and his aim is fulfilled, they will say: we did it ourselves</em>.”</p><p>Lao Tzu, an ancient Chinese philosopher</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/396/1*SB57l9o62UMr16euQMGdgw.png" /><figcaption>Abstract illustration representing leadership in an agile environment</figcaption></figure><p>The leadership of a Scrum Master is unique compared to traditional management roles. A Scrum Master uses servant leadership rather than command and control to guide and facilitate.</p><p>The role of the Scrum Master has different facets. For further details, I invite you to refer to the Scrum Guide. Below, you will find a non-exhaustive list of principles and responsibilities:</p><p>• Relay the product owner’s vision of the product</p><p>• Recentre activities and decisions on added value for the customer</p><p>• Animate, support, and protect the team</p><p>• Remove obstacles and create trust</p><p>• Optimise communication</p><p>• Promote the autonomy, responsibility, adaptation, and learning of team members</p><p>• Manage interfaces with other actors in the organisation</p><p>This leadership and availability promote innovation. The Scrum Master influences, stimulates and generates creativity, allowing team members to have ideas and make proposals in a protective framework.</p><p>In short, a Scrum Master’s leadership is less about hierarchical authority and more about encouraging and empowering the team to be effective and autonomous.</p><p>I remember when I had my first leadership role for a small team. During their annual appraisals, I was very anxious about remembering all that had happened during the year. To keep track of everyone’s progress, I used a notepad and made a red mark whenever I thought something was not good enough and a green mark when I thought it was extraordinary.</p><p>That was not the most human way to behave, and fortunately, I have changed since, and I would give direct, fair feedback rather than wait for the appraisal.</p><p>For a Scrum Master looking to self-assess their leadership style, the Tannenbaum and Schmidt Continuum is a fitting and freely available tool. This model helps leaders determine how much autonomy they give their teams and how directive or participative they are in their leadership approach.</p><p>The Tannenbaum and Schmidt Continuum is a model of leadership styles that demonstrates a range of roles a leader can take in decision-making, from authoritarian to democratic. Developed by Robert Tannenbaum and Warren H. Schmidt in 1958, this model proposes that the leadership style is contingent upon various factors, including the manager’s personal background, the qualities of subordinates, and the organisational environment.</p><p>Here is a breakdown of the Continuum:</p><p>1. **Manager Makes the Decision and Announces It**: This is the most autocratic style on the Continuum. The leader makes decisions unilaterally without seeking input from team members.</p><p>2. **Manager “Sells” the Decision**: The leader still makes the decision alone but attempts to gain commitment by persuading team members that the decision is to their advantage.</p><p>3. **Manager Presents Ideas and Invites Questions**: The leader presents a decision or a plan and invites questions and discussion, which helps team members understand the rationale behind the decision.</p><p>4. **Manager presents a Tentative Decision Subject to Change**: Here, the leader still needs to finalise the decision and remains open to suggestions and feedback from the team.</p><p>5. **Manager Presents the Problem, Gets Suggestions, Then Makes the Decision**: The leader outlines the problem, gets input from the team, and then makes the decision based on this feedback.</p><p>6. **Manager Defines Limits; Asks Group to Make Decision**: The leader sets the parameters and boundaries within which the team must operate and leaves the decision-making process up to the team.</p><p>7. **Manager Permits Subordinates to Function within Limits Defined by a Superior**: This is the most democratic style on the Continuum. The leader allows the team to operate autonomously and make decisions within the confines of a broader strategic framework.</p><p>This Continuum shows that leadership style can be fluid and adaptable, and influential leaders can move along this Continuum as per the situation&#39;s needs, the task at hand, and the maturity and capability of their team members. In the context of Agile and Scrum, a Scrum Master might lean towards the more democratic end of the Continuum, promoting team autonomy and self-organisation while also providing guidance and boundaries as needed.</p><p>The Continuum ranges from authoritarian (the manager makes all decisions) to democratic (the team makes decisions within prescribed limits), with varying degrees of delegated freedom. It aligns well with the Scrum Master role, which requires balancing guidance with team autonomy.</p><p>While the Tannenbaum and Schmidt Continuum itself is a conceptual model and does not come with a ready-to-use questionnaire, you can reflect on the following questions to assess where you might fall on the Continuum:</p><ol><li>When a decision is needed, do I tend to make it on my own, or do I seek the team’s input?</li><li>How comfortable am I with allowing the team to make decisions related to their work?</li><li>Do I often find myself telling the team what to do, or do I facilitate discussions that lead to the team coming up with their solutions?</li><li>When the team faces obstacles, is my first instinct to step in and solve the problem, or do I encourage the team to find a resolution?</li><li>In times of high pressure, do I take control or trust the team to perform?</li><li>How do I react when the team makes a decision that I disagree with? Do I intervene, or do I respect their autonomy?</li></ol><p>Reflecting on these questions gives you a sense of where you fall on the Tannenbaum and Schmidt Leadership Continuum.</p><p>For a more structured self-assessment, Agile-specific tools and quizzes are available online to assess leadership style within the context of Agile and Scrum principles. A quick search with terms like “Agile leadership style quiz” or “Scrum Master self-assessment” in your preferred search engine should yield some free options to explore. These tools assess your alignment with Agile values and principles, which is critical for a Scrum Master.</p><p>Remember, the goal of such an assessment is to provide insights into your leadership tendencies and to help you become more adaptable and responsive to the needs of your team and the demands of the Agile environment.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63730973c232" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>