<?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 Bartosz Mazurek on Medium]]></title>
        <description><![CDATA[Stories by Bartosz Mazurek on Medium]]></description>
        <link>https://medium.com/@bartoszmazurek?source=rss-639e09599c2f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WGbQVEgbzFc9-FbWB7splA.jpeg</url>
            <title>Stories by Bartosz Mazurek on Medium</title>
            <link>https://medium.com/@bartoszmazurek?source=rss-639e09599c2f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:04:59 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bartoszmazurek/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[[1 min thought] The vaguest thing ever.]]></title>
            <link>https://medium.com/@bartoszmazurek/1-min-thought-the-vaguest-thing-ever-e7bf187a0d83?source=rss-639e09599c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/e7bf187a0d83</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Bartosz Mazurek]]></dc:creator>
            <pubDate>Fri, 05 Oct 2018 06:26:11 GMT</pubDate>
            <atom:updated>2018-10-05T06:26:11.345Z</atom:updated>
            <content:encoded><![CDATA[<h3>[1 min thought] The vaguest thing ever. Story points, and why it’s crucial to have a common understanding across the team.</h3><p>Story points (aka Potato points, Avocado points) are one of the vaguest things in Agile product delivery. They can be super useful, but can also bring a lot of confusion into the team and the company itself (across all levels). On one hand, we can use a derivative of SP — Velocity, to predict delivery and plan milestones. On the other hand, it can be useful as an indicator of the health of the delivery process which might prompt some process improvements.</p><p>The missing part of this tool (Story Points) is a common understanding of it. If you put a number of people in a room, most probably each or person will tell you a different definition of SP. You will probably hear all sorts of different things like effort, risk, dependency, conversion to absolute hours (arrr!!) and so on. The thing is that most of answers can seem to make sense, but also they will likely have very different real world meanings.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F3oD3YrUgucpmkZr5a8%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3oD3YrUgucpmkZr5a8%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F3oD3YrUgucpmkZr5a8%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="432" frameborder="0" scrolling="no"><a href="https://medium.com/media/7100dd3e4669726a446d58f1feeeb535/href">https://medium.com/media/7100dd3e4669726a446d58f1feeeb535/href</a></iframe><p>To avoid this situation, with the teams I work with, we perform an exercise at the beginning of the journey to make sure that we are talking the same language when it comes to estimating something.</p><p>Usually what we do is a discussion to align and have one shared understanding.</p><p>Before the discussion I like to do a silent brainstorming to think about all possible understandings or definitions of SP to be able to explain the impact of going with a particular one.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/767/1*f__twGrJ-sfi8X2-i0cWnw.png" /></figure><p>During the meeting we have a retro style alignment where each person presents his/her point of view. This this is the time when the main discussion is happening. At this stage we have a proper brainstorming, all concerns are raised and are addressed to a certain degree.</p><p>In the final stage, all team members need to agree on common story points measures. Here some people need to make some compromises, but overall it usually tends to go quite smooth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zfLab0rXUaNffkDbmCj19w.jpeg" /></figure><p>Finally, the result should be made visible and available for each of the team members. Next time, if anyone asks “ok, why this kind of thing is estimated by e.x. 13 SP?”, we can easily say — “<em>because we all agreed on that</em>”.</p><p>To have a disclaimer, this is not a “one time document”. It can (and should) be redefined from time to time. Also estimation by comparison, ruler style, estimation poker are valid because they bring decisions into our team. But the key takeaway of this short thought is:</p><h3>Do not assume that something is so obvious that having a common understanding of a things is easy.</h3><p>Make sure that your team is talking the same language about the same thing. The rest is a matter of time and proper dynamics.</p><p>Ps. Special THX for Neil and my Two teams which gave me this lesson ❤</p><p>PS. what we did with one of team was that after this meeting we went one more time trough product backlog and we did re-estimation of all relevant PBI (Product backlog items). That’s was very nice exercise to accomplish above activity.</p><p>Did you enjoy this post? If yes, please share it or/and give me a ❤. <strong>Every view, read, and recommendation is for me great praise and motivation.</strong></p><p>Do you want to read more about some other interesting stuff related to Agile, management? Look <a href="https://medium.com/@bartoszmazurek">Medium</a><strong> </strong>or <a href="https://www.linkedin.com/today/author/bartoszmazurek">LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e7bf187a0d83" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[1 min thought] Bottom of backlog refinement sessions]]></title>
            <link>https://medium.com/@bartoszmazurek/1-min-thought-bottom-of-backlog-refinement-sessions-ec4a5c6902db?source=rss-639e09599c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec4a5c6902db</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[management]]></category>
            <dc:creator><![CDATA[Bartosz Mazurek]]></dc:creator>
            <pubDate>Wed, 27 Jun 2018 06:44:18 GMT</pubDate>
            <atom:updated>2018-06-27T06:44:18.877Z</atom:updated>
            <content:encoded><![CDATA[<p>I have the pleasure of working with a distributed Scrum Team. New team, new setup, sort of a new project. We are currently forming our Agile delivery process and on one of the meetings, during backlog refinement to be precise, I got a revelation.</p><h3>Grooming basic things:</h3><p>As you all know, the main purpose of the backlog refinement meeting (aka grooming meeting) is to get your upcoming PBI (Product Backlog Item) known better (including DoR (Definition of Ready), story points, potential risk, upcoming priority and so on). Basically the objective is to get things prepared for the next planning session.</p><h3>Beyond that :</h3><p>So, about that revelation… Suddenly, out of the nowhere, I realized that this kind of meeting is more than preparation. It actually serves the following purposes:</p><ul><li><strong>Builds awareness</strong> — inside the team, on what they are going to work on and how important it is for the company. On this meeting, the PO should explain the potential impact and provide the business context of the task and how it supports the company goals.</li><li><strong>Encourages collaboration along with cooperation</strong> — this is a very important point, especially at the beginning of the Agile journey. Long story short, the team should strive to define a goal which is meaningful to everyone instead of just accomplishing a list of tickets.</li><li><strong>Builds a common understanding</strong> — Each of the team members who will be focused enough on the meeting will have context of the other’s work. It’s important because at any point of time, any team member can help and know why (It’s a bit extrapolation but I think that you get my point). By knowing other colleagues’ tasks and context, it’s easier to project a common goal.</li><li><strong>It fosters self-organization </strong>— Referring to the above points, it is clear that all these drive self-organization. Why ? Because we share understanding across the team, we are aware of things; why, how, and what needs to be done. In case of a quick priority change or free time, a team member can easy help the other person to move forward with their things (one more time, because know why, how, and what needs to be done).</li><li><strong>Gives perspective — </strong>So called, the knowledge of the crowd. Each team is made with a variety of guys with different skills, UX, UI, E2E, MP3, ACDC, PO, 2PAC and so on… each of these skill sets and mindsets can bring on the table different points of view and produce a lot of “aha” moments…</li><li><strong>Sets the event horizon — </strong>Gives a feeling of safety, we know what we (think, forecast) are going to focus on in the upcoming sprint(s). Of course priority may change from sprint to sprint, but probably next week we will have the same meeting when we will go through the same process.</li></ul><p>And all of that in the one meeting.</p><p>I wanted to share this to build awareness what is behind the process and show how what we might sometimes see as repetitive, endless, meetings, can at the end of the day, have a great impact on team dynamics.</p><p><strong>More quick thoughts ?</strong></p><ul><li><a href="https://medium.com/@bartoszmazurek/1-min-thought-product-owner-the-root-of-the-wealthy-process-b871b1c64cad">[1 min thought] Product Owner — the root of the wealthy process.</a></li><li><a href="https://www.linkedin.com/pulse/1-min-thought-scrum-masters-avoid-proxy-bartosz-mazurek/">[1 min thought] Scrum Master(s), avoid to be a proxy.</a></li><li><a href="https://www.linkedin.com/pulse/1-min-thought-quality-just-sonar-bartosz-mazurek/">[1 min thought] quality is not just the % in Sonar</a></li></ul><p>Did you enjoy this post? If yes, please share it or/and give me a ❤. <strong>Every view, read, and recommendation is for me great praise and motivation.</strong></p><p>Do you want to read more about some other interesting stuff related to Agile, management? Look<a href="https://medium.com/@bartoszmazurek"> Medium</a><strong> </strong>or<a href="https://www.linkedin.com/today/author/bartoszmazurek"> LinkedIn</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec4a5c6902db" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Sprint Goal doesn’t have to be equal to the sum of tickets — and it’s actually good if it isn’t.]]></title>
            <link>https://medium.com/@bartoszmazurek/the-sprint-goal-doesnt-have-to-be-equal-to-the-sum-of-tickets-and-it-s-actually-good-if-it-78765185000d?source=rss-639e09599c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/78765185000d</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Bartosz Mazurek]]></dc:creator>
            <pubDate>Mon, 04 Jun 2018 07:34:04 GMT</pubDate>
            <atom:updated>2018-06-04T07:34:12.973Z</atom:updated>
            <content:encoded><![CDATA[<p>How many times you heard the classic — “so you as a team COMMIT to deliver those set of stories”; and suddenly out of nowhere, this sentence became unspeakably horrifying.</p><p><strong>So what is a Sprint Goal?</strong></p><p>In my opinion, a Sprint Goal has to cover all the roles of a Scrum Team. The whole team has to agree on it, make it explicit, and understandable for everyone.</p><ul><li><strong>Product owner</strong> needs to make sure that this sentence will maximize the potential value of the sprint.</li><li><strong>The development team</strong> has enough flexibility in achieving it, and clearly, understands what needs to be done. Can focus on the most important thing and in case of the rush, swarm on the most important feature. It’s also a catalyst for collaboration (inside of cooperation). The team have a purpose to rally around and it makes it easier to not miss customer value.</li><li><strong>Scrum Master </strong>can focus on the most important impediments, especially those which could be the potential blockers for team’s main focus.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/578/1*phF5pcMgpXQUi3qh2e3xrg.jpeg" /></figure><p><strong>Why it shouldn’t be the sum of tickets — example.</strong></p><p>Let’s imagine this scenario the team has quite a big capacity so that they took to the sprint backlog a number of features which are related to registration functionality (via Google or Facebook), technical debt stuff, and some minor bugs. They treat those PIBs (Product backlog iteams) as their forecast, but to maximize the business output of the sprint, they decided that they will instead focus on the main business needs.</p><p>Because of that, they agreed on the sprint goal:</p><p><strong><em>“Allow for easier and faster customer account registration.”</em></strong></p><p>Sprint has started.</p><p>After a while, they figure out that Google integration isn’t so simple and needs from the team, quite significant system refactoring. They change the focus to using Facebook’s registration feature.</p><p>At the end of the Sprint, they manage to deliver login/registration functionality, technical debt, and bug fixes. Google story was not delivered and comes back to the backlog — for better refinement.</p><p><strong>Let’s have a look at what happened:</strong></p><ul><li><strong>Did team achieve a sprint goal </strong>— <strong>YES</strong>, because they deliver to end customer possibility to easier and faster account registration. Maybe only by one channel but probably number of registered users will increase.</li><li><strong>Why we use forecast versus commit in terms of sprint backlog </strong>— because development is a complex process and even though we know both systems, something unexpected can happen. The team by committing to a sprint backlog, promise that they will deliver everything, regardless of any impediments and 3rd party conditions or unexpected things.</li><li><strong>How about predictability </strong>— In my opinion, it’s a good mix of sprint goal achievement ratio and velocity (with a bigger weight on the first one). If the Development team have a good relationship with the product owner, the sprint goal achievement ratio should maximize the income of your business, not the velocity itself. In this case, Product Owner is in charge to make sure that sprint goal has maximum business value and the velocity tells the team how much they can possibly handle within one sprint.</li></ul><p><strong>Last but not least.</strong></p><p>Let the team find the best solution to deliver as much businesses value as they can. Assume that they will do their best to deliver things, but be so kind to not trivialize their work. Remember that at the end of the day, they need to do the job, not you. Don’t put sprint backlog under the gun because you will end up with a reduced throughput because people start to protect themselves from overambitious goals.</p><p>Don’t use one value as your main indicator or KPI (Key Performance Indicator). If you’re going to use only the Sprint Goal, you can overlook the team’s velocity, and most importantly, any information that you could use for further improvement. If you’re going to use only velocity, people start to miss the purpose of their work because there is more incentive to delivering smaller tasks with no value rather than tasks with actual value.</p><p>Lastly, always remember to be pragmatic though. Listen to your people and don’t analyse Agile processes with too much focus on numbers, otherwise, you can lose people (both your employees, and customers).</p><p>Did you enjoy this post? If yes, please share it or/and give me a ❤. <strong>Every view, read, and recommendation is for me great praise and motivation.</strong></p><p>Do you want to read more about some other interesting stuff related to Agile, management? Look <a href="https://medium.com/@bartoszmazurek">Medium</a><strong> </strong>or<a href="https://www.linkedin.com/today/author/bartoszmazurek"> <strong>LinkedIn</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=78765185000d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[1 min thought] quality is not just the % in Sonar]]></title>
            <link>https://medium.com/@bartoszmazurek/1-min-thought-quality-is-not-just-the-in-sonar-926646d34a6d?source=rss-639e09599c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/926646d34a6d</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Bartosz Mazurek]]></dc:creator>
            <pubDate>Tue, 08 May 2018 06:54:23 GMT</pubDate>
            <atom:updated>2018-05-08T06:54:23.463Z</atom:updated>
            <content:encoded><![CDATA[<p>How do we achieve quality, and what does it really mean anyway? Long story short, the simplest option is to have a mutual agreement (across all levels, vertically and horizontally) on the Definition of Ready and the Definition of done. If all involved parties obey those definitions, it’s very likely that all the following things will be done to a high level</p><ul><li>unit tests code coverage</li><li>static code analysis</li><li>coverage of test automation</li><li>“just enough” documentation</li><li>performance checks</li><li>rollout / rollback plan</li><li>secure control</li></ul><p>and so on….</p><p>Did you ever think what other things can lead us to this promised land? I believe that these are not the only qualities we should be taking care of.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/531/0*-K838iEku0MWqOuV." /></figure><p>In Scrum, which is basically used by (almost) every business nowadays, there are different roles which have their own areas of responsibilities and need to communicate with other groups to achieve their business goals. A lot of issues that tend to arise usually come from aspects related to communication.</p><ul><li><strong>Quality communication</strong> — Do you talk on a daily basis or just exchange messages? Do you have good communication flow? What kind of tools are you using for daily communication. Do you have enough knowledge to handle possible issues?</li><li><strong>Quality roles </strong>— Do you have clear role expectations, do you follow those roles expectations? Does the team know who is responsible for what in the scrum team and the company itself?</li><li><strong>Quality trust </strong>— Do you trust in your colleague’s decisions, do you have proper context? Are you open to new thoughts, things, concepts? Are you able do experiments that challenge the status quo? Do you have an opportunity to fail fast?</li><li><strong>Quality team </strong>— Do your team members treat each other with respect? Do you have space for open and honest conversation? Do you agree to disagree? How about engagement and focus? Do you treat everyone equally?</li><li><strong>Quality environment</strong> — Do you have space where someone is taking care about your intellectual and psychological needs, do you have the possibility to grow? Are you allowed to give and receive a honest feedback in a safe and respectful way? Do you have support from your manager and are they supporting you?</li></ul><p>The moral of the story here is that we can’t expect that all the technical qualities will be in place or at a good level when you (we) have the problem with basic communication or vague roles. If your (our) teams are dysfunctional, don’t wait for collaboration or communication to magically get better on it’s own. Establish the basics first and other things will follow and eventually things will start going smoother.</p><p>More quick thoughts ?</p><ul><li><a href="https://medium.com/@bartoszmazurek/1-min-thought-product-owner-the-root-of-the-wealthy-process-b871b1c64cad">[1 min thought] Product Owner — the root of the wealthy process.</a></li><li><a href="https://www.linkedin.com/pulse/1-min-thought-scrum-masters-avoid-proxy-bartosz-mazurek/">[1 min thought] Scrum Master(s), avoid to be a proxy.</a></li></ul><p>Did you enjoy this post? If yes, please share it or/and give me a ❤. <strong>Every view, read, and recommendation is for me great praise and motivation.</strong></p><p>Do you want to read more about some other interesting stuff related to Agile, management? Look <a href="https://medium.com/@bartoszmazurek"><strong>Medium</strong></a><strong> </strong>or<a href="https://www.linkedin.com/today/author/bartoszmazurek"> <strong>LinkedIn</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=926646d34a6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[1 min thought] Scrum Master(s), avoid to be a proxy.]]></title>
            <link>https://medium.com/@bartoszmazurek/1-min-thought-scrum-master-s-avoid-to-be-a-proxy-36e7da486fbc?source=rss-639e09599c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/36e7da486fbc</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[scrum-master]]></category>
            <dc:creator><![CDATA[Bartosz Mazurek]]></dc:creator>
            <pubDate>Wed, 18 Apr 2018 07:14:49 GMT</pubDate>
            <atom:updated>2018-04-25T08:13:47.291Z</atom:updated>
            <content:encoded><![CDATA[<p>I always believed that the ultimate win for a Scrum Master (team leader/manager) is when the team no longer needs his or her support (and both sides agree on that). Recently I was asking myself the question, should a Scrum Master need to know everything and be a single point of truth?</p><h3><strong>NO.</strong></h3><p>The Scrum Master needs ensure that people are communicating effectively and that the necessary information is flowing to the people who should be receiving it. In a simpler words, (he or she) needs to ensure good communication both inside and outside the team and also needs to support transparency on the all possible levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/428/1*vaDI1PxBbTaXkpWAb0hcZg.jpeg" /></figure><h3><strong>Why?</strong></h3><p>Because you don’t want to be a single point of failure. When you start to hoard information, sooner or later you (as the Scrum Master) will become a bottleneck and slowly destroy any potential of self-organization within the team.</p><p>Scrum Masters! As Nokia said a few years ago, support communication, acts as a semaphore.</p><h3><strong>“Connect the people!”</strong></h3><p>More quick thoughts ?</p><ul><li><a href="https://medium.com/@bartoszmazurek/1-min-thought-product-owner-the-root-of-the-wealthy-process-b871b1c64cad">[1 min thought] Product Owner — the root of the wealthy process.</a></li></ul><p>Did you enjoy this post? If yes, please share it or/and give me a ❤. <strong>Every view, read, and recommendation is for me great praise and motivation.</strong></p><p>Do you want to read more about some other interesting stuff related to Agile, management. Look <a href="https://medium.com/@bartoszmazurek"><strong>Medium </strong></a>or <a href="https://www.linkedin.com/today/author/bartoszmazurek"><strong>LinkedIn</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=36e7da486fbc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[1 min thought] Product Owner - the root of a healthy process.]]></title>
            <link>https://medium.com/@bartoszmazurek/1-min-thought-product-owner-the-root-of-the-wealthy-process-b871b1c64cad?source=rss-639e09599c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/b871b1c64cad</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-development]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Bartosz Mazurek]]></dc:creator>
            <pubDate>Thu, 12 Apr 2018 10:19:51 GMT</pubDate>
            <atom:updated>2018-10-19T13:53:08.197Z</atom:updated>
            <content:encoded><![CDATA[<p>More and more I realise how important the relationship with the Product Owner, his understanding of the process and his knowledge about the team are, when working in an Agile team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/400/0*5dufrYSFgHIe4Cnl." /><figcaption><a href="https://goo.gl/uvqfD9">https://goo.gl/uvqfD9</a></figcaption></figure><p>I can go far enough to say that without this “connection”, it will be very hard to establish a good and successful process and in actual fact, the flip-side can bring a lot of bad feelings and frustration.</p><p>Let’s look what the main responsibility of a PO is and what happens if he doesn’t care.</p><h4>Crappy backlog</h4><ul><li>No value delivery — creating things that potentially doesn’t bring any value; neither technical nor businesses.</li><li>Mess in priorities — potentially bringing a lot of unfinished products/projects. brings a lot of uncertainty about the future.</li><li>Lack of helicopter view — no ability to understand the true purpose. Lack of clear product vision can highly demotivate the Scrum team.</li></ul><h4>Crappy PBI</h4><ul><li>No acceptance criteria — missing quality, lack of consistency, no “sign off” criteria.</li><li>Big or unfeasible tasks — big lead and cycle time, lack of predictability, big variation of delivery time.</li><li>Not being able to estimate — because of above; lack of basic predictability, big risk factor in terms of value delivery.</li></ul><h4>Crappy events</h4><ul><li>Poor / too micromanaged planning session — negative influence on the team.</li><li>No backlog refinement — a dead end for all above</li></ul><h4>Crappy communication</h4><ul><li>Lack of negotiation — lack of flexibility can bring delays in the delivery process, being closed to ideas can cause reduction of creativity and any mutually beneficial solutions (win-win solutions).</li><li>Lack of time — rest of Scrum team are in the “fog”, don’t know what they need to do and at the same time some unknown expectations are set.</li><li>Things are obvious — development team couldn’t have full businesses context, so things which are trivial for PO can be black magic for rest of the scrum team.</li></ul><p>and much much more….</p><p>So dear team, take your time and meet your product owner — ideally in person. Try to understand his point of view, and talk, talk a lot, because proper discussion can help you go along farther than you might think. And next time when you are going to review some process, start with this side.</p><p>PS. Special thx for <a href="https://www.linkedin.com/in/neil-scicluna-96320923/">Neil</a></p><p>Did you enjoy this post? If yes, please share it or/and give me a ❤. <strong>Every view, read, and recommendation is for me great praise and motivation.</strong></p><p>Do you want to read more about some other interesting stuff related to Agile, management. Look <a href="https://medium.com/@bartoszmazurek"><strong>Medium </strong></a>or <a href="https://www.linkedin.com/today/author/bartoszmazurek"><strong>LinkedIn</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b871b1c64cad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Feedback patterns in self-organizing Agile teams and/or HR as a service.]]></title>
            <link>https://medium.com/@bartoszmazurek/feedback-patterns-in-self-organizing-agile-teams-and-or-hr-as-a-service-a3abee9e6569?source=rss-639e09599c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a3abee9e6569</guid>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[feedback]]></category>
            <dc:creator><![CDATA[Bartosz Mazurek]]></dc:creator>
            <pubDate>Tue, 30 Jan 2018 07:48:07 GMT</pubDate>
            <atom:updated>2018-02-02T07:48:07.064Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xRXwY5zTxILLLGch4UmsCA.jpeg" /></figure><p>More and more I see that feedback in self-organizing agile teams is becoming a hot topic these days. Being part of an agile community, we have different experiences and understanding as to who should be responsible for this process and how it should look like. Despite the structure of the organization, the questions which need to be answered stay more or less the same.</p><ul><li>Who is responsible for getting and giving feedback?</li><li>Who is responsible for employee growth?</li><li>How the feedback culture influences the business?</li><li>Who is responsible for fostering a culture of learning?</li><li>Do we need HR as a service?</li><li>How should HR scale in a large company?</li><li>Are self-organized teams able to handle feedback on their own?</li></ul><p>As a disclaimer at the beginning of this post, I want to say that without the good will and “drive” to learn, all above questions are redundant. To be crystal clear — WE are responsible for our own self-development, and no one can force us to learn if we don’t want to.</p><h3><strong>Functions of feedback</strong></h3><p>Regardless of the type of feedback, we can identify 4 functions of this process:</p><ul><li>Self-development function — This refers to learning about your strengths and weaknesses and knowing how to leverage them.</li><li>Motivation function — highlight the purpose and reason why we’re doing our job.</li><li>Shaping culture function — show an impact which can potentially have a social and business impact.</li><li>Diagnostic function — identify the gaps and weak points in ourselves and our environment</li></ul><h3><strong>Types of feedback</strong></h3><p>Before we go through the different feedback patterns in teams, let’s have a look at the types of feedback types and highlight two factors, frequency and level of formalization.</p><p><strong>Informal ongoing feedback</strong></p><ul><li>“Managing by walking around and listening”</li><li>Small talk</li><li>Company culture events, eg. teams lunches.</li></ul><p><strong>Formal ongoing feedback</strong></p><ul><li>1 on 1 — manager to employee, employee to employee</li><li>Skip-level 1 on 1 — top-level manager to employee (skip one, or more hierarchical level)</li><li>Retrospective — Team to team</li></ul><p><strong>Formalized feedback cycles</strong></p><ul><li>360 feedback — full spectrum; peer review, manager, self-assessment,</li><li>Peer review — team members to employee</li><li>180 feedback — manager to employee</li></ul><h3>Models</h3><p>Now that we are done with the background and we’re “on the same page” let’s focus on two types of models, one with a structured and organized information flow (hierarchy), and the second one, a very flat one (network).</p><p>Both models have their advantages and disadvantages and need different levels of team maturity and people/roles involved in feedback process to work properly.</p><h4><strong>#1. Structured and organized information flow.</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*DZBQi7yf-NfW9mD2KE0lSg.png" /></figure><p>In this model, we assume that in each of the teams we have a person who will take care of feedback process. You can call him the Team leader, people champion, servant leader and so on… In this role, the person will be responsible for managing feedback sessions (all 3 types) and “execute” all 4 functions of it (motivation, diagnostic, culture and grow).</p><p>“Process person” (example Scrum Master) can influence team by delivery process events (like retrospective) and/or coach/mentor team in a team of self-organization, motivation, and performance.</p><p>Because of the nature of those roles and the separation of the roles, they are not mutually exclusive and they complement each other well.</p><p><strong>Let’s look at split and frequency</strong></p><ul><li>Team lead (People champion, servant leader) — Daily basis feedback, 1 on 1, 360</li><li>Scrum Master — Retro, daily basis performance delivery coaching/mentoring</li></ul><p><strong>Where does HR fit in this model? How HR can support us?</strong></p><p>As in every model, HR can support with their skills, they need to pass feedback and knowledge (tools, techniques) to the people who take care of feedback process within the team. They should also evangelize about the importance and true purpose of such feedback.</p><p><strong>Weak points</strong></p><p>The person that is responsible for feedback can be a potential bottleneck in terms of this process and have a monopoly of the knowledge. This can hinder the self-regulation of the team and could also introduce bias.</p><p><strong>How it scales</strong></p><p>Good. In general, this approach limits the energy needed to handle this process. What is need to scale is to build your teams on someone who is able to handle people-related stuff (or find someone who is keen to do it).</p><h4><strong>2#. Flat one — network</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/655/1*kaXCEqNn00r9Lsrug5dQHQ.png" /></figure><p><strong>Let’s look at split and frequency</strong></p><ul><li>All to all — Daily basis feedback, 101</li><li>Scrum Master — Retro, daily basis performance delivery coaching/mentoring</li><li>Pear review like 360 — on demand</li></ul><p><strong>Where does HR fit in this model? How HR can support us?</strong></p><p>In this model, I see a lot of space for HR. HR needs to encourage and support a culture of feedback, both bottom-up and top-down. HR needs to educate the top management and junior developers about the importance of this process and highlight that open and straightforward communication is natural from the very first day.</p><p><strong>How does it scale?</strong></p><p>Even better than the first model, but unfortunately, it requires a great deal of support from all people from the company and it’s much harder to implement unless it exists from the very beginning of the company.</p><p><strong>Weak points.</strong></p><p>For people who don’t “feel” this kind of culture it can be a weird and kind of damaging experience. We can be overwhelmed or abused even though the second person could have good intentions, only because we are not “trained” enough for this kind of honesty and straightforward communication.</p><h4>Let’s talk</h4><p>No matter which model you’re working with, and which role you have, there’s always a good reason to discuss openly. I believe that any kind of feedback is good in the long run, and I also believe that for the most part, people have good intentions. Of course with such fragile thing as personal communication, we need to remember about certain things, rules, and being respectful to the other person, but at the end of the day, we all seek feedback.</p><p>Take it as an occasion to grow, develop your skills and identify your blind spots. Finally, remember that lack of feedback is also feedback……</p><p>Did you enjoy this post? If yes, please share it or/and give me a ❤. <strong>Every view, read, and recommendation is for me great praise and motivation.</strong></p><p>Do you want to read more about some other interesting stuff related to Agile, management, look <a href="https://medium.com/@bartoszmazurek"><strong>HERE</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a3abee9e6569" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to kill Agile in a one statement a.k.a don’t judge book by its cover. #Agile #Scrum]]></title>
            <link>https://medium.com/@bartoszmazurek/how-to-kill-agile-in-a-one-statement-a-k-a-dont-judge-book-by-its-cover-agile-scrum-cd66c6878397?source=rss-639e09599c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd66c6878397</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Bartosz Mazurek]]></dc:creator>
            <pubDate>Fri, 08 Sep 2017 07:15:29 GMT</pubDate>
            <atom:updated>2017-09-26T12:00:25.488Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cQLkvimC1cXgu7SHKFE3aQ.jpeg" /></figure><blockquote><strong><em>“If you not able to deliver a working product at the end of your iteration you can’t say that you are Agile team”</em></strong></blockquote><p>I hear this quite often from people working in Agile-ish environments and across the internet. Recently it got me thinking, and I decided to review (once again) the Agile manifesto, Agile principles, Scrum guide and some other stuff.</p><p>It’s certainly true that a lot of the core aspects of Scrum and agile focus on delivery like:</p><p><a href="http://agilemanifesto.org/principles.html"><strong>12 Agile principals:</strong></a></p><p><em>“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”</em></p><p><em>“Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.”</em></p><p><a href="https://www.scrumguides.org/docs/scrumguide/v1/scrum-guide-us.pdf"><strong>Scrum guide:</strong></a></p><p><em>“The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint. Only members of the Development Team create the Increment.”</em></p><p><em>“The heart of Scrum is a Sprint, a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created.”</em></p><p>… and some more</p><p><strong>Importance of the principals</strong></p><p>Guys, trust me I don’t want to downplay the importance of this guide, but on the other hand, I also don’t agree that it’s gospel.</p><p>The Agile Manifesto and the 12 Agile principles put a lot of emphasis on team autonomy, feedback, motivation, customer collaboration, technical excellence, delivered value, and response to change. Therefore saying that frequent delivery is the most important aspect, in my opinion, is a false.</p><p><strong>Whole system view a.k.a Metrics trap</strong></p><p>I like to see Agile as a whole system, the set of the rules, guidance without priorities. Since we are (only) human and everyone has a different point of view, for some of us one of those rules can be a more important than the others, but making a rule from this kind of “gut feeling” isn’t a smart idea.</p><p>Tracking metrics is a very good analogy for this. If you’re going to focus only on one metric, eg. cycle time, most probably you will see an increase but at the cost of another eg. quality and vice versa. We always should look at the whole system, being selective makes it worse.</p><p><strong>Back to the “statement”</strong></p><p>I see a lot of benefits of having a “potentially releasable product at the end of the sprint”, it mean that your process is quite healthy and your team is effective, but it’s not the end of the world if you produce your software in couple of months, you can still can be <strong>Agile</strong>.</p><p>Did you enjoy this post? If yes, please share it or/and give me a ❤. <strong>Every view, read, and recommendation is for me great praise and motivation.</strong></p><p>Do you want to read more about some other interesting stuff related to Agile, management, look <a href="https://medium.com/@bartoszmazurek"><strong>HERE</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd66c6878397" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vox populi, vox Dei. The problem of missing context. #Agile #Communication]]></title>
            <link>https://medium.com/@bartoszmazurek/vox-populi-vox-dei-the-problem-of-missing-context-agile-communication-fe69bb614e74?source=rss-639e09599c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe69bb614e74</guid>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Bartosz Mazurek]]></dc:creator>
            <pubDate>Fri, 11 Aug 2017 11:03:21 GMT</pubDate>
            <atom:updated>2017-08-11T11:09:09.158Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oPTkdSt-s2x4lXLtWnr8Jw.jpeg" /><figcaption>Hunting on Unicorns, in Black metal forest of Darkness — Fot: Neil Scicluna</figcaption></figure><p><em>“What is the meaning of your job and what is your main goal?”</em></p><p>If you’re going to ask such kind of questions to business people and development teams, you will often get very different answers. If I were to generalize, I would say that those two “mindsets” often think very differently and are not too keen on explaining their thoughts to another group.</p><p>The main cause for this is a lack of the opposite group’s context and an assumption that there is only one truth.</p><p>I’ve seen developers complaining about business and business complaining about developers too many times just because they didn’t (or couldn’t) explain their decision making and context.</p><p><strong>Dev teams care about</strong></p><ul><li>Interesting and challenging tasks</li><li>Relevant technology stack</li><li>Quality</li><li>Delivery process</li><li>Deliverables</li><li>Finished project</li><li>Non functional requirements</li><li>Good working environment</li></ul><p><strong>Business care about</strong></p><ul><li>ROI</li><li>Delivered features</li><li>Customer happiness</li><li>Customer demands</li><li>Market opportunities</li><li>Market demands</li><li>Brand grow</li><li>Competency</li></ul><p>In such situations, we have two groups, with different interests who both claim that the “others” are wrong and we are right, just because they are each expert in their domains.</p><p><strong>Who loses in this situation? Everyone, and what’s more important is that we lose focus on our main goal — the satisfaction of the customer.</strong></p><p><strong>A bit of a story</strong></p><p>Currently, I’m working on a very interesting project, green field technology, agile environment, good collaboration with PO. I knew that this project is very critical for the company but I didn’t really know why… I had a lack of context. I shared my concern with my delivery manager and guess what, he invited our boss, who’s responsible for the digital tribe to explain the bigger picture.</p><p>After one relatively short meeting, we knew exactly why this particular project is so important for the company. Our tribe lead showed and explained to us all the “numbers” related to this project and he made us aware of how fast we can grow if we meet our estimates and what can be next potential opportunities.</p><p>For me, it was a big boost, because finally, I realised WHY. It wasn’t because of a new “Java 8ish, Reactish, AWSish microservices” things. I was excited that I’m holding a product that can grow by hundreds of percents in the next years.</p><p><strong>Other solutions</strong></p><p>Project kickoff — This is a great time where all of these topics can be explained, noted and shared with all interested parties. On such meetings, the team should usually agree on the purpose of the project, success criteria, sponsors, and other roles that have a direct influence on the final delivery.</p><p>PO — This person can be the “bridge”, a mediator, between the business and the development team. One of the limitations of this solution is that that the person who is going to play this role needs to have a good understanding of both sides to be able to translate the goals to a common language.</p><p>Retrospective — Just ask your SM to try provide this kind of information or arrange a meeting with someone who can explain in detail.</p><p>Post mortem — if it’s too late to gather such information, or you just feel so miserable that you feel like you don’t care anymore, try to do a post mortem of the project and agree on the first actions that you will start with on new projects.</p><p><strong>“…common sense..”.</strong></p><p>Dear reader, regardless of whoever you are, business owner, CTO, PO, Junior developer or architect, please, ALWAYS provide YOUR context to all interested parties. Don’t just assume that it’s obvious, because we don’t have this magical ability to read minds, so please, just share.</p><p>Remember, most of the time people have good intentions, but what causes bad impressions is the way things are communicated.</p><p>The road to hell is paved with good intentions and the problem with common sense is that it is not very common.</p><p>PS. As usual, thx @Neil Scicluna</p><p>Did you enjoy this post? If yes, please share it or/and give me a ❤. <strong>Every view, read, and recommendation is for me great praise and motivation.</strong></p><p>Do you want to read more about some other interesting stuff related to management, look <a href="https://medium.com/@bartoszmazurek"><strong>HERE</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe69bb614e74" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How Agile can (sometimes) kill motivation.]]></title>
            <link>https://medium.com/@bartoszmazurek/how-agile-can-sometimes-kill-motivation-4ce3a5a7776e?source=rss-639e09599c2f------2</link>
            <guid isPermaLink="false">https://medium.com/p/4ce3a5a7776e</guid>
            <category><![CDATA[management]]></category>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[hr]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Bartosz Mazurek]]></dc:creator>
            <pubDate>Fri, 23 Jun 2017 07:39:32 GMT</pubDate>
            <atom:updated>2017-06-23T08:42:42.475Z</atom:updated>
            <content:encoded><![CDATA[<p>In an Agile world, we believe that our holy grail is self-organized teams (how to get there is a story for another time). That’s cool, because I’m a big fan of this approach. Most of the time they have a lot of seniority and are very mature as a team.</p><p>At the same time, an Agile approach is strongly focused on communication and cooperation. From my experience, this is one of the most important factors for project success.</p><p>I can see a lot of well-processed cooperation in scrum/kanban/XP teams, which help to solve basic daily issues. People tend to talk more to each other about their concerns, ideas, improvements….</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*WVhrsiCXo2gGTxXnlqUAPQ.jpeg" /></figure><p>That’s AWSOME, isn’t it ???!!!!</p><p>Unfortunately, sometimes I have the impression that amongst all those cool things we forget about other important processes. I think, that we unfortunately tend to forget that Agile, XP, Kanban, are a focused first and foremost on product delivery. This is the main goal at the end of the day, and we shouldn’t lose sight of this.</p><p>What about potential HRish things. Do you see in any of above processes something about regular 101 feedback meetings, 360 reviews, personal development, growth, salary/bonus negotiations, performance management, training budgets… Most probably no, but these are crucial and they are normally part of company culture, managerial duties, and HR processes.</p><p>Currently, I saw/read about cases that companies change their structure because “they don’t need management, they are self-organised”. At the same time, they don’t have a plan B for how to cover all above issues or don’t have enough capacity to do this properly. Who suffers? The people, and in a long run, the managers and the company itself.</p><p>If you (Managers) don’t know about people’s needs and how you’re going to cover their needs and desires, how are you going to handle their growth if you don’t know in which direction they want to go and what they want to achieve?</p><p>Furthermore, based on what data will you make decisions about potential bonuses and salary increases?</p><p>I don’t want to bitch one more time (see the last post :D), but guys (managers and developers) when was it the last time you had a feedback session between you? Can you quickly go through your people and mention their needs and what they want to achieve in the next 6–12 months?</p><p>Guys, please, don’t underestimate the importance of the HRish things. If you do a transformation, have a plan B for how to cover all those topics. And what is the most important, don’t believe that ONLY because you have a great Agile implementation, people will be super motivated. Yes, it’s a big factor, but remember that it’s not the only one.</p><p>Did you enjoy this post? If yes, please share it or/and give me a ❤. <strong>Every view, read, and recommendation is for me great praise and motivation.</strong></p><p>Do you want to read more about some other interesting stuff related to management, look <a href="https://medium.com/@bartoszmazurek"><strong>HERE</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4ce3a5a7776e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>