<?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 Barbara Rogala on Medium]]></title>
        <description><![CDATA[Stories by Barbara Rogala on Medium]]></description>
        <link>https://medium.com/@barbararogala?source=rss-25135e920366------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*2ADjM_IzsJdS9oh5.</url>
            <title>Stories by Barbara Rogala on Medium</title>
            <link>https://medium.com/@barbararogala?source=rss-25135e920366------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 01:55:51 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@barbararogala/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[Why and how to pass the PSPO I certification — Scrum Master’s perspective]]></title>
            <link>https://medium.com/@barbararogala/why-and-how-to-pass-the-pspo-i-certification-scrum-masters-perspective-c0841b22f184?source=rss-25135e920366------2</link>
            <guid isPermaLink="false">https://medium.com/p/c0841b22f184</guid>
            <category><![CDATA[learning]]></category>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Barbara Rogala]]></dc:creator>
            <pubDate>Wed, 01 Aug 2018 21:36:12 GMT</pubDate>
            <atom:updated>2019-01-23T20:14:24.359Z</atom:updated>
            <content:encoded><![CDATA[<p>Being a Scrum Master on a regular basis shows me every day the need to understand the responsibilities of the Development Team and Product Owner on the same level as my own.</p><p>Since in my organisation, Product Owners belongs to other companies, learning from them and supporting them is more difficult than cooperation with developers. I was wondering how to gather the knowledge in that particular situation, and then I realised that one of the ways is trying to pass PSPO I exam.</p><h3><strong>Why do I think that the PSPO I certification is worth investing?</strong></h3><blockquote><em>„The Product Owner is responsible for maximising the value of the product resulting from work of the Development Team. How this is done may vary widely across organisations, Scrum Teams, and individuals.” </em>Scrum Guide</blockquote><p>In my opinion, Product Owner is the most important person in the Scrum Team. And there is a simple explanation. All is about a product and the PO is responsible for its success. We know that success can be defined in numerous ways, but the PO is a guard who stands for all the areas connected to those definitions (for example Product Backlog maintenance, working with stakeholders, maximising the value of the Development Team work).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2F1M9fmo1WAFVK0%2Ftwitter%2Fiframe&amp;display_name=Giphy&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2F1M9fmo1WAFVK0%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia1.giphy.com%2Fmedia%2Fv1.Y2lkPTc5MGI3NjExcm0xOGx3aHhrbjN6bHgzZHMzOHlqNHZ0Zzd5dG5wa29wOWlkZjN3biZlcD12MV9naWZzX2dpZklkJmN0PWc%2F1M9fmo1WAFVK0%2Fgiphy.gif&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="246" frameborder="0" scrolling="no"><a href="https://medium.com/media/5fbfded72b6272894e1dea782e7369f9/href">https://medium.com/media/5fbfded72b6272894e1dea782e7369f9/href</a></iframe><p>As the Scrum Master, I have been working with Product Owners from diverse organisations, and it is true that there is no the best set of tools, ways or solutions how to maintain product and Development Team’s work to maximise its value. Beside that, one is still the same — the Scrum Master helps the Product Owner, and he needs to understand the PO’s role. To maximize the value of his work, the SM should know what kind of duties should be supported by his work and in which domains the PO may need some supervision.</p><p>Preparation to the PSM I gave me guidance how to understand Scrum, and I believe that during studying for the certification I’ve learned more than whenever before. That time, I quickly understood that I need to pass PSPO I — <strong>there is nothing that motivates me more to go deeper</strong> and be familiar with the PO responsibilities, especially those beyond the Scrum Team.</p><p>So, why the PSPO certification is worth investing? I have a simple answer for that question. You can make the PSPO I your goal and motivator to gather new knowledge or it can be some kind of summary of what you currently know. A learning process can give you direction and show you a new areas, and the exam will test if you have a good understanding of the PO role in practical (and unexpected) situations.</p><h3><strong>How to prepare to PSPO I certification?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/300/1*PCb8S3qXBzdyD4q_guoqGw.png" /><figcaption>The PSPO I badge</figcaption></figure><p>First of all, motivation is very important here! Certification is not an easy one, you have to get 85% to pass the exam. Below you can find my tips how to pass the PSPO I exam and what kind of books or blogs are useful at the beginning of your journey with Scrum.</p><p><em>Things you can do:</em></p><ol><li><strong>Understand <em>The Scrum Guide</em> </strong>— identify the most important things or those which you don’t remember. If you are not the native English speaker, read the Scrum Guide in your own language three times too. That path will help you learn the key things about working with Scrum. The PSPO I exam includes a bunch of questions about the Scrum framework which also are in the PSM I test.</li><li><strong>Read the <em>Scrum Glossary</em></strong> — it is the brief list of the most important words, it helps to understand questions in the test.</li><li><strong>Read the <em>The New New Product Owner</em> </strong>— it is a fascinating article, showing overall Product Owner’s work purpose, read it twice and make some notes or highlights.</li><li><strong>Read the <em>Evidence-Based Management Guide</em></strong> — really helpful and valuable for PO’s, read it twice and make some notes or highlights.</li><li><strong>Do </strong><a href="https://www.scrum.org/pathway/product-owner-learning-path"><strong>Product Owner Learning Path</strong></a><strong> from Scrum.org site</strong>—it is the extensive list of areas which are essential to the good and deep understanding of the PO role.</li><li><strong>Do all Open Assessments from Scrum.org site</strong> — you will see what type of questions will occur on the exam, you should be completely sure that they are clear for you — 100% scored a few times in a row is a must.</li><li><strong>Do quizzes from the blog of </strong><a href="http://mlapshin.com/index.php/scrum-quizzes/"><strong>Mikhail Lapshin</strong></a> — it is the best way to learn and understand the key aspects of the Product Owner’s role (all questions are based on the Scrum Guide and sources promoted by the Scrum.org organization).</li></ol><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fgiphy.com%2Fembed%2FxSiN0kCNA1fpu%2Ftwitter%2Fiframe&amp;url=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxSiN0kCNA1fpu%2Fgiphy.gif&amp;image=https%3A%2F%2Fmedia.giphy.com%2Fmedia%2FxSiN0kCNA1fpu%2Fgiphy.gif&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=giphy" width="435" height="244" frameborder="0" scrolling="no"><a href="https://medium.com/media/fe7209ad35b85fe028ac7d691f20cccb/href">https://medium.com/media/fe7209ad35b85fe028ac7d691f20cccb/href</a></iframe><p><em>Tips &amp; Tricks for those who are at the beginning of their journey with Scrum:</em></p><ol><li><strong>Try to visualize</strong> (mind maps, sketchnoting) new information you’ve learned from reading any sources.</li><li><strong>Read two highly important books</strong> in a way for better understanding of the Scrum: <em>The Art Of Doing Twice The Work In Half The Time by Jeff Sutherland </em>and <em>Software in 30 Days by Jeff Sutherland and Ken Schwaber.</em></li><li><strong>Participate in the PSPO training course</strong> — it is a good way to get familiar with PO’s role while you are at the beginning of your experience with the Scrum. There is vastness of books which you can read, but meeting with people who can explain you the framework and roles in practice is more worthy.</li><li><strong>If you have time, read some </strong><a href="https://www.scrum.org/resources/suggested-reading-professionalscrum-product-owner"><strong>books recommended by Scrum.org</strong></a> as a preparation for the PSPO and the PSM certification —<a href="https://www.scrum.org/resources/suggested-reading-professionalscrum-product-owner,">,</a> they will widen your horizons.</li><li><strong>Review </strong><a href="https://www.scrum.org/resources/blog"><strong>Scrum.org blog</strong></a> — there are various articles related to the PO work areas which can help you understand better the real meaning of this role.</li></ol><p>If you believe that you have done everything to learn how to be the great Product Owner, and you have all test listed above at one’s fingertips… you are ready to get the exam!</p><h3><strong>Summary</strong></h3><p>I think that preparation for any exams needs time and strong motivation, it also gives us the goal which we want to accomplish. The way I went to get the PSM I and the PSPO I certification shows me that the goal is the key, and in that case, it is the best motivator to learn new things or widen horizons.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c0841b22f184" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Write User Stories and Why They are Crucial for Successful App Development]]></title>
            <link>https://medium.com/droidsonroids/how-to-write-user-stories-and-why-they-are-crucial-for-successful-app-development-faf00f08d9d8?source=rss-25135e920366------2</link>
            <guid isPermaLink="false">https://medium.com/p/faf00f08d9d8</guid>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[clients]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Barbara Rogala]]></dc:creator>
            <pubDate>Wed, 21 Mar 2018 10:40:09 GMT</pubDate>
            <atom:updated>2018-04-01T21:52:16.387Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>In this article, we will explain what User Stories are, how to build them correctly, and why you should be aware of them, if you want to develop a mobile or web application.</strong></h4><p><em>Written by </em><a href="https://medium.com/u/25135e920366"><em>Barbara Rogala</em></a><em> &amp; </em><a href="https://medium.com/u/33ac0631360f"><em>Cieszysława Tichonow</em></a></p><blockquote>This post was featured in <a href="https://www.androiddevdigest.com/digest-185/">AndroidDev Digest #185</a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vP82LXJC_g0P3hg8fk2sNA.jpeg" /></figure><p>If you want to develop a mobile or web application, <strong>User Stories will help you to find common ground with a Development Team, especially if you don’t have programming skills and don’t know the technical language. </strong>We can say that, thanks to User Stories, our work implementation is better prepared and in some cases,<strong> the development can be faster.</strong></p><p>In short, User Stories:</p><p><strong>✔️eliminate bridges </strong>between business and technical teams,<br> ✔️help with <strong>product understanding</strong>,<strong><br> ✔️engage app users </strong>in process modelling.</p><p>But, how can we achieve this level and use all of these advantages?</p><figure><img alt="How to Write User Stories and Why They are Crucial for Successful App Development" src="https://cdn-images-1.medium.com/max/640/0*Y97bZtqv9MX7h8yc.gif" /></figure><p>In this article, we will try to answer that question and explain to you why <strong>using User Stories are so efficient and valuable from a business point of view</strong>.</p><h3>What exactly is a User Story?</h3><p><strong>A User Story is a description of an application’s functionality</strong> and it<strong> should be understandable for everyone involved</strong> in the product development process — for both developers and non-technical team members.</p><p>A User Story usually consists of a Summary and a Description. In this article, <strong>we will focus on the Summary because it’s the crucial part of the User Story</strong>, which is mostly underestimated and difficult to formulate.</p><h3>6 attributes of a good User Story</h3><p>A good User Story can be described via six attributes (<a href="https://xp123.com/articles/invest-in-good-stories-and-smart-tasks/">INVEST by Bill Wake</a>):</p><ul><li><strong>Independent</strong> — this means that we should avoid dependencies between User Stories as much as possible. It is better to create a bigger story than one with dependencies, which can cause problems with estimation and prioritization.</li><li><strong>Negotiable</strong> — stories are not fixed descriptions of functionalities and they should contain in their description only short information about the basic specifications. If more information is required, a development team should start a discussion with the Product Owner.</li><li><strong>Valuable</strong> — stories have to be valued by users of the software or the Product Owner (client). Thanks to this direction, the Product Owner can easily handle prioritization and scheduling.</li><li><strong>Estimatable</strong> — in most cases, a User Story is not estimable when it is too big, not described well or developers have not enough knowledge to do it. In all these cases, the team should resolve the problem and try to make the story ready for estimation.</li><li><strong>Small</strong> — the proper size of a User Story is based on the team, its knowledge, the technologies being used and the project type.</li><li><strong>Testable</strong> — stories should be defined as a testable part of a working system, if a story has passed its tests, it proves that it has been successfully developed.</li></ul><p>To achieve all of these points, the whole team should work together and discuss each User Story on Refinement meetings during Sprints.</p><p>Thanks to this approach, <strong>the scope of the project will be clear for everyone </strong>which, for sure, is going to have <strong>an impact on the quality of the development process</strong>.</p><h3>User Story template</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/783/1*3JrEeODCJ4mEbeaFhgNHRw.png" /></figure><p>It’s clearly visible who is an actor, how does he interact with the system’s component(s) and why or where does the interaction take place. <strong>Using this pattern and remembering these three elements allows us to write simple and understandable stories</strong> every time and usually for each case.</p><h3>📖 Test yourself 📖 Which User Story is correct?</h3><p>We already know the rules and we know what kind of criteria a good User Story should follow. So, <strong>have a look at two examples of how good and bad User Stories look like.</strong></p><p>Let’s say we would like to write a perfect User Story using an example of Instagram.</p><h4>Instagram User Story // Example 1:</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/1*sIjyg-lvPly0n8WZANPusw.png" /><figcaption>Instagram User Story // Example 1</figcaption></figure><p><strong>Try to guess which of these two options would be better:</strong><br> <em>User’s personal data can be edited by a user</em> or <em>User edits his or her profile to update their personal data</em></p><p>At a glance, the first story seems to be good enough. But, do we know Why / For what / From where the action of editing data has to be available on Instagram? Remember that, sometimes, it’s obvious for an author, though we can’t be sure that someone who will work on it will understand it as well.</p><p>So, let’s see why, in this version, <em>when a User edits his or her profile to update their personal data, it</em> is better. We know <strong>who (user) is doing, what (edits his profile), and why (to update his personal data).</strong></p><figure><img alt="How to Write User Stories and Why They are Crucial for Successful App Development" src="https://cdn-images-1.medium.com/max/1024/0*y3sieA_yfc8RkgRJ.png" /></figure><h4>Instagram User Story // Example 2</h4><figure><img alt="How to Write User Stories and Why They are Crucial for Successful App Development" src="https://cdn-images-1.medium.com/max/750/0*UyarnYgV3Xtbqz-0.gif" /><figcaption>Instagram User Story // Example 2</figcaption></figure><p>We can start with a story where the <em>App should let users add stories</em>. Do you see which parts of a good User Story pattern are missing here?</p><p>How should the correct version look like? Let’s compare it with the example when a <em>User adds stories to his profile from the profile tab to show it to his friends</em>.</p><figure><img alt="How to Write User Stories and Why They are Crucial for Successful App Development" src="https://cdn-images-1.medium.com/max/1024/0*dX4y9ubfJTwNGcOe.png" /></figure><p>The table shows which parts are missing in the first User Story. Without Who and Why / For what / From where , the action is completely unintelligible.</p><p>Based on these two comparisons, we can learn how to recognize a good pattern, which will help our teams build a product matching a Product Owner expectations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/786/1*jX2JdTrIw5OCbfP3NVGXVQ.png" /></figure><h3>8 great advantages of User Stories for your business</h3><p><a href="https://www.mountaingoatsoftware.com/company/about-mike-cohn">Mike Cohn</a> wrote about 8 great advantages of User Stories in his book, which perfectly shows why they are valuable for business:</p><ol><li>User Stories emphasize <strong>verbal communication </strong>— instead of writing an extremely detailed description or documentation for each requirement, the Product Owner should be in contact with the development team. <strong>The User Stories form forces both sides to communicate and make the feedback loop as short as possible.</strong> Only in this way will you get what you want; in the opposite case, it will probably only be the developer’s interpretation of the written document.</li><li>User Stories are <strong>comprehensible</strong> to everyone — the opposite to detailed technical requirements, a good User Story is clear for developers and business people, which <strong>helps in implementing the right software</strong>.</li><li>User Stories are the <strong>right size</strong> for planning — release planning, risk forecasting, and prioritization are clear processes when the<strong> requirements are the right size and not too closely combined</strong> with other parts of the software, both for developers and client.</li><li>User Stories work for <strong>iterative development </strong>— there is no need to have completed list of User Stories at the beginning of the project. <strong>The team can start with a few of them and add new ones during the development process through the next Refinement meetings.</strong> This advantage especially supports products which are not well known at the beginning and will be changed often during development.</li><li>User Stories encourage <strong>deferring detail</strong> — stories can be written during the whole project, so <strong>you, as a Product Owner, can add a bigger epic whenever you want</strong> and then, in cooperation with the developers, you can easily describe or split it later.</li><li>User Stories support <strong>opportunistic design </strong>— software must be developed opportunistically, because most of the time our product changes during the implementation process and we are incapable of remembering that many details and predicting all the possible problems or dependencies.</li><li>User Stories encourage <strong>participatory design </strong>— User Stories help to <strong>engage real users in the process</strong> and it allows you to react quickly to their needs or expectations.</li><li>User Stories build up <strong>tacit knowledge </strong>— the knowledge builds up within the team, not just the Product Owner.</li></ol><p>Experience shows us that <strong>the most important part of the mobile application development process is a good understanding of customer needs and real values, which stand behind ideas that have to be implemented</strong>.</p><figure><img alt="How to Write User Stories / Mobile App Development Process" src="https://cdn-images-1.medium.com/max/400/0*gqfaf3kt-pCLWxig.gif" /></figure><p><strong>This is only possible when developers and the Product Owner use the same method to describe software functionalities</strong> and, as I wrote above, User Stories make this happen.</p><h3>Wrap up</h3><p><strong>User Stories are universal and we can use them in any kind of projects, including mobile &amp; web application development processes. Properly prepared, they can be a big help for the team and the Product Owners.</strong></p><p>If you want to go deeper in the topic, we strongly recommend you Mike Cohn’s book “User Stories Applied”, which is full of example cases, explanations and good conclusions about User Stories.</p><p><strong>Now is the time to check your new knowledge in real life </strong>🚀</p><p>Let us know if you have any other ideas when it comes to creating a good User Story. Just leave us a comment on the article.</p><p><em>Originally published at </em><a href="https://www.thedroidsonroids.com/blog/how-to-write-user-stories-why-they-are-crucial-for-successful-app-development"><em>iOS &amp; Android Mobile App Development Company — Droids On Roids — Poland</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=faf00f08d9d8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/droidsonroids/how-to-write-user-stories-and-why-they-are-crucial-for-successful-app-development-faf00f08d9d8">How to Write User Stories and Why They are Crucial for Successful App Development</a> was originally published in <a href="https://medium.com/droidsonroids">droidsonroids</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>