<?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[The Boring Team - Medium]]></title>
        <description><![CDATA[We’re a dedicated team of passionate young people sharing our ideas to the world, including Software Development, UI/UX Design and Business. - Medium]]></description>
        <link>https://medium.com/the-boring-team?source=rss----3f2bed57827d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>The Boring Team - Medium</title>
            <link>https://medium.com/the-boring-team?source=rss----3f2bed57827d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:06:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/the-boring-team" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Respect — Everyone is valuable (Part 5 of 5)]]></title>
            <link>https://medium.com/the-boring-team/respect-everyone-is-valuable-part-5-of-5-874a064b392d?source=rss----3f2bed57827d---4</link>
            <guid isPermaLink="false">https://medium.com/p/874a064b392d</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[scrum-master]]></category>
            <dc:creator><![CDATA[Tepes Alexandru]]></dc:creator>
            <pubDate>Thu, 13 Jan 2022 20:10:29 GMT</pubDate>
            <atom:updated>2022-01-13T20:10:29.317Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jr0V5OnooMCzFHJ1Y8q8PA.png" /></figure><h3>Respect — Everyone is valuable (Part 5 of 5)</h3><p>This is the last article in this series about Scrum Values. For more insights, enter my digital garden and explore more of my knowledge. Everything is open and available for free. The link is at the bottom of the article.</p><p>To read the previous article, click here: <a href="https://medium.com/the-boring-team/commitment-always-do-your-best-part-4-of-5-679ca701d995">Commitment — Always do your best (Part 4 of 5)</a>.</p><h3>How Respect helps the Scrum Process</h3><p>Respect facilitates empiricism and collaborative teamwork.</p><p>By <strong>respecting all opinions and perspectives</strong> that are shared in the team, the Scrum team can ensure that everyone has the opportunity to be heard. When every individual <strong>feels that they have been heard</strong>, it’s easier for them to <strong>support a team decision</strong> even if it’s not their preference.</p><p>By <strong>respecting that people are doing their best</strong>, based on their experience and their current resources, the Scrum team <strong>enables transparency</strong>. It’s okay to change direction once new information has been gathered.</p><p>By respecting that people are motivated <strong>by autonomy, mastery, and purpose</strong>, people will be more eager to engage with one another and the value of <strong>the team becomes far greater than the sum of every individual</strong>.</p><p>By <strong>showing respect </strong>and assuming that people have the best intention, it’s easier to have difficult discussions that <strong>help resolve conflict</strong> and make the team better.</p><h3>How the Scrum Process promotes Respect</h3><p>The entire Scrum Team attends Sprint Planning, Sprint Review, and the Sprint Retrospective. Here everyone has the <strong>chance to speak their mind</strong> and share their perspective.</p><p><strong>The Sprint Backlog is owned by the Developers</strong>. This shows respect to their abilities to create a valuable increment given their current skills. By also <strong>only delivering an increment that meets the Definition of Done</strong>, it promotes respect towards the stakeholders.</p><p><strong>The Scrum Team is cross-functional</strong>, meaning that by collaborating, they have all the necessary skills to deliver a usable product. This promotes respect for everyone’s skills, experience, and ideas, while also promoting learning and growth.</p><p>The focus of the Scrum Master is on the health of the Scrum Team and the effective use of Scrum. Having a role fully dedicated to this promotes <strong>respect towards the people on the team and their capacity to grow</strong>.</p><p>This is the last article in this series, if you want to learn more, explore my digital garden. I will most likely publish more articles about Scrum in the future, but none are planned yet.</p><p>Until then, read another story of mine: <a href="https://theboringteam.com/7-easy-steps-to-know-how-much-you-can-achieve-in-2022-d42bf182a5c8">7 Easy steps to know how much you can achieve in 2022</a>.</p><p><strong>🪴</strong><a href="https://tepesalexandru.github.io/quartz/"><strong>My Digital Garden</strong></a><strong>.</strong></p><p>Țepeș Alexandru, <em>The Boring Team </em>👏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=874a064b392d" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-boring-team/respect-everyone-is-valuable-part-5-of-5-874a064b392d">Respect — Everyone is valuable (Part 5 of 5)</a> was originally published in <a href="https://medium.com/the-boring-team">The Boring Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Commitment — Always do your best (Part 4 of 5)]]></title>
            <link>https://medium.com/the-boring-team/commitment-always-do-your-best-part-4-of-5-679ca701d995?source=rss----3f2bed57827d---4</link>
            <guid isPermaLink="false">https://medium.com/p/679ca701d995</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Tepes Alexandru]]></dc:creator>
            <pubDate>Sun, 09 Jan 2022 10:53:29 GMT</pubDate>
            <atom:updated>2022-01-13T20:15:56.022Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*f-vu1kOhmskrU1kv0gJPLQ.png" /></figure><h3>Commitment — Always do your best (Part 4 of 5)</h3><p>This article is a continuation of the Scrum Values series. To read the previous article, click here: <a href="https://medium.com/the-boring-team/courage-be-brave-every-day-part-3-of-5-88666320542e">Courage — Be brave every day (Part 3 of 5)</a>.</p><p>Before I dive in, it’s important to note that the word “commitment” here <strong>does NOT refer to the promise of delivering a set scope of features by a set date</strong>. This Scrum Value is often misunderstood, and this article will help you have a better understanding of it.</p><h3>How Commitment helps the Scrum Process</h3><p>When each individual member <strong>commits to the success of the entire team</strong>, not just caring about themselves, that creates an environment of trust, collaboration, and high standards.</p><p>By <strong>committing ourselves to continuous improvement</strong>, it becomes much easier to change direction based on new information or empirical data.</p><p>When we <strong>commit to delivering value</strong>, we feel that our work is part of a higher purpose while also sparking our drive to collaborate.</p><p>Commitment is all about <strong>doing our best work</strong>. It’s impossible to predict or control all of the complex scenarios while developing a product, but we can <strong>commit to adjusting our behavior and taking action</strong> based on feedback and new information.</p><p>Also, by fully <strong>committing to doing Scrum in its entirety</strong>, not just picking and choosing what we like about it, we can fully experience the benefits that come with it, such as transparency, inspection, and adaptation.</p><h3>How the Scrum Process promotes Commitment</h3><p>First off, the Scrum framework has 3 accountabilities: The Product Owner, The Developers, and The Scrum Master. Each one of them has a set commitment in their role:</p><ul><li>The Product Owner demonstrates commitment by <strong>making the best possible decisions</strong> to maximize the value of the product being built.</li><li>The Developers demonstrate commitment by <strong>delivering an Increment that meets the Definition of Done</strong> at the end of every Sprint.</li><li>The Scrum Master demonstrates commitment by <strong>upholding the Scrum Framework</strong> and making sure it&#39;s always respected.</li></ul><p>Every Product Backlog Item has a Definition of Done which promotes the <strong>commitment to deliver quality and continuous improvement</strong>.</p><p>The Daily Scrum meeting is the perfect place to show our <strong>commitment to work as a team</strong> and help each other in order to reach the Sprint Goal.</p><p>Both the Product Backlog and the Sprint Backlog enable the <strong>commitment to be transparent</strong>. Everything is out in the open, such as our current progress in the Sprint, and the stakeholder can see at any time what has been completed in the Product Backlog so far.</p><p>The Sprint Retrospective promotes a <strong>commitment to constantly improve as a team</strong>. We sit together and discuss openly what went great, bad, and what can be improved starting from the next Sprint.</p><p>The next article: <a href="https://medium.com/@tepes_alexandru/respect-everyone-is-valuable-part-5-of-5-874a064b392d">Respect — Everyone is valuable (Part 5 of 5)</a>.</p><p>Țepeș Alexandru, <em>The Boring Team </em>👏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=679ca701d995" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-boring-team/commitment-always-do-your-best-part-4-of-5-679ca701d995">Commitment — Always do your best (Part 4 of 5)</a> was originally published in <a href="https://medium.com/the-boring-team">The Boring Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Courage — Be brave every day (Part 3 of 5)]]></title>
            <link>https://medium.com/the-boring-team/courage-be-brave-every-day-part-3-of-5-88666320542e?source=rss----3f2bed57827d---4</link>
            <guid isPermaLink="false">https://medium.com/p/88666320542e</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Tepes Alexandru]]></dc:creator>
            <pubDate>Thu, 06 Jan 2022 20:22:11 GMT</pubDate>
            <atom:updated>2022-01-09T10:52:11.990Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yh5p1-QtyiWL4HgiK2WIMA.png" /></figure><h3>Courage — Be brave every day (Part 3 of 5)</h3><p>This article is a continuation of the Scrum Values series. To read the previous article, click here: <a href="https://medium.com/the-boring-team/openness-letting-go-of-ego-and-accepting-transparency-part-2-of-5-fa718e464edf">Openness — Letting go of ego and accepting transparency (Part 2 of 5)</a></p><h3>How Courage helps the Scrum Process</h3><p>Courage facilitates empiricism and collaborative teamwork.</p><p>It takes courage to <strong>ask for help</strong> when we don’t know something or we’ve been stuck on a task for hours.</p><p>It takes courage to <strong>admit our mistakes</strong> in front of the team. Although it may be hard at first and feel that we’re going to be fired for having done something wrong, it’s really important that everyone on the team is transparent about their decisions.</p><p>It takes courage to <strong>start building something that no one on the team has built before</strong>, not knowing if it’s going to work or not. This could mean using a new framework or library, or even a new programming language.</p><p>Sometimes the team may find that they’ve built something that the customer didn’t actually want. It takes courage to <strong>admit that their assumption was wrong</strong> and that they need to go in a different direction.</p><p>When discussing with other team members you may find that people share a different point of view with you. It takes courage to <strong>share your opinion</strong> even if it’s different from that of everyone else and <strong>engage in productive conflict</strong>.</p><h3>How the Scrum Process promotes Courage</h3><p>Every Scrum Event is built around the idea that <strong>anything is open to change</strong>. This assumption enables courage to propose new ideas and knowing that changing direction is an option. Also, each Sprint has a <strong>fixed duration</strong>. This gives the Scrum Team the <strong>courage to explore</strong> new things, experiment, and gain knowledge.</p><p><strong>The Scrum Team is transparent</strong> about their planned work through both the Sprint Backlog and the Product Backlog. The team is also transparent about their progress by showing the stakeholders their progress at the end of each Sprint. <strong>Transparency takes courage, and transparency helps us build trust.</strong></p><p>At the end of each Sprint, a couple of hours are dedicated towards a <strong>Sprint Retrospective</strong>. Here each team member has a chance to analyze how they’ve worked together as a team and <strong>bring up eventual issues</strong>. It takes courage to <strong>tell someone on the team </strong>that there are things<strong> he could improve</strong>, but it constantly improves the team and helps it reach the next level.</p><p>There are three accountabilities when it comes to the Scrum Team: The Product Owner, The Developers, and The Scrum Master. <strong>Each one of them promotes courage</strong>.</p><p>The Product Owner needs to always make the right decision in order to maximize the value of the product being built, and he must <strong>have the courage to say “no” to features that bring little to no value</strong>.</p><p>The Developers need to maintain a certain quality in their code, to make it easier to build future features and maintain or improve the current ones. They must also display the courage <strong>to say “no” to cutting quality under the pressure of time</strong>.</p><p>The next article: <a href="https://medium.com/@tepes_alexandru/commitment-always-do-your-best-part-4-of-5-679ca701d995">Commitment — Always do your best (Part 4 of 5)</a></p><p>Țepeș Alexandru, <em>The Boring Team </em>👏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88666320542e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-boring-team/courage-be-brave-every-day-part-3-of-5-88666320542e">Courage — Be brave every day (Part 3 of 5)</a> was originally published in <a href="https://medium.com/the-boring-team">The Boring Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Openness — Letting go of ego and accepting transparency (Part 2 of 5)]]></title>
            <link>https://medium.com/the-boring-team/openness-letting-go-of-ego-and-accepting-transparency-part-2-of-5-fa718e464edf?source=rss----3f2bed57827d---4</link>
            <guid isPermaLink="false">https://medium.com/p/fa718e464edf</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Tepes Alexandru]]></dc:creator>
            <pubDate>Thu, 06 Jan 2022 16:36:05 GMT</pubDate>
            <atom:updated>2022-01-09T10:51:53.990Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yFbvvm2brb1WvpJtorKtpw.png" /></figure><h3>Openness — Letting go of ego and accepting transparency (Part 2 of 5)</h3><p>This article is a continuation of the Scrum Values series. To read the first article, click here: <a href="https://medium.com/the-boring-team/focus-the-first-scrum-virtue-you-need-part-1-of-5-f88433e6b5d1">Focus — The first Scrum virtue you need (Part 1 of 5)</a>.</p><h3>How Openness helps the Scrum Process</h3><p>Openness facilitates empiricism and collaborative teamwork.</p><p>Openness is about being able to tell the team that you are struggling with your current task and <strong>need some help</strong>. It allows other team members to <strong>offer help</strong> and <strong>collaborate </strong>together to solve an obstacle.</p><p>Being open allows people to <strong>share their perspectives</strong> on the subject at hand, <strong>feel heard</strong>, and possibly <strong>explore new solutions</strong>. It also allows individuals to get together and <strong>make decisions as a team</strong>.</p><p>Often members inside the team have to make important decisions on how to implement a certain feature or deal with a certain bug. Being open helps team members <strong>admit that their approach was wrong</strong> and that another solution would be better instead. It’s better that everything is out there on the table rather than trying to keep something that doesn’t quite work hidden and let the whole team find out later on.</p><h3>How the Scrum Process promotes Openness</h3><p>In Scrum, every event is timeboxed. This means its duration is known beforehand.</p><p>The Scrum framework puts an upper limit to the duration of a Sprint to one month. This promotes openness to possibly <strong>take another approach</strong> towards a solution and change directions if needed <strong>when new information appears</strong>.</p><p>Each Sprint also has a fixed <strong>Sprint Goal </strong>that provides a shared vision for the team, but the plan to reach the goal is <strong>totally open to changes</strong> based on team decisions and the knowledge of the Developers.</p><p>The <strong>Product Backlog </strong>is public to see by everyone on the team at any time. This demonstrates transparency with the <strong>project stakeholders</strong> about what has currently been completed, what is being planned, what features will be put on hold, and what features will not be included at all.</p><p>Having a <strong>Sprint Review</strong> makes it visible to everyone what has been achieved so far, especially to the project stakeholders and it <strong>allows collaboration</strong> with them and it’s a great moment to receive <strong>constructive feedback</strong>.</p><p>Lastly, having a <strong>Sprint Retrospective</strong> at the end of each iteration allows each team member to express his opinion about what went well and what didn’t. This creates a medium <strong>open to feedback, reflection,</strong> and <strong>improvement</strong>.</p><p>The next article: <a href="https://medium.com/the-boring-team/courage-be-brave-every-day-part-3-of-5-88666320542e">Courage — Be brave every day (Part 3 of 5)</a></p><p>Țepeș Alexandru, <em>The Boring Team </em>👏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fa718e464edf" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-boring-team/openness-letting-go-of-ego-and-accepting-transparency-part-2-of-5-fa718e464edf">Openness — Letting go of ego and accepting transparency (Part 2 of 5)</a> was originally published in <a href="https://medium.com/the-boring-team">The Boring Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Focus — The first Scrum virtue you need (Part 1 of 5)]]></title>
            <link>https://medium.com/the-boring-team/focus-the-first-scrum-virtue-you-need-part-1-of-5-f88433e6b5d1?source=rss----3f2bed57827d---4</link>
            <guid isPermaLink="false">https://medium.com/p/f88433e6b5d1</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Tepes Alexandru]]></dc:creator>
            <pubDate>Thu, 06 Jan 2022 13:54:03 GMT</pubDate>
            <atom:updated>2022-01-09T10:51:21.767Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gmRd7mHWNjdu4Ne4QumlDg.png" /></figure><h3>Focus — The first Scrum virtue you need (Part 1 of 5)</h3><p>I am currently studying to become a <a href="https://www.scrum.org/professional-scrum-master-i-certification">Professional Scrum Master</a> and decided that I’d like to share my learning journey with you through articles. I invite you to follow this journey and learn how to become a Scrum Master as well.</p><p>This will be a 5 part series describing the core values of the Scrum framework, those being:</p><ul><li><strong>Focus</strong></li><li>Openness</li><li>Courage</li><li>Commitment</li><li>Respect</li></ul><h3>How Focus helps the Scrum Process</h3><p>Focus facilitates empiricism and collaborative teamwork</p><p>First off, “<strong>Empiricism” </strong>means working in a fact-based environment. This means that every decision should be based on evidence and experience. Scrum uses an empirical process to identify progress based on what has been done and what still needs to be done, not on imaginary plans and wishes.</p><p>When it comes to the Scrum team, it’s important that everyone has a <strong>product vision</strong>, because this creates focus on the direction that the team needs to go towards and can guide their decisions on a daily basis.</p><p>When <strong>uncertainty </strong>sneaks into the team there isn’t a clear path anymore. The first instinct may be to keep analyzing until more information is discovered, but focus helps the team accept the current uncertain situation and make a small step forward with what they know today.</p><p>When there are <strong>competing priorities</strong>, focus helps the team decide what is the most important thing right now. If there are 100 things to do in a limited amount of time, it’s better to put the best effort into completing 10 things rather than doing 100 things badly.</p><p>When multiple <strong>issues and impediments</strong> appear, focus helps the team to stay calm and determine what to tackle first, and work towards a solution.</p><h3>How the Scrum Process promotes Focus</h3><p>The <strong>Product Backlog</strong> is an ordered list, where the items at the top of the list have the most priority. This helps the team focus on what’s the top priority item at all times.</p><p>The Scrum <strong>events and artifacts</strong> such as the 15-minute Daily Meeting help the team focus by sharing what everyone is working on and possible issues that have arisen. All Scrum events have a defined time beforehand, this creates urgency and helps the team focus on the purpose of the event.</p><p>Lastly, each sprint has a clear <strong>Sprint Goal </strong>and <strong>Done Increment.</strong> This helps focus on what they have achieved so far and in what direction they are headed.</p><p>Next article: <a href="https://medium.com/the-boring-team/openness-letting-go-of-ego-and-accepting-transparency-part-2-of-5-fa718e464edf">Openness — Letting go of ego and accepting transparency (Part 2 of 5)</a></p><p>Țepeș Alexandru, <em>The Boring Team </em>👏</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f88433e6b5d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/the-boring-team/focus-the-first-scrum-virtue-you-need-part-1-of-5-f88433e6b5d1">Focus — The first Scrum virtue you need (Part 1 of 5)</a> was originally published in <a href="https://medium.com/the-boring-team">The Boring Team</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>