<?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[Agile Perpsectives - Medium]]></title>
        <description><![CDATA[Agile Projects - Medium]]></description>
        <link>https://medium.com/agilestories?source=rss----17c604ecfa4---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Agile Perpsectives - Medium</title>
            <link>https://medium.com/agilestories?source=rss----17c604ecfa4---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 05:10:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/agilestories" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Top 6 secrets to embracing agility in your teams]]></title>
            <link>https://medium.com/agilestories/agility-in-teams-not-a-mythical-folklore-7917fff310c0?source=rss----17c604ecfa4---4</link>
            <guid isPermaLink="false">https://medium.com/p/7917fff310c0</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[team-collaboration]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Sriram Jaikumar]]></dc:creator>
            <pubDate>Thu, 22 Mar 2018 21:36:16 GMT</pubDate>
            <atom:updated>2018-03-26T05:50:10.383Z</atom:updated>
            <content:encoded><![CDATA[<h3>Agility in Teams: Not a mythical folklore</h3><p><em>by </em><a href="https://medium.com/u/3cd64bb4a2ac"><em>Sriram Jaikumar</em></a> <em>and </em><a href="https://medium.com/u/d5ef1375b415"><em>Rohan Sharma</em></a></p><p>It’s our strong belief that enabling people to function autonomously can tremendously help in building great teams and achieving excellence in software.</p><p>We’re passionate about helping great teams get better, whilst building high-quality software that delights customers. All of this comes from our experiences and combines best practices observed from the eyes of a Scrum Master, Product Owner, Product Manager for delivering B2C and B2B products (sometimes for <strong>millions</strong> of end-users).</p><p>In this article we share suggestions, examples, challenges &amp; tips toward helping embrace agility in your team.</p><p><strong>A quick glance at what’s ahead:</strong></p><ol><li><strong>Getting ready for lift-off — How to kick-start the journey</strong></li><li><strong>Let’s speak <em>Customer!</em></strong></li><li><strong>Squeezing the accelerator on team collaboration</strong></li><li><strong>Shaping mindsets while moving from Traditional to Agile is, well, pottery!</strong></li><li><strong>Moving on is hard (waterfall to agile) — Please don’t get too stuck on velocity</strong></li><li><strong>Allow slacking</strong></li></ol><h3><strong>1. Getting ready for lift-off</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QgGTs5MIMWc6CaswQDjftQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/yN4O7XwWoyY?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rawpixel.com</a> on <a href="https://unsplash.com/search/photos/software-development-team?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Building a cohesive team starts with sharing the product vision and working with the team to crowdfund rules of engagement. As a Scrum Master, arrange an informal catch up with the team first thing when you start a new project.</p><p>To make best use of the activities described below, we encourage you to:</p><ul><li>Let team members know which activities are on agenda and if any preparation is needed</li><li>Pass out sticky notes to everyone for the sessions — you can consolidate them later for building team profiles (Jude likes to begin at 11am, dedicated focus time b/w 3pm-5pm …); maybe also add a picture of each member next to their preferences?</li><li>Publish it later either on a team collaboration platform or on a physical wall.</li></ul><blockquote>You’ll notice that after a few references this becomes embedded in the subconscious — voila, inception complete.</blockquote><p><strong>Let’s begin!</strong></p><p><strong>A) Break the Ice</strong></p><p>If this is the first time you’re meeting as a team, ensure everyone’s at ease.</p><p>Some tips here:</p><ol><li>Give away coffee/tea</li><li>A short personalized note welcoming each team member aboard</li><li>Have everyone share their name</li><li><strong><em>Collectively come up with a name your team</em></strong> — Ask for ideas and do a poll. Team name can be based on a movie, a character, a hero, a God or anything everyone finds cool. The goal is to instill a sense of belonging that can later translate to pride with every incremental success.</li></ol><p><strong>B) Encouraging thy comrades to share their individual ‘work preference’</strong></p><p>This is key to helping each individual understand how others prefer to work, and collaborate better.</p><p>Be open and go first to break the ice if you must. Once you’re done with this exercise you’ll immediately notice a positive sense of cohesion in the team and also go away knowing your teammates so much more so quickly.</p><p>A simple way to help and encourage everyone speak out is to talk about things like:</p><ul><li><strong>When do I start/end my day?</strong></li><li><strong>What’s your personal learning goal from the project?</strong><br><em>e.g. Learn a new technology and contribute back to the larger community on observed challenges</em></li><li><strong>Is there a time in the day I like to be completely focused for more productivity?</strong><br><em>e.g. 2pm to 4pm is when I put my headphones on and go into my DND mode. But am still available to help is someone absolutely needs it!</em></li><li><strong>Are there any personal restrictions that I want my team to know to help me be at my best?<br></strong><em>e.g. I have a regular doctor’s appointment on Mondays, so I may not be able to attend meetings in the first half, OR I need to be away for prayer at xx:xx &amp; xx:xx hrs every day</em></li><li><strong>What is the best mode to reach out to me at work based on urgency?</strong><br><em>e.g. email if my response can wait for some hours, phone if urgent…</em></li></ul><p><strong>C)</strong> <strong>Create alignment on Scrum practices</strong></p><p>Discuss schedules for daily stand-up, backlog refinement sessions, retrospectives, sprint duration, sprint planning. Also acknowledge any personal circumstances of squaddies(team members) derived from the team norming exercise.</p><p>You could also introduce an “ice-cream meter”: An ice- cream meter is a fun way to incentivize people to attend the Daily Stand Up meetings. Any person who does not attend the daily stand-up more than 2 times in a given week is tasked with taking the entire team out for ice-cream. In our experience this practice enforces norms that the team have established and also adds fun and collaboration!</p><p><strong>D) Show support to fail early, experiment and lending a helping hand to each other </strong>— A plan is a map, not the terrain and you will see some challenges and failures along the way. Software development projects usually span a few months during which means teams spend a large portion of their lives together (hopefully co-located and building code right :)</p><p>By removing the first (mental) impediment of meeting failure, we can help teams focus on</p><ul><li>Sharpening their skills</li><li>Helping fellow squaddies for conducting experiments and sharing learnings</li><li>Creating a sense of warmth and belonging within the team</li></ul><blockquote>In one of our projects we really emphasized this and saw some early results where folks, whilst trying to solve library limitations for own features, also contributed their solutions back into GitHub to help the global community</blockquote><p><strong>E) The 3Ws of effectively sharing a Product Vision and Strategy — W</strong>hy, <strong>W</strong>hat, <strong>W</strong>hom</p><blockquote><em>As a Product Owner,</em></blockquote><blockquote><em>I want to lay out the problem our product fixes and for whom</em></blockquote><blockquote><em>So that my team(s) see the bigger picture from day-1</em></blockquote><p>Yes, you need to share the big picture so your team knows why they’re there. Some tips on making your product vision and strategy coherent:</p><ol><li>Simplify the problem statement and “end-user delight” that the product achieves</li><li>Explain how our product will touch and enhance people’s lives — people are more connected to the goal if they can empathize with the end-user (keep user personas handy for this)</li><li>Use the “competitive landscape” to illustrate who else is in the game — our key contenders, how your company/client benefits from the product</li><li>Also, an effective way to reinforce why we’re doing what we’re doing is to use a strategically located large wall space to nicely articulate the product vision and strategy — it’s a subtle reminder to the subconscious every time some crosses it</li></ol><h3><strong>2. Let’s speak <em>Customer</em>!</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EUFBLHuz7ahYs8EM_TbW_Q.jpeg" /><figcaption>unsplash.com</figcaption></figure><p>It’s common for development teams to never or seldom interact with end-users, usually because it’s the marketing, sales, customer support or design teams that engage end-users. Filling in this void and bringing your team closer to user-experiences helps them connect more with product vision and customers. Here’s how you can go about this…</p><p><strong>A) Give the squaddies first-hand customer experiences</strong></p><p>If possible, try to accommodate a few willing team members to attend end-user testing sessions. They’ll take back and share experiences with others on the team — think of this as bees engaging in cross-pollination, but with experiences/ideas.</p><p>This builds an extremely outside in perspective of the product and is a source of valuable feedback and serves as a validator of the product vision.</p><p><strong>B) Feed the insights back passively</strong></p><p>You can share pictures/videos of end-users playing around with a prototype or take some user feedback on sticky-notes and put it up near the team area</p><p><strong>C) Arrange a “meet the team” with customers</strong></p><p>If the team members can’t go out and meet end-users, bring the users to your team. Let the team know in advance and set some ground rules of engagement (e.g. not disclosing any in-development features, refraining from promising timelines for feature delivery…). This meet-up should ideally be facilitated by the product owner and scrum master so they can intervene should a situation arise where the team feels obliged to respond on ETA.</p><h3><strong><em>3. Squeezing the accelerator on team collaboration</em></strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2dTPj27x9WXwh7Nua6xIoA.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/yN4O7XwWoyY?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">rawpixel.com</a> on <a href="https://unsplash.com/search/photos/software-development-team?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p><strong><em>A) </em>Crowd<em>-refine</em> your backlog</strong></p><p>Get together with your team and let ’em hear your story (aka backlog refinement sessions) -&gt; more satiating sprint planning sessions</p><p>Backlog Refinement sessions are extremely engaging and powerful sessions and a must do before going into sprint planning sessions. We believe that every member in the team should contribute towards the acceptance criteria of a user story. This fosters a collective understanding and helps your team build confidence before proceeding to developing them. QA team members have an extremely important role to play in this process. They can pair up with every developer and help add additional acceptance criterias to proactively solve for potential defects.</p><p><strong>B) Introducing “Fancy check-outs”</strong></p><p>Someone once suggested having a daily “check-out meeting” with our dev team every evening, the agenda for which was similar to the daily-stand up. However, the goal was to make the scrum master and PO keep a close tab on progress so that “prescribed velocity targets” could be met. It seemed like a terrible idea but we gave it a try in the spirit of experimentation.</p><blockquote><em>To our surprise it was TRANSFORMATIONAL!</em></blockquote><p>We’ll talk about how it worked out, but first, +50,000 Agile Points to you if you thought this meeting to be extremely taxing for the team. This is purely because:</p><ul><li>Our dev team loved tinkering with code/ideas over having multiple meetings in a day</li><li>There was a mandate to attend this meeting in-person so some folks would have to stay back later than usual</li><li>Nobody, looked forward to it :-(</li></ul><p>A few days in and this meeting started adding toxicity to our team dynamics. And that’s when we thought of making it “fancy”.</p><p>Here’s how we made the prescribed check-out meeting, well, <em>fancy</em>:</p><p>1. Started taking the team out every day — a restaurant/local pub/cafe that worked for everyone</p><p>2. Eliminated the ‘agenda’ bit completely</p><p>3. Celebrated achievements from the day/week, played some games, chatted and got to know each other better</p><p>4. <strong>That’s it.</strong></p><p><em>Sustaining this became a tad expensive on a daily basis so we slowly tapered it down to alternate days, and then weekly.</em></p><p><strong>Impact:</strong></p><ol><li>We successfully eliminated a practice that was clearly detrimental to the team’s health and performance</li><li>Increased collaboration between folks outside work premises</li><li>Helped bring down communication barriers owing to cultural differences within the team. As a result everyone got along better and folks began sharing ideas or concerns more freely</li><li>Reiterated and encouraged that experimenting and failing is OK (and healthy), as long as we’re learning and continuously improving</li><li>Word spread about this across other squads/teams and the practice got widespread adoption</li><li>The bond between team members felt stronger with each “fancy check out”</li></ol><p><strong>The take away from all this:<br></strong>Take the team out once in a while, and as often as possible. Having more fun with the team only makes it <em>better</em>.</p><h3><strong>4. Shaping mindsets while moving from Traditional to Agile is, well, pottery!</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fa-hQF_pAqyQ8EKaV3dS4g.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/znw9Xs5I9ro?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Jared Sluyter</a> on <a href="https://unsplash.com/search/photos/-pottery?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>There’s a popular term in the cryptocurrency world called F.U.D., or Fear Uncertainty Doubt. When FUD creeps in, many holy investors begin mass selling of their holdings, resulting in a crash. In organizations that are moving from traditional software development to Agile, the expectation often can self-set for the project to be delivered much quicker. It’s very common and we’ve come up with a few ways to help everyone calm down, and HODL your faith in Agile.</p><p>The task here is to go top-down and help key stakeholders understand how Agile helps:</p><ol><li>Deliver real value to end-user by delivering features and experiences in quick short feature bursts <strong>vs</strong> long releases in traditional approach e.g. 2–4 weeks vs months</li><li>This in turn enables you to get feedback, with which you can either re-orient and test another idea</li><li>Therefore you do not need to wait for months before knowing if your solution is really needed</li></ol><p>In such situations it is also natural for businesses/stakeholders to take key concepts from Agile and attempt to apply them for finding control in the project — some symptoms to look out for:</p><ul><li>“Velocity targets” being passed on</li><li>Frequent progress meetings</li><li>A drop in trust between departments/teams</li><li>Demotivation/burn-out in teams</li></ul><p>As a scrum master or agile coach, if you see this happen you need to quickly step in to help everyone calm down and re-establish the basics.</p><p>Now since there’s always a business driven push to “churn out more stuff in less time — you’re agile for god’s sake”, this problem is a wee bit tricky to solve.</p><p>Our tips…</p><p><strong>A) Assert value realized by delivering working software</strong></p><p>Definition of progress can be greatly misunderstood if how Agile helps is unclear. The expectation can be to see the product get magically developed and delivered within a very short span of time because the teams are adhering to Agile.</p><p>Help stakeholders understand what Agile aims to accomplish and set expectations right to avoid undue heat from reaching the development teams. Assuming DevOps has been established and teams are pushing releases into production, use this to show how Agile drastically brings down time-to-market. Also emphasize on prioritized delivery of incremental feature updates for quick feedback. All of this would have been a dream in traditional models.</p><p><strong>B) Correlate numbers on diminishing quality with long work hours</strong></p><p>Examples from real world software development projects show how such efforts only lead to rework (owing to bad quality code) and hence cost more money and time</p><p><strong>C) Highlight the problems with excessive context switching</strong></p><p>This happens with trying to deliver more and more in the same period of time. Context switches destroys developer productivity and hence kills efficiency. But why is this hard? This is because humans cannot quickly retrace their steps on a dropped task and catching up takes loads of brain-cell mining. Us beings have an extremely context dependent memory and only by returning to how the memory was made are we able to recall it.</p><h3><strong>5. Moving on is hard (waterfall to agile) </strong>—Please don’t get <em>too</em> stuck on velocity</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*tAAi7UaSi1d0dOwR-6LxpQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/iRnUeA04kUY?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">toine Garnier</a> on <a href="https://unsplash.com/search/photos/speed?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>What we have learned is that velocity should be used as a tool:</p><ul><li>To gauge how process improvements owing to Agile practices are helping the team go faster — <em>are we working on continuously identifying and executing “accelerator tasks”?</em></li><li>To equip the team understand how much complexity of work can be accomplished within a team</li><li>Help stakeholders get a sense of when a new team needs to be brought up</li></ul><p>However, it could end up being a metric in order to have the Product Owner promise long term delivery of features based on it to stakeholders and customers during sprint review. Using velocity outside of the scrum can be dangerous for 3 reasons</p><p><strong>A) Using velocity to evaluate different teams working on a single product</strong></p><p>If you’ve seen multiple teams working to build a single product, their velocities can easily be very different despite same team composition. And this does not necessarily imply that one/some teams are less productive. The measure of progress is not just working software but working software which delivers real value.</p><p><strong>B) Avoid turning velocity as a metric into target</strong></p><p>While measuring something if the thinking is to define it as a target it ceases to be a useful metric. Velocity only tells you how much complexity the team can realistically deliver each sprint period so you can tell which features to prioritize or when feature(s) make it into users’ hands.</p><p><strong>C) Affinity to use velocity for evaluating people</strong></p><p>When you set up a metric and tell people that you will be evaluated against it, they will do whatever is required to reach that goal ,however damaging it may be to other areas of work. This tends to manifest itself in terms of bad code quality, build up for technical debt and estimating in a way which results in the velocity graph always having a positive trajectory</p><p>A very interesting phenomenon we’ve observed is the trap that stakeholders can fall into while attempting to correlate a <strong>team’s velocity</strong> with <strong>number of hours</strong>, and then determining the time needed to complete remaining features.` It’s an art and science that perplexes us still given it yields astoundingly incorrect results every time. Also a really negative side-effect of this activity is something called <strong>“prescribed target velocity” </strong><em>e.g. At least 40 points need to be burned to keep an avg velocity of 28 points</em></p><p>Sounds like deja vu?<em> </em>We’ve experienced this a couple of times after which everything agile suggests goes down the drain. We recommend getting help from a seasoned Agile coach if you see this happening.</p><p><strong>Side-effects of a velocity prescriptions:</strong></p><p>Teams will work extra long hours to meet “prescribed target velocity”. However, this comes with a few side-effects:</p><p>- Cutting corners w.r.t. code quality in order to rush features in</p><p>- Folks refraining from considering edge cases and the list continues</p><p>- Less thorough or skipped peer reviews</p><p>- Manual testing gets rushed</p><p>…the list goes on like Godzilla wreaking havoc in a city and nothing in sight that can help.</p><blockquote>An even worse a side-effect if the velocity isn’t met is if the team members begin over-estimating story size so that the next sprint doesn’t burn them out. We’ve seen this happening multiple times in such scenarios and with all this, the point of relative sizing to assess feature complexity just goes into the bin we find ourselves being neither waterfall nor agile.</blockquote><h3><strong>6. Allow slacking</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SFz3OFBUlvHfHPFcUHaxRQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/photos/oWt--QQVNr4?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">paul morris</a> on <a href="https://unsplash.com/search/photos/creativity-people?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Unsplash</a></figcaption></figure><p>Everybody likes to slack off once a while — <strong>and it’s OK</strong>, even healthy some studies suggest. We encourage you to avoid being the warden who seeks slackers and punishes them - instead help them rejuvenate. The goal is to let your team-mates switch context from work to replenish their “creativity quotient”.</p><p><em>Maybe take your team out for a quick coffee/snack, and slack together?!?</em></p><p><strong>You can use times like these to:</strong></p><p>1. Spark discussions around ideas someone has recently suggested in the team</p><p>2. Sharing a happy customer’s review and congratulate your team</p><p>3. Reiterating how fixing a bug takes much much longer if not done soon — and accumulating a debt in bugs bites the team later</p><blockquote>It’s also important to acknowledge and reward your team when you see them going an extra mile or brew some innovation. <strong><em>“</em></strong><em>Fancy check-outs” are a proven way to give away +5000 Team Happiness Points :)</em></blockquote><h3>So, a quick recap:</h3><p>1. Build and invest in relationships before starting to build your product</p><p>2. Form consensus on scrum practices and help new teams understand the “why” of Agile</p><p>3. Show support to experiment frequently and learn. Practice what you preach and set an example, and don’t be embarrassed of failing!</p><p>4. Remember to share the “The 3Ws of effectively sharing a Product Vision and Strategy — Why, What, Whom”</p><p>5. Crowd-refine your backlog as often as possible in every sprint. Use the wisdom of your team to build a concept even better as a product.</p><p>6. Strive to help your team experience Customer Experiences and feedback</p><p>7. Have fun with your teams, always. And be fancy about it ;)</p><p>8. Transform mindsets when helping organizations/teams moving from waterfall to agile. Turn wardens into mentors and supporters</p><p>9. Don’t equate velocity and time, ever.</p><p>10. Let your team relax — it will boost their creativity and productivity.</p><p><strong><em>Thank you for your time, we hope you liked reading this article as much as we loved curating it!</em></strong></p><p><strong><em>Please feel free to leave comments for feedback or thoughts.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7917fff310c0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/agilestories/agility-in-teams-not-a-mythical-folklore-7917fff310c0">The Top 6 secrets to embracing agility in your teams</a> was originally published in <a href="https://medium.com/agilestories">Agile Perpsectives</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>