<?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 Jody Weir on Medium]]></title>
        <description><![CDATA[Stories by Jody Weir on Medium]]></description>
        <link>https://medium.com/@jodyweir?source=rss-b64cd1daa39b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*txgXWUXOF7u4sz4kydTShA.jpeg</url>
            <title>Stories by Jody Weir on Medium</title>
            <link>https://medium.com/@jodyweir?source=rss-b64cd1daa39b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 02:59:40 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@jodyweir/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[Our Experience with Squad Self-Selection (Spoiler Alert: DO IT!!!!!)]]></title>
            <link>https://medium.com/the-iconic-engineering/our-experience-with-squad-self-selection-spoiler-alert-do-it-f815ee573648?source=rss-b64cd1daa39b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f815ee573648</guid>
            <category><![CDATA[team-self-selection]]></category>
            <category><![CDATA[new-ways-of-working]]></category>
            <category><![CDATA[work-culture]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[squad-self-selection]]></category>
            <dc:creator><![CDATA[Jody Weir]]></dc:creator>
            <pubDate>Thu, 15 Nov 2018 03:30:59 GMT</pubDate>
            <atom:updated>2018-11-18T23:56:30.911Z</atom:updated>
            <content:encoded><![CDATA[<p>We have run Squad Self-Selection for two quarters in a row within ICONIC Tech and it has been wildly successful (99% of our staff either love it, 77%, or like it, 22%). Our process included about 30 people and 5 Squads. We wanted to share our experience in the hopes of inspiring other organisations to try this too.</p><p>We decided to try Squad Self-Selection because we thought it might be a better approach to what we were currently doing which was having managers decide who was on which squad. We hire exceptional people and thought they could best decide what and who they worked with while keeping the interests of the company front of mind.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/615/0*ilY22uEaGw3g1UKO" /></figure><p><em>Immediately After our Squad Self-Selection Process…those are genuine smiles!!</em></p><p><strong>A bit about THE ICONIC and ICONIC Tech</strong></p><p>THE ICONIC is the largest online fashion retailer in Australia and New Zealand. THE ICONIC stands for benchmark-setting experiences (3-hour delivery, access to over 1,000 top brands, market-leading shopping app), for impassioned communities (connecting Australians fashion and sports lovers through digital innovation), and for our love of the newest in fashion from our 1,000+ leading local and international brands.</p><p>Our ICONIC Tech Team is currently 110 people strong. We have 13 Squads that are made up of ~7–11 people with cross-functional skills including Product Owner, Scrum Master, Software Engineer (Front-end, Back-end, App), User Experience Design (UXD), Data Science and Analytics. Our Squads are self-managing and autonomous. We release into production 10–20 times a day. For the past 2 quarters, 5 of our 13 Squads have been experimenting with Squad Self-Selection.</p><p><strong>What is Squad Self-Selection?</strong></p><p>“Squad Self-Selection is a facilitated process of letting people self-organise into small, cross-functional teams. Self-organising teams are groups of motivated individuals who work together toward a share goal and have the ability and authority to take decisions and readily adapt to changing demands.”1</p><p>“Self-Selection honours the principles of trusting people to be responsible adults who can solve complex problems and organise in a way that’s best for the organisation and themselves. We believe that organisations get the best results when they can choose what they work on and who they work with.”2</p><p><strong>Why did we do it?</strong></p><p>Squad Self-Selection is a great fit with our culture at THE ICONIC which is customer obsessed and focused on employee empowerment and continuous learning. We hire the best people and trust and enable them to do great work. With Squad Self-Selection, our people have the power to choose for themselves with the company’s best interests in mind. It’s also efficient and effective. Even the best informed and well-intentioned managers will never be able to be able to choose for an employee as well as the employee could for themselves. And it takes way less time. A bit of prep and a facilitated workshop and it is done and dusted, versus several meetings to gather preferences, make decisions and communicate those decisions back to each individual.</p><p><strong>How did we do it?</strong></p><p>We followed the guidance from Sandy Mamoli and David Moles’ blog posts and book ‘<a href="https://www.amazon.com/Creating-Great-Teams-Self-Selection-People/dp/1680501283">Creating Great Teams…How Self-Selection Lets People Excel</a>’. We also had the courage to give it a go. While we were planning, it was easy to come up with ‘what if’ scenarios that might be tricky to solve…what if no one wants to work on X initiative? What if it doesn’t work and the people aren’t able to work things out together? We decided to plan our approach as best we could, deal with challenges in the moment and stop ‘what if-ing’, since those conversations weren’t moving us forward.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/628/0*cR_lO3J_HSToL09-" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cHlzVdA0CwRlOVND" /></figure><p>Source: <a href="https://nomad8.com/squadify-with-self-selecting-teams/">Squadify with Self-Selecting Teams</a> by Sandy Mamoli and David Mole</p><p><strong>What did we do? (The nitty gritty)</strong></p><p><em>Before the Squad Self-Selection Process</em></p><p>We first determined what we were going to focus on delivering in the next Quarter. This gave us the mission for each Squad. The Product Owners decided ahead of time which Squad they would be on and compiled a 1–3 page document with the following info. This info was shared with the people involved in Squad Self-Selection before the Squad Self-Selection session.</p><p>- What problem we are trying to solve and why</p><p>- Overall project vision (why this?)</p><p>- How will we measure success</p><p>- Scope</p><p>- Overall objective for next quarter</p><p>- Tech stack</p><p>- Squad talent needed (ie. front-end developer, back-end developer, UXD, Data Science)</p><p>For people who were not working on the day of the Squad Self-Selection we got their preferences ahead of time (1st, 2nd and 3rd choice). Those participating remotely attended via video conference (Zoom) and had a person in the room with a computer taking them around and moving their card for them.</p><p>In the room we had the following set up…</p><p>1) Index cards for each person involved in the Squad-Self Selection Process with their name, role and picture.</p><p>2) Sections on the wall for each Squad with the Squad name, mission, list of talent needed, a big blank space for people to put their cards and some room to write the results after each round of self-selection.</p><p>3) Principles and Rules posted on the wall</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8wQD4ctz6-tKDGar" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/0*zUwWR3zHGnRKB0Is" /></figure><p><em>During the Squad Self-Selection Process</em></p><p>- Product Owner Pitch: Each of the Product Owners briefly described their Squad’s mission and highlights from their 1–3 page summaries. (These were given to everyone to read ahead of time as well.)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*bfpYyov4SNveqo1i" /></figure><p><em>During the Squad Self-Selection Process — Product Owner Pitch</em></p><p>- Product Owner Q&amp;A: We had a question and answer session with the Product Owners. The first quarter this was done as one big group and not many questions were asked. The second quarter we split the group into 5 breakout groups and had each group rotate around and meet with each Product Owner for 5 mins. After each group had met with each Product Owner we asked the Product Owners if there were any questions they’d like to share with the whole group. Some people asked if they had to go to a Product Owner Q&amp;A if they weren’t interested in joining that Squad. We said yes since we wanted everyone to get a good understanding of what was happening in the next quarter, even if they weren’t interested in joining a particular squad.</p><p>- Squad Self Selection:</p><p>- Set countdown timer for 4 minutes and asked everyone to put their card on the squad they were interested in joining. People could move their cards during the 4 minutes if they wanted to.</p><p>- After 4 minutes was up, we went through the status of each Squad and wrote down where they had more or fewer people with certain skills than requested.</p><p>- Everyone was asked to take their cards off the wall to start the next round</p><p>- If a Squad had all the skills needed we never took it out since people could still have the option of moving in and out of that squad.</p><p>- Repeat</p><p>Things to note:</p><ul><li>In both quarters it took us 3 or 4 rounds and the squads were set.</li><li>We did have a few people that were hired but hadn’t started yet that we were able to use as wildcards and put them in squads to fill necessary gaps.</li></ul><p>Once the Squads were set we took pictures of everyone in the newly formed squads and announced when people would be moving seats.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/660/0*0bHSMNV8zgfp1WnY" /></figure><p><em>Photos of all the newly formed Squads at the end of the Squad Self-Selection Process</em></p><p><em>After Squad Self-Selection</em></p><p>- There was a noticeable energetic buzz in the air. Research says that a key factor for high performing teams is persistent teams. With Squad Self-Selection this didn’t seem to matter. People were committed to getting their new squad going quickly and were excited be there. There were fewer changes to the Squad missions and team members during the second quarter. But those who didn’t move Squads still actively re-committed and that was equally powerful. After the Squad Self-Selection session, some squads went right into a design sprint while others planned some team building activities.</p><p><strong>What would we do differently?</strong></p><p>There are a few small things we are tweaking, but for the most part the process worked great. One area that we are paying more attention to going forward is what work is still in process at the end of the quarter and which Squad will be responsible for finishing this work in the next quarter, if it’s continuing.</p><p><strong>What did our people say about Squad Self-Selection?</strong></p><p><em>“Only people passionate about the project are involved! It’s contagious!”</em></p><p><em>“People are driven to work on what they like or what they are more curious about.”</em></p><p><em>“Highly motivating and the chance to work with different people.”</em></p><p><em>“I have the ability to review the available work and decide where I can best apply my skills and expertise.</em></p><p><strong>Conclusion….DO IT!!!!</strong></p><p>If you want to foster an environment with engaged and committed employees, we HIGHLY recommend Squad Self-Selection. We already see huge benefits and are continuing to experiment on how to improve the process further. This includes holding Design Sprints to determine our priorities and what we will build. We will aim to put a blog post together on that too…stay tuned :-)</p><p>We want to thank Sandy Mamoli and David Mole for their guidance on how to bring this to life. We hope sharing our experience encourages other organisations to try this approach. If you have any questions, please let us know!</p><p>The ICONIC Tech Team <br>(Manuel Silva, Peter Petrovski, Max Antonov, Will Rogers, Piers Warmers, Scott D’Abrera and Jody Weir)…this was, and continues to be, a team effort after all</p><p>References</p><p><a href="https://www.agilealliance.org/resources/experience-reports/creating-how-self-selection-lets-people-excel/">1. How Self-Selection Lets People Excel</a> (article) by Sandy Mamoli and David Mole</p><p><a href="https://nomad8.com/creating-great-teams-how-self-selection-lets-people-succeed/">2. Creating Great Teams — 5 Questions About Self-Selection</a> (blog post) by Sandy Mamoli</p><p><a href="https://nomad8.com/squadify-with-self-selecting-teams/">3. Squadify with Self-Selecting Teams</a> by Sandy Mamoli and David Mole (blog post</p><p><a href="https://www.amazon.com.au/Creating-Great-Teams-Self-Selection-People-ebook/dp/B019EKWG6M/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1541377805&amp;sr=1-1&amp;keywords=creating+great+teams">4. Creating Great Teams: How Squad Self-Selection Helps People Excel</a> (book) by Sandy Mamoli and David Mole (Available on Amazon.com.au and 24 reviews on <a href="https://www.amazon.com/Creating-Great-Teams-Self-Selection-People/dp/1680501283">Amazon.com</a> with a 4.5 out of 5 star rating)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f815ee573648" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-iconic-engineering/our-experience-with-squad-self-selection-spoiler-alert-do-it-f815ee573648">Our Experience with Squad Self-Selection (Spoiler Alert: DO IT!!!!!)</a> was originally published in <a href="https://medium.com/the-iconic-engineering">THE ICONIC Tech</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dan is a TRUE Agile leader & is getting exceptional results…Do you agree?]]></title>
            <link>https://medium.com/@jodyweir/dan-is-a-true-agile-leader-and-is-getting-exceptional-results-do-you-agree-238f4b0733c5?source=rss-b64cd1daa39b------2</link>
            <guid isPermaLink="false">https://medium.com/p/238f4b0733c5</guid>
            <category><![CDATA[agile-behaviours]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[agile-values]]></category>
            <category><![CDATA[agile-leadership]]></category>
            <category><![CDATA[agile-mindset]]></category>
            <dc:creator><![CDATA[Jody Weir]]></dc:creator>
            <pubDate>Tue, 31 Oct 2017 04:18:23 GMT</pubDate>
            <atom:updated>2017-10-31T04:23:35.868Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>In the first of a series on Agile leaders who live and breathe the Agile philosophy, I have interviewed Dan Gordon at Peoplebank…</strong></p><p>This is not your typical Agile success story and Dan Gordon isn’t your typical Agile leader…which is one of the reasons I decided to share his story with you. Dan and his team embrace Agile and are achieving enviable outcomes, but they aren’t developing software and they utilise very little of the formal Agile methods (think Scrum, Kanban, Lean Startup, Lean etc.). They are, however, role models for leveraging an Agile mindset and behaviours.</p><p>Dan is an IT Recruitment Practice Lead at Peoplebank, guiding a team of 15 IT recruiters — his ‘tribe’. Dan and his team are very successful. They have happy customers. They aim to have a fulfilling and joyful work environment and they are achieving exceptional results.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*pQukJwQJ3GiPqz0OGFM0FQ.jpeg" /></figure><p>Okay, let’s define exceptional results…Dan claims his team is five times more productive than the average recruiting team in Sydney of a similar size as measured by recruiting dollars generated per person. I didn’t fact check this, but even if he’s overstating it a bit, it is still impressive. His retention rates are phenomenal too…per Dan, the average tenure for a recruiter in Sydney is 1.8 years, at Peoplebank it is 3.4 years and on Dan’s team it is 7.5 years!!</p><p>One key ingredient to Dan’s success seems to be his Agile mindset and behaviours. Keep reading to learn why. I hope you enjoy learning about Dan’s story as much as I did.</p><p><strong>Dan’s Agile story….</strong></p><p>Dan sees Agile as a process of doing things better. Always striving to be better as a worthy pursuit. Agile provides him and his team with guidelines on how to go about doing that — nothing more, nothing less.</p><p>In 2012, Dan found himself recruiting for more and more Agile roles and decided to go to a Scrum Master Training course to better understand Agile. He had his Agile ‘light bulb moment’ at the very beginning of the course when the <a href="https://msdn.microsoft.com/en-us/library/dd997578%28v=vs.120%29.aspx?f=255&amp;MSPPError=-2147217396">Agile values</a> were being explained…<em> ‘It instantly made absolute sense. It described something with such clarity that I’d been reflecting on for some time. I want to improve and here is a mindset to help me do it. I felt empowered and elated!’</em></p><p>Dan’s mindset is defined by many as an Agile mindset and he leverages this mindset both inside and outside of work. At a high-level, he describes it as a constant lens of ‘Is this the highest value thing I can be doing in the highest value way?’ What drives Dan to live life in this way? <em>‘I want to be better than the previous version of myself and am surrounded by people at work and at home that share that drive. I want to lie on my death bed and say I gave that a really good shake and made the most of the time I had. I want to live a meaningful and deliberate life.’</em></p><p>As noted in the article by Susan McIntosh <a href="https://www.infoq.com/articles/what-agile-mindset">“So what is an Agile mindset?”</a> , it depends on who you ask. I like Susan’s description which defines an Agile mindset as:</p><p>· Respect (Trust)</p><p>· Collaboration</p><p>· Improvement and learning cycles</p><p>· Pride in ownership</p><p>· Focus on delivering value</p><p>· Ability to adapt to change</p><p>· Transparency (I took the liberty of adding this one to the list)</p><p>This definition aligns well with how Dan describes his and his team’s mindset.</p><p>· <strong>Respect (Trust):</strong> <em>‘Our team is completely flexible in how we work. There is total trust in the team’s commitment and follow through and ability to continuously communicate as required. As a result, it doesn’t matter where people work or when. We agree on what our desired outcomes are and then work in the most fluid and dynamic way we can to deliver on them. I believe that this perpetuates high engagement and high performance as each of us can be highly successful whilst having jobs that are completely molded to the rest of our lives.’</em></p><p>· <strong>Collaboration:</strong> <em>‘We are cross-functional in that there are levels and different roles within the team, but ultimately anyone will step in to help with whatever is needed at the time regardless of the task or the persons ‘rank’ within the team (this includes management putting their hands up for the menial jobs first). Again, there is a common commitment to outstanding results for our clients and doing whatever is necessary to make that happen as a team. We have a shared pursuit of excellence and an understanding that the effort of the whole far exceeds the effort of the parts.’ <br> <br></em>Dan had the wooden partition in his team’s work space removed to create a more open physical environment. Although they have fixed desks, they regularly change where people sit. ‘<em>It was uncomfortable at first, but you become better at connecting more quickly and it accelerates the sense of ‘us’. We want people to be forming and reinforcing stronger relationships with people in the team all the time. This facilitates trust and open communication.</em>’</p><p>· <strong>Improvement and learning cycles:</strong> Dan and his team have regular training sessions where team members teach each other the things they are each particularly good at. As a result, they continually adapt, reflect and refine what they do and how they work together to deliver to their clients. They are committed to constant improvement in line with Peoplebank’s stated culture. There is a discipline around review and adaptation…HR, org-wide and team specific. Employees decide on what their continuous improvement topics should be and then gather employee, customer and market feedback to guide their improvement and learning.</p><p>· <strong>Pride in ownership: ‘</strong>Good enough’ is not good enough for Dan’s team. <em>‘One of the key changes in our team that’s allowed us to deliver high performance is having the right people. We try and bring people into the team who are excellence focused for themselves and share our belief in pursuit of excellence as a group. This has allowed us to drive each other to continually perform better. The people I’m surrounded with every day make me want to be better.’</em></p><p>· <strong>Focus on delivering value:</strong> <em>‘The chemistry, shared understanding of purpose, constant communication and shared understanding of values and high standards allows us to achieve high performance in relation to one another and for our clients.’</em> Peoplebank’s vision is to “Enhance peoples’ lives and help them achieve their dreams”. These values were created based on input from everyone in the company. Every person was asked…Why is what we do valuable? What behaviours will we accept and won’t accept? Peoplebank works hard to reinforce its vision and purpose at all layers of the business. Perhaps this has been a key contributor to Peoplebank’s success, which includes being awarded the Aon Hewitt Best Employers Award for 2012, 2013, 2014 and 2015.</p><p>· <strong>Ability to adapt to change:</strong> <em>‘Our team is interchangeable…people go on holiday or change roles and there is no significant impact to overall team performance. Because we have clear, Agile processes based on common values and goals we can effectively adapt to change. My experience is that this empowers people and drives accountability and autonomy. Through common goals and common behaviours, people get confidence to act without specific direction. We are always moving towards the same point.’</em></p><p>· <strong>Transparency:</strong> Dan’s team runs on a policy of complete openness. They don’t hold any meetings behind closed doors and they encourage each other to say what needs to be said. <em>‘We say whatever we need to in front of each other respectfully and without being defensive, all completely secure in the fact that we always act with care and only with outstanding delivery and constant improvement in mind.’</em></p><p>Like many keen Agilists, Dan’s agile practice expands into his personal life as well. <em>‘If I am going to spend time with my kids, I ask myself…. What’s the most valuable thing I can be doing with them? If we want to play a game, what is the best game? Homework…what’s the best way to concentrate together? I constantly shuffle and reshuffle the product backlog of my life (in my head),…this translates to collaborative meetings with my wife and children. We recently talked with the whole family about what each of us thought was important regarding our upcoming family holiday. My wife and I have a goals (long- and short-term) board at home and we talk about it at least once a month…we don’t want to drift. We want to live and act with purpose.’</em></p><p>So, what do you think…is Dan a true Agile leader?</p><p>Agile leadership is all about mindset, values and behaviours. You can sprinkle in some agile practices and methods, but that’s like adding salt and pepper to a meal. It may enhance the meal, but it isn’t the meal. Salt and pepper for dinner anyone? I think not. We don’t need to get overly prescriptive about what we mean by mindset, values and behaviours. Are leaders embracing a mindset, values and behaviours that include the attributes below? If so, game on people!!</p><p>· Respect (Trust)</p><p>· Collaboration</p><p>· Improvement and learning cycles</p><p>· Pride in ownership</p><p>· Focus on delivering value</p><p>· Ability to adapt to change</p><p>· Transparency</p><p>The leader is the limit when it comes to Agile. High-performing Agile teams need to be supported by a leader who embraces agility and actively displays an agile mindset and agile behaviours. I see this in Dan and applaud him. Hats off to you Dan!</p><p>Do you know other Agile leaders like Dan? If so, I’d love to hear their stories. We need to shine the light on these exemplary leaders and learn from them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*1SDqBdLEI6l-tea9EqH1rQ.jpeg" /></figure><p>(Bonus Feature!!…Or perhaps consider this a virtual party favour for you 😊 This quote was on the wall in Peoplebank’s offices. It’s a great quote and another artifact that I believe helps to describe an Agile mindset.)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=238f4b0733c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>