<?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 Artemisa Yescas on Medium]]></title>
        <description><![CDATA[Stories by Artemisa Yescas on Medium]]></description>
        <link>https://medium.com/@arteyescas?source=rss-5704a6d8bdde------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_H4E5L70fhUGyzgQmUAb8g.jpeg</url>
            <title>Stories by Artemisa Yescas on Medium</title>
            <link>https://medium.com/@arteyescas?source=rss-5704a6d8bdde------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:56:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@arteyescas/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[Transitioning From Quality to Product Management — pt 4]]></title>
            <link>https://arteyescas.medium.com/transitioning-from-quality-to-product-management-pt-4-20900fda07f8?source=rss-5704a6d8bdde------2</link>
            <guid isPermaLink="false">https://medium.com/p/20900fda07f8</guid>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <dc:creator><![CDATA[Artemisa Yescas]]></dc:creator>
            <pubDate>Tue, 06 Apr 2021 02:33:18 GMT</pubDate>
            <atom:updated>2021-04-06T02:52:44.106Z</atom:updated>
            <content:encoded><![CDATA[<h3>Transitioning From Quality to Product Management — pt 4</h3><h4>Am I ready for the role?</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FhJkUFAxiR07XJ2O9DlXiw.jpeg" /></figure><p>Yaaay, I’ve finally reached the end of this series of posts!! Even though I read, studied, and practiced everything that my mentors recommended, plus the Professional Scrum Product Owner (PSPO I) training material… <br>I still feel not capable. And that is <strong>normal</strong>.</p><p>I compare it to my testing background:<br>until you are out there getting your hands dirty, learning from experience, reaching your goals, you won’t feel prepared and accomplished.</p><p>What I can offer you is a compilation of the advice that I received and treasured during my role transition:</p><ul><li>Every company looks at the role differently. Find out <strong><em>how</em></strong> does your company defines the role and clarify any expectations.</li><li>Learning about the industry vertical is <strong><em>crucial</em></strong><em> </em>and it is a differentiator between an average PM/PO to an exceptional one.</li><li>Folks may not treat you seriously since you don’t have that much business experience and this could be downright ‘insulting’ at first. In some ways, some people believe that because they understand biz that they are somehow above you. But drive on. We all start somewhere.</li></ul><blockquote>Don’t underestimate the fine &amp; vintage art of taking notes.</blockquote><ul><li>Learning is endless, learn as much as possible.</li><li>Listen, absorb, and don’t hesitate to make questions.</li><li>Never assume anything.</li><li>It’s OK to ask for help.</li><li>Give thanks to the team + give praise to the team = :)</li><li>Identify your strengths and understand how can you contribute back supported by them.</li><li>Ask for feedback frequently.</li><li>Adapting is <strong><em>KEY</em></strong>.</li><li>Build trust and relationships.</li><li>Conduct yourself with empathy and never show a blameful attitude when things go wrong.</li><li>Always think from a diverse set of user perspectives.</li></ul><h4>My Next Steps</h4><p>Currently, I am already working with a client in a PM/PO position, but I still want to test my learnings. I want to take the Professional Scrum Product Owner<strong>™</strong> level I (PSPO I) certification to validate my knowledge of the Scrum framework and the ability to support value creation and delivery.</p><p>It is a thorough assessment in place to ensure you understand the Product Owner role and therefore detailed in its questions and required answers. Many questions ask the test-taker to think about or interpret the meaning from the Scrum Guide and/or to apply content from the PSPO subject areas and in some cases, apply their own experience.</p><h4>Great Lectures</h4><ul><li><a href="https://www.scrum.org/resources/blog/tips-starting-product-owners">Tips for starting Product Owners</a></li><li><a href="https://www.romanpichler.com/blog/one-page-product-owner/">The Scrum Product Owner Role at a Glance | Roman Pichler</a></li><li><a href="https://blogs.starcio.com/p/agile-for-product-owners.html">Social, Agile, and Transformation</a></li></ul><h4>PSPO Certification</h4><p><a href="https://www.scrum.org/professional-scrum-product-owner-i-certification#Details">Professional Scrum Product Owner™ I</a></p><p><strong>Thanks for reading! Let me know any tips and tricks that could be handy.<br>Clap</strong> 👏 — please show if you like this article so others can find it.<br><strong>Respond </strong>💬 — please let me know if you have any suggestions or questions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=20900fda07f8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transitioning From Quality to Product Management — pt 3]]></title>
            <link>https://arteyescas.medium.com/transitioning-from-quality-to-product-management-pt-3-30fb040e2e6d?source=rss-5704a6d8bdde------2</link>
            <guid isPermaLink="false">https://medium.com/p/30fb040e2e6d</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Artemisa Yescas]]></dc:creator>
            <pubDate>Fri, 19 Feb 2021 02:28:00 GMT</pubDate>
            <atom:updated>2021-02-19T18:37:25.343Z</atom:updated>
            <content:encoded><![CDATA[<h3>Transitioning From Quality to Product Management — pt 3</h3><h4>User Stories can either save you or condemn you.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XFF_JlM-wlzr5AzUENBlOw.jpeg" /></figure><p>In Agile, one of the most common approaches for capturing the user’s requirements is User Stories. They represent customer requirements in a card, leading to conversation and confirmation<em> </em><a href="https://ronjeffries.com/xprog/articles/expcardconversationconfirmation/"><em>(Jeffries, 2001)</em></a>.</p><p>Let’s start by clarifying that anyone in an Agile team can write a user story. <em>However</em>, the product owner needs to make sure the user stories are actually necessary for the product and they have a prioritized backlog. To make sure this happens, the PO needs to communicate regularly with the team and they discuss the stories together. User stories should get written collaboratively during the product backlog grooming/refinement sessions.</p><h4>User Story</h4><blockquote>A user story describes functionality that will be valuable to either a user or a purchaser of a system or software. They are generalized details of the user requirements of the system and what the client hopes to gain from this functionality. They don’t show much details and the requirements are added later on, once they are agreed upon by the team.</blockquote><p>Format:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*upd40KubbgG4f-ny8OTTFQ.jpeg" /></figure><p>User stories are high-level and simple, written only long enough to include a brief description and acceptance criteria. The user stories are not only composed of a written description but also conversations about the story that serve to clarify the details of the story. They also contain tests and documents that help determine when the story is complete. Remember: user stories are not a full description of work to be done; their purpose is to encourage collaboration.</p><h4>Acceptance Criteria</h4><blockquote>List of conditions that need to be met in order to accept a story as complete. <br>“What needs to be done”.</blockquote><p>It is very important that before agreeing to work on a story, the team must clearly understand the acceptance criteria.</p><h4>Acceptance Tests</h4><blockquote>All the tests that form the ‘acceptance criteria’ for the user story. Each acceptance criteria can have one or more acceptance tests. They can be functional and non-functional. <br>“How they should be done”.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EdAIprbbyUWhrmuviktqFQ.jpeg" /></figure><p>To create a great user story there are six attributes we can focus on:</p><ol><li><strong>I</strong>NDEPENDENT<br>Avoid introducing dependencies between stories because dependency leads to prioritization and planning problems, and harder estimation.</li><li><strong>N</strong>EGOTIABLE<br>Stories are not written contracts, they are reminders to talk to the customer. They are short descriptions of functionality, the details of which are to be negotiated in a conversation between the customer and the development team.</li><li><strong>V</strong>ALUABLE FOR USERS/CUSTOMERS<br>Stories should be written so that their value to users or customer is clear. To ensure each story is valuable to users/customers have the customer write the stories.</li><li><strong>E</strong>STIMABLE<br>The larger the story, the harder it is to estimate it. Developers need to be able to estimate the size of the story or the amount of time it will take to turn a story into working code.</li><li><strong>S</strong>MALL<br>Size matters because if stories are too large or too small you cannot use them in planning. The user story is appropriately sized based on the team, its capabilities, and the technologies in use but also small enough to fit in a Sprint.</li><li><strong>T</strong>ESTABLE<br>Successfully passing the story’s tests proves that it has been successfully implemented.</li></ol><p>When blocked on how to shape a User Story, elaborating the structure of your user story by using mind maps is very helpful, for example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/858/1*1gIaPaKQtddxBTzDjxZn_Q.png" /><figcaption>User Story Elaboration (grayed fields are an alternative approach)</figcaption></figure><p>The product owner is responsible for adding to the product backlog only useful features and providing the best return on investment, this way the User Stories get prioritized based on their value to the organization. During a Sprint planning meeting, the team decides which stories are being tackled for the next Sprint, forming the Sprint Backlog.</p><h4>Definition of Ready</h4><blockquote>Definition of Ready (DoR) is an explicit and visible working agreement between the teams and the product owner on what readiness means for them. Basically a criteria that a user story must meet prior to being accepted into the upcoming Sprint. The team decides and can refuse to take an item into the Sprint if the DoR is not met.<br>Normally the DoR follows the format of a checklist based on the INVEST matrix and the user story including an acceptance criteria. User stories get reviewed during the product backlog grooming/refinement meetings.</blockquote><h4>Definition of Done</h4><blockquote>The team agrees on a list of criteria that must be met before a product increment (usually the acceptance criteria of the user stories) is considered “done”. Definition of Done (DoD) is critical for a team since verifying that the activities completed meet the DoD criteria will ensure that you are delivering features done, in terms of functionality and quality. The PO officially determines when the acceptance criteria is met and at this point the user stories are considered “accepted”.</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sivSygFPfLCmatTdK3A4NA.jpeg" /><figcaption>In an Agile Scrum Framework — Where does DoR and DoD take place? / Artemisa Yescas 2020</figcaption></figure><h4>Multiple Users</h4><p>When writing a user story keep in mind to think about your user, a clearly defined role. if there are multiple end-users you could consider making multiple stories. User Personas is a method that helps to scope out the range of users, it supports writing user stories from the user persona’s point of view. Its impact is discovering the <em>right</em> stories.</p><p>More about this topic → <a href="https://en.99designs.com.mx/blog/business/how-to-create-user-personas/">How to create a User Persona</a></p><h4>Splitting Stories</h4><p>Large user stories are actually Epics and they are further divided to form smaller stories. If a story doesn’t fit in an iteration, the story needs to split into two or more smaller stories.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*iaev5TRb0Qbeq1KCfpbWQA.png" /></figure><p>Smaller as “small enough” stories are way better since they get implemented, delivered, and returning value more quickly. I am stressing this part because if a story is too small, it won’t provide a measurable business value. Eventually, you and your team will get better at splitting stories.</p><p>Benefits of breaking into small manageable units of work are:</p><ul><li>Estimation and tracking are easier.</li><li>Small pieces of work promote ownership and accountability by the team</li><li>The tasks are more doable</li><li>It is effortless to uncover key risks early on</li></ul><p>More about this topic → <a href="https://www.humanizingwork.com/the-humanizing-work-guide-to-splitting-user-stories/">Patterns for Splitting User Stories</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*ksee-dnqZ9NjuyLDMBfFkg.jpeg" /><figcaption><a href="https://twitter.com/ialcazar/status/493442626180628480?s=20">User Story Splitting Patterns</a> — Israel Alcázar 2014</figcaption></figure><h4>Estimating Stories</h4><p>Estimation is hard in the beginning. What is the right size of a story? There is no standardized or universal size for a user story, it always depends on your team, their skills, the technology in use, and their level of domain knowledge. Same as with splitting, when your team has a cadence, this will be easier and more accurate. The decision on which technique to use to point stories relies on you and your team.</p><p>More about this topic → <a href="http://www.agilebuddha.com/agile/all-about-story-points-and-estimation/">All about story points &amp; Agile estimation series</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fFENH8yTxSMFmLC68Pty6w.jpeg" /><figcaption>Estimating complexity using Fibonacci Sequence — Artemisa Yescas 2020</figcaption></figure><h3>Ok but, why User Stories?</h3><ul><li>It is an easy-to-understand concept.</li><li>Right size for planning.</li><li>Work for iterative development.</li><li>Emphasize verbal rather than written communication.</li><li>A placeholder for further discussions.</li><li>Reduce waste since nothing is done with the user story until it is prioritized by the customer.</li></ul><h3>Finally, some things to consider:</h3><ul><li>The difference between a user story and a traditional requirement is the level of detail.</li><li>Avoid the <em>how </em>trap. Acceptance Criteria states intent but is not a solution.</li><li>Do not write User Stories that require the development of other features.</li><li>Acceptance criteria need to have a standard of measurement used to gauge the progress of product development.</li><li>Effective User Stories should not exist without tight collaboration with the user and without them understanding what the requirement will supply.</li><li>Do not feel pushed to use User Stories, if this format doesn’t work for you there are other ways to do it.</li><li>Take a story writing workshop-helpful to figure out how to improve the product backlog and to fill it more effectively.</li></ul><h3>References</h3><ul><li><a href="https://www.informit.com/store/user-stories-applied-for-agile-software-development-9780321205681">User Stories Applied: For Agile Software Development</a></li><li><a href="https://www.scrum.org/scrum-guide-2020">Scrum Guide 2020 Updates</a></li><li><a href="https://ronjeffries.com/xprog/articles/expcardconversationconfirmation/">Essential XP: Card, Conversation, Confirmation</a></li></ul><h3>Next steps in part IV…</h3><p>The advice other awesome PM/POs gave to me.</p><p><strong>Thanks for reading!<br>Clap</strong> 👏 — please show if you like this article so others can find it.<br><strong>Respond </strong>💬 — please let me know if you have any suggestions or questions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=30fb040e2e6d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transitioning From Quality to Product Management — pt 2]]></title>
            <link>https://medium.com/swlh/transitioning-from-quality-to-product-management-pt-2-f33db2b566da?source=rss-5704a6d8bdde------2</link>
            <guid isPermaLink="false">https://medium.com/p/f33db2b566da</guid>
            <category><![CDATA[story-maps]]></category>
            <category><![CDATA[user-story-mapping]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[product-owner]]></category>
            <dc:creator><![CDATA[Artemisa Yescas]]></dc:creator>
            <pubDate>Tue, 02 Feb 2021 01:03:34 GMT</pubDate>
            <atom:updated>2021-02-04T07:38:40.632Z</atom:updated>
            <content:encoded><![CDATA[<h3>Transitioning From Quality to Product Management — pt 2</h3><h4>A practical approach using Story Mapping</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Xo0aBcbFdtFghF9GNlJLag.jpeg" /><figcaption><a href="https://www.comstocksmag.com/longreads/meeting-goals">(Original photo by Mike Graff)</a></figcaption></figure><p>Alrighty, in my <a href="https://arteyescas.medium.com/transitioning-from-quality-to-product-management-pt-1-cb67c169d8df">previous article</a> we went through a list of product management theory and reference material which lays the foundation for the terminology, standardized procedures, and best practices.</p><p>Now we need to roll up our sleeves and get immerse on the practical side!</p><p>We are going to start with <strong>User</strong> <strong>Story Mapping</strong>. Let’s remember, story maps look at the big picture and it facilitates rich discussions about product vision, potential users, their needs, key product capabilities, minimal viable product, product releases, their goals, risks, and priorities. It is about creating a shared understanding of the following narratives:</p><ul><li>Developers understand the users, their goals, and context better.</li><li>Designers understand what is feasible, what the risks, costs, trade-offs are.</li></ul><blockquote>Story Mapping keeps us focused on users and their experience, and the result is a better conversation, and ultimately a better product. — Jeff Patton.</blockquote><h3>1. Frame It (capture the primary goal of your product/feature)</h3><p>Before starting the mapping, create a small product/feature brief. Think of it as establishing a common goal or vision. Ask these questions:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yTRte5Ay60LNFLhMCuZdXg.png" /></figure><h3>2. Map that ‘BIG PICTURE’ (building the backbone)</h3><p>Start with blank wall space and a high-level vision — <em>a placeholder for upcoming conversations.</em> The activities and high-level user tasks that tell the whole story/entire user journey form the <strong>backbone</strong> of your story map. <br>Think “milewide, inch deep”.</p><p>Continue by describing the <strong>user type </strong>most critical to your product’s success. Then imagine a common day in that user’s life adopting the new product, an <em>ideal user flow.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*__gjbJWNR0QAy300bmH6MA.png" /></figure><p>Map the user’s steps as user tasks from left to right. Identify user activities, any groups of tasks that together can support a common goal. After this, add in supplementary users. When following the typical use of the product, you may find other types of users enter your story. Proceed to model their story left to right.</p><p>We need to talk to subject matter experts to get more information, that way our journey will be nourished. During this activity, everybody can write the steps needed and put them on the board.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-U5a-SXngs7H5ESWszE9ug.png" /></figure><h3>3. Explore &amp; break large tasks into subtasks</h3><p>The steps in the backbone probably are too big for a sprint duration. Break down larger user tasks into smaller subtasks and interface details. Add cards, split one card into two, rewrite, reorganize them. Place subtasks underneath their associated task/step and activity.</p><p>Think about all the possibilities, what could go wrong, exceptions, variations. Do not worry if your ideas are <em>‘in or out of scope’</em>. Later on, things can move to adjust to the desired scope. This is also the time to add other product details like a description of the proposed UI, business rules, data elements, etc.</p><p>Don’t hesitate to involve other people from different parts of your company, they might tell you: where you are missing steps in the user journey, if the task is too big, too small, too risky to implement. Search for<em> ‘pain points’</em>, most of the time those are things we haven’t thought about.</p><p>Remember to prioritize the importance of each task by moving them up and down, keeping high-priority ones at the top.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D1na0ahvh6P_haztkTMzvQ.png" /></figure><h3>4. Slicing Viable Releases</h3><p>It’s time to slice your map into product releases. By moving horizontally from left to right you can get a slice of what your product could do. These slices need to form an increment product release roadmap where each release should be a minimal viable product release.</p><p>Every release should have explicit outcomes and impact. This way we know how the release contributes to the overall goal. Also, identify product success metrics. Answer the following, <em>‘what would we measure to determine if this product was successful?</em>’.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*omzAtmdcgqsxortTyhU4bQ.png" /></figure><h3>5. Slicing a Developing Strategy</h3><p>Slice the first release of your map into three or more delivery phases so that your team can learn fast and avoid risk. A development strategy can help you release the best product possible in the time constraints you have. For example:</p><ul><li><strong>Delivery phase 1 — ‘MVP’:</strong> the simplest possible functional version of your product. Vet the product with users and other stakeholders. Begin validating performance and scalability.</li><li><strong>Delivery phase 2 — ‘Higher quality of service’:</strong> completing all major functionality and making existing functionally richer. Continue testing and adjusting the product based on feedback; continue testing performance and scalability.</li><li><strong>Delivery phase 3 — ‘Scaling Up’:</strong> Refining the product in preparation for release. Continuously assess release readiness based on your release level product goals. Notice that unforeseen work can emerge during this last stretch of development, so you need to count it in.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L5PpEhhaXVVqXGjXATxSrA.png" /></figure><p>In your developing strategy, you need to consider planning the work necessary to refine stories. If the stories still need it, you can have story workshops to go through details and agree on acceptance criteria. <br>Also, plan and schedule development and testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iieGy3w1GO3W5TOmwQ-FDA.jpeg" /></figure><h3>Last thoughts:</h3><ul><li>In terms of scope and complexity, visual representation of the product backlog brings all stakeholders on the same page.</li><li>Story Mapping helps with prioritization and supports easy slicing of the backlog into small enough releases. Be ruthless when slicing!</li><li>Don’t forget your user story map is alive. Make sure an updated version exists and it remains relevant.</li><li>Story Map Structure: <strong>Goals &gt; Activities &gt; Tasks &gt; Stories</strong></li><li>A good map has many levels of detail.</li><li>Remember to surf your system from a user perspective.</li><li>For an existing backlog of well-written user stories, simply pull them into your map.</li><li>A useful comparison I use: <br><strong><em>Activities &lt;&gt; Themes <br>User Tasks&lt;&gt;Epics<br>User SubTasks &lt;&gt; User Stories</em></strong></li></ul><h4>Great online tools to do Story Mapping:</h4><ul><li><a href="https://trello.com/">Trello</a></li><li><a href="http://www.featuremap.co/">Feature Map</a></li><li><a href="https://miro.com/templates/user-story-map/">Miro</a></li><li><a href="https://marketplace.atlassian.com/apps/1222309/agile-user-story-mapping-board-for-jira?hosting=cloud&amp;tab=overview">Agile User Story mapping for Jira</a></li></ul><h4>Resources studied:</h4><ul><li><a href="http://shop.oreilly.com/product/0636920033851.do">User Story Mapping</a></li><li><a href="https://www.lego4scrum.com/">#lego4scrum</a></li><li><a href="https://www.agilealliance.org/glossary/storymap/#q=~(infinite~false~filters~(postType~(~&#39;page~&#39;post~&#39;aa_book~&#39;aa_event_session~&#39;aa_experience_report~&#39;aa_glossary~&#39;aa_research_paper~&#39;aa_video)~tags~(~&#39;story*20mapping))~searchTerm~&#39;~sort~false~sortDirection~&#39;asc~page~1)">What is Story Mapping?</a></li></ul><h3>Next steps in part III…</h3><p>All about user stories &amp; how to write awesome acceptance criteria.</p><p><strong>Thanks for reading! <br>Clap</strong> 👏 — please show if you like this article so others can find it.<br><strong>Respond </strong>💬 — please let me know if you have any suggestions or questions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f33db2b566da" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/transitioning-from-quality-to-product-management-pt-2-f33db2b566da">Transitioning From Quality to Product Management — pt 2</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Product Manager vs. Product Owner. Is there a real difference?]]></title>
            <link>https://arteyescas.medium.com/product-manager-vs-product-owner-is-there-a-real-difference-438f4fda1a2a?source=rss-5704a6d8bdde------2</link>
            <guid isPermaLink="false">https://medium.com/p/438f4fda1a2a</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[product-manager]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile-teams]]></category>
            <dc:creator><![CDATA[Artemisa Yescas]]></dc:creator>
            <pubDate>Tue, 26 Jan 2021 17:18:04 GMT</pubDate>
            <atom:updated>2021-01-26T17:29:38.558Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*lsTzc1iKiHdGXdPeWGttqA.jpeg" /></figure><p>Many people in tech use these terms interchangeably but I would definitely not use them this way. The best way to identify the differences between a Product Manager and a Product Owner is to identify their responsibilities and analyze what is their focus:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vzJAEaBsYK1oSRhjxNiBLA.png" /></figure><p>For the <a href="https://www.scaledagileframework.com/product-owner/">Scaled Agile approach (SAFe)</a> specifically, we have a slight change:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/970/0*MCJBvo5UB5GpkKro.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/917/0*1gOnH_MjV6d4hZp_.png" /></figure><p>We may see some responsibilities overlap between the two roles, such as:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*S2dtP77NQeWtZZQ5oeoR5Q.png" /></figure><blockquote>You might say that PM and PO roles sometimes overlap. Well, yes, there IS a certain overlap between the product manager’s strategic activities and the product owner’s tactical activities. This indicates a need for collaboration and communication between the people who hold these roles. The tactical decisions should reflect the overall strategy and the overall strategy is generally affected by the circumstances that the development team faces. <br> <a href="https://medium.com/u/7da6bb46f7b0">Anna Aria</a> —<a href="https://medium.com/hackernoon/product-owner-vs-product-manager-who-is-the-boss-7497b63e42f6"> Hackernoon</a></blockquote><p>But whatever the approach used, basically the Product Manager is going to be <strong>customer-focused</strong> and the Product Owner would be <strong>team-focused</strong>.</p><p>And let’s remember that both the product manager and the product owner will always need to work towards a common goal — to build &amp; improve products that create meaningful value for customers and all stakeholders within the company.</p><h4>If you enjoyed this story, please click the 👏 button and share to help others find it! Feel free to leave a comment below. Thanks!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=438f4fda1a2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Transitioning from Quality to Product Management — pt 1]]></title>
            <link>https://arteyescas.medium.com/transitioning-from-quality-to-product-management-pt-1-cb67c169d8df?source=rss-5704a6d8bdde------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb67c169d8df</guid>
            <category><![CDATA[transitions]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Artemisa Yescas]]></dc:creator>
            <pubDate>Thu, 21 Jan 2021 21:53:17 GMT</pubDate>
            <atom:updated>2021-01-21T21:53:17.110Z</atom:updated>
            <content:encoded><![CDATA[<h3>Transitioning from Quality to Product Management — pt 1</h3><h4>Establishing a syllabus</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gLNUuUNZCVma-yiRsobbgA.jpeg" /></figure><p>To give you a little context, I have been in software development for more than a decade and my roles have been developer, QA, and QA lead. A few months ago, as my QA manager was preparing for his retirement, he mentioned how he could see me going forward into product management. Note that I have been working under his wing for eight years and during that time we overcome many challenges so I valued his opinion. This was an idea that I kept in the back of my head, but it resurfaced when the new QA manager (another person I have worked with for many years) mentioned this too. So I took the scary but empowering decision to leave my client and role to pursue training for the PM/PO role in my current company. Currently, I am also being part of the effort to create a role syllabus — which is very exciting!</p><p>As a QA Lead, I felt a natural evolution towards the Product Owner/ Product Manager world. I had to deal with project management on some level: from making sure all parties align, having small interactions with devs to verify the built features consistency versus the specifications, up to having meetings to clarify lessons learned. With a QA background, we can contribute and collaborate by,</p><ul><li>Being a great advocate for the user. QA has an intimate knowledge and understanding of the product–its goals, requirements, and roadmap.</li><li>Having the eye for details and quality perspective on processes, workflows, and procedures.</li><li>Providing testing documentation experience necessary to write better requirements documentation.</li><li>Sharing constructive suggestions and feedback on how to improve or even evolve the product.</li></ul><p>Taking into consideration that I am a trainer in Practitioner in Agile Quality certification, I already have covered the Agile knowledge needed for the PM/PO role. It’s always good to go over the related topics to refresh that knowledge. Let’s remember who the PO is and what are their responsibilities, according to the Scrum guide:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/874/1*5JL0Rer_u8-1DcD0d9ckng.png" /><figcaption><a href="https://www.scrumguides.org/scrum-guide.html">https://www.scrumguides.org/scrum-guide.html</a></figcaption></figure><p>To have a complete perspective of all the subjects necessary for a project manager, during the holidays I took a course in project management for beginners directed by the PM institute. This is an introductory course that provides the foundational knowledge necessary to join a project team and can serve as the first step on your path to a project management career:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/843/1*2u4ZhsiI_ZOft3ALY7jX6Q.png" /><figcaption>Project Management for Beginners — <a href="https://my.pmi.org/">https://my.pmi.org/</a></figcaption></figure><p>Aligned to what my company expects from the PM/PO role, these are the resources I had to study and I hope they are useful to you:</p><h4><a href="https://www.amazon.com/User-Story-Mapping-Discover-Product/dp/1491904909/ref=as_sl_pc_qf_sp_asin_til?tag=jefpatass-20&amp;linkCode=w00&amp;linkId=NX2UXYQEFAANOFPO&amp;creativeASIN=1491904909">Jeff Patton’s User Story Mapping</a></h4><p>This book is a jewel, I recommend reading it all.</p><h4><a href="https://www.amazon.com/-/es/Mike-Cohn/dp/0321205685/ref=sr_1_2?__mk_es_US=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;dchild=1&amp;keywords=Mike+Cohn%27s+User+Stories&amp;qid=1610730886&amp;s=books&amp;sr=1-2">Mike Cohn’s User Stories Applied</a></h4><p>- Gathering stories<br>- Acceptance testing <br>- Guidelines for good stories</p><h4><a href="https://www.amazon.com/-/es/Aswin-Pranam-ebook/dp/B0787T85J6/ref=sr_1_1?__mk_es_US=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;dchild=1&amp;keywords=Product+Management+Essentials+-+Tools+and+Techniques+for+Becoming+an+Effective+Technical+Product+Manager+-+Aswin+Pranam&amp;qid=1610730939&amp;s=books&amp;sr=1-1">Product Management Essentials — Tools and Techniques for Becoming an Effective Technical Product Manager — Aswin Pranam</a></h4><p>- Difference between Product Manager/Project Manager/Program Manager<br>- Product Requirement Document<br>- Product Roadmap<br>- Roles/Artifacts</p><h4><a href="https://www.amazon.com/-/es/Matt-LeMay/dp/1491982276/ref=sr_1_1?__mk_es_US=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;dchild=1&amp;keywords=Product+Management+in+Practice%3A+A+Real+World+guide+to+the+key+connective+role+of+the+21st+century+-+Matt+Lemay&amp;qid=1610731031&amp;s=books&amp;sr=1-1">Product Management in Practice: A Real World guide to the key connective role of the 21st century — Matt Lemay</a></h4><p>- Guiding questions to help you get started with creating a clear sense of how an organization intends to use its roadmap.<br>- Core skills of PM<br>- Assumptions<br>- Rather than being accountable for hitting specific metrics, PMs can seek to be held accountable for…<br>- Impact-vs-Effort Matrix<br>- Official process/template for handling last-minute requests or “emergency” feature requests</p><h4><a href="https://www.amazon.com/-/es/Don-McGreal/dp/0134686470/ref=sr_1_1?__mk_es_US=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;dchild=1&amp;keywords=The+Professional+Product+Owner%3A+Leveraging+Scrum+as+a+Competitive+Advantage+-+by+Don+McGreal&amp;qid=1610731164&amp;s=books&amp;sr=1-1">The Professional Product Owner: Leveraging Scrum as a Competitive Advantage — by Don McGreal</a></h4><p>- Different layers of planning, the product mgmt. vacuum<br>- Business model canvas<br>- Comparison of delivery and owner metrics<br>- Happiness index<br>- Radar graphs for visualizing progress over time<br>- Scoreboard to organize metrics<br>- Build-Measure-Learn feedback loop<br>- How to measure the uncertainty of an environment<br>- From Scrum Guide: Product owner’s role, Scrum team, Product backlog, Refinement, Sprint backlog, Sprint Planning, Sprint Review, Retrospectives)<br>- Requirement categories <br>- What defines the quality of your user story?<br>- Acceptance criteria<br>- How to order product backlog<br>- How to measure value, risk, size<br>- List of “done” elements/”Done” template for multiple teams working on one product. <br>- Story Mapping<br>- Release Management<br>- Estimation &amp; velocity<br>- Mapping T-shirt sizes to Points</p><h4><a href="https://plan.io/blog/user-story-mapping/#let-s-start-with-the-basics-what-are-user-stories-and-user-story-examples">Plan.io</a></h4><p>A Guide to User Story Mapping: Templates &amp; Examples (How to Map User Stories)</p><h4><a href="https://alistapart.com/article/object-oriented-ux/">Object-Oriented UX</a> by Sophia V. Prater</h4><h4><a href="https://www.rewiredux.com/ooux">OOU — The ORCA process</a> by Rewired UX</h4><h4><a href="https://medium.com/@adamedgerton/full-stack-basics-for-the-non-developer-cead94f9f4a6">Full Stack Basics for the Non-Developer</a> by Adam Edgerton</h4><h4><a href="https://louderthanten.com/resources/risk-management">Risk Management </a>by Louder Than Ten</h4><p>Red flag &amp; risk assessment checklist, Scope Creep guide</p><h4><a href="https://www.youtube.com/watch?v=lKcJW1XqY4E">Project Management Scope Creep: 7 Top Tips To Prevent It! </a>(video) by Projectmanager.com Director Jennifer Bridges</h4><h4><a href="https://www.amazon.com/-/es/Harold-Kerzner/dp/1119385970/ref=sr_1_3?__mk_es_US=%C3%85M%C3%85%C5%BD%C3%95%C3%91&amp;dchild=1&amp;keywords=PROJECT+MANAGEMENT+CASE+STUDIES+-+Harold+Kerzner&amp;qid=1610732073&amp;sr=8-3">Project Management Case Studies — Harold Kerzner</a></h4><ul><li>Chapter 21 Agile/Scrum Project Management</li></ul><h3>Next steps in part II…</h3><p>Practical exercises covering User Story Mapping and User Story creation.</p><p>Let me know if you have any tips and tricks for this type of process I am going through. :)</p><h4>If you enjoyed this story, please click the 👏 button and share to help others find it! Feel free to leave a comment below. Thanks!</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb67c169d8df" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[For the X time, happiness is not about smiling]]></title>
            <link>https://arteyescas.medium.com/for-the-x-time-happiness-is-not-about-smiling-4a581966a268?source=rss-5704a6d8bdde------2</link>
            <guid isPermaLink="false">https://medium.com/p/4a581966a268</guid>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[life-lessons]]></category>
            <category><![CDATA[happiness]]></category>
            <category><![CDATA[office-culture]]></category>
            <dc:creator><![CDATA[Artemisa Yescas]]></dc:creator>
            <pubDate>Wed, 20 Jun 2018 00:43:16 GMT</pubDate>
            <atom:updated>2018-06-20T00:44:37.584Z</atom:updated>
            <content:encoded><![CDATA[<p>Our definition of happy isn’t very good</p><blockquote>“Why aren’t you smiling? Aren’t you happy? Is there something wrong?”</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*FiA9g3oAbdtclypv5cSmnA.jpeg" /></figure><p>These are questions that I hear very often and make me feel terribly annoyed. We don’t really know <a href="https://hbr.org/2015/07/the-research-weve-ignored-about-happiness-at-work">what happiness is</a> or how to <a href="https://hbr.org/2015/07/the-research-weve-ignored-about-happiness-at-work">measure it</a>. Just a smile could easily mean 20 different emotions. Personally, being “happy” at my job involves feeling engaged, meaningful, pleasant and comfortable in my working environment. Feeling good about my daily routine. There are ways to be this kind of happy at work and it doesn’t take much from ourselves to put them in practice.</p><h3>What do you like about your job? If you’re not sure, try to think of a good day of work you had recently.</h3><p>Being <strong>engaged</strong> at work isn’t as simple as “being happy”. It involves many factors around this concept. What can we do to make sure our imaginary great day takes place? Yup:</p><h4>Face your demons</h4><p>Let me speak to small audiences and I will entertain everybody and have lots of fun. But with big audiences, this is a different story. I get very nervous and anxious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/395/1*JOyBz-m7VgTCjXi9u5zzhg.jpeg" /></figure><p>I realized the only way to deal with this issue is PRACTICE, confronting the problem, straight upfront. I still get nervous, but I am getting better at controlling it. I have also experienced that this same tactic applies for many other cases. In reality if you don’t take the bull by its horns, problems will stay there, dormant, very comfortable hibernating with you. The possibility to improve relies directly in your hands.</p><h4>Share a treat with a coworker (A.K.A La Hora Gordita)</h4><p>We might think interaction with coworkers outside our job tasks is something trivial and unimportant, but in the contrary: this kind of social behavior supports bonding and building better relationships between teams.</p><p>It can be something as informal as “<em>La Hora Gordita</em>”. In the QA team I currently work with, we used to have The Fatty Hour (which wasn’t really an hour, just a break). Its purpose was basically having a <a href="http://www.lovethispic.com/uploaded_images/169061-Chocoflan-Recipe.jpg"><strong>sinful</strong></a> treat while we relaxed for a bit and just joke around or talk about the latest box office movie, our next Team Building event’s location or complain about something random.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/1*9PAi1d1_-hEP6m8dmo0Djg.png" /></figure><h4>Don’t use a checklist. Instead think about accomplishments.</h4><p>Checklists from hell become an endless source of things that need to be done. Instead of strictly following this list, focus on the continuous progress and you will feel satisfied about the results that are being achieved.</p><p>Likewise, be prepared to accept failure and learn from your mistakes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*98AumQxvUFL8yB0wsrPOcQ.png" /></figure><h4><em>Stop the mechanical, boring routine.</em></h4><p>In my case, I take care of my mood by starting my day exercising. At work, when I get a sense of weariness, I try to stir things up by changing the original order of tasks I had planned or use a different tool than the one I am accustomed to.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*QfUI3yzEtlMdHFdBBHV1tg.jpeg" /></figure><p>There are other ways like taking breaks:<br>- to play a videogame<br>- check social media <br>- breath and appreciate the landscape</p><p>The important thing is to break the pattern by taking care of your mood.</p><h4>Master the ancient art of saying NO</h4><p>There have been many times when someone has requested something from me at the worse time possible and my answer has been: <em>“hmm, yeah, I am busy right now but sure, I will help you”</em>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/429/1*kKpR2mPuOndXzKceUZS63g.jpeg" /></figure><p>That <em>sure</em> transformed into workload that consumed a lot of time, shifting everything in my calendar. I am not the kind of person that commits to something and doesn’t finish it, so even though I was able to help with this unexpected task and complete my daily activities, I ended up staying late and working more hours to be able to finish with everything. When this type of behavior is recurring, we end up burning ourselves.</p><p>Instead I should have declined and said something like: <em>currently I am not able to commit but here’s what I can do […] or we can reschedule.</em> This doesn’t mean we have to over-explain but we need to be honest about our situation.</p><p>You can be a kind, gentle person and still say NO. It is CRUCIAL learning to say no because being able to say it means that we have awareness of what our limits are. Don’t lie. Just say no.</p><h4><strong>Staying humble</strong></h4><p>Remember that no matter how good you are at what you do, you are not indispensable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/610/1*Tp1an57xuJeJKrRZ-h6YCQ.png" /></figure><p>Be comfortable with imperfection.</p><blockquote><a href="https://www.ted.com/talks/martin_seligman_on_the_state_of_psychology?language=es">Real happiness comes from finding meaning in what you do.</a></blockquote><p>Being happy at work means that I have a sense of purpose within my job. At the end, we are the ones with the responsibility and choice of <strong>#CodingOurOwnHappiness.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/200/1*k6NqWKD2BOemeJEbeec8eg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/725/1*emxDrmtEiMy6h5JXecj-Og.gif" /><figcaption>Found this post useful? Kindly tap the ❤ below to recommend it to other interested readers!</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4a581966a268" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[¿Estamos haciendo suficiente por la inclusión de Mujeres en la Tecnología?]]></title>
            <link>https://medium.com/nearsoft-jobs/estamos-haciendo-suficiente-por-la-inclusi%C3%B3n-de-mujeres-en-la-tecnolog%C3%ADa-8fcedae68ea9?source=rss-5704a6d8bdde------2</link>
            <guid isPermaLink="false">https://medium.com/p/8fcedae68ea9</guid>
            <category><![CDATA[nearsoft]]></category>
            <category><![CDATA[mujeres]]></category>
            <category><![CDATA[comunidad]]></category>
            <category><![CDATA[tecnología]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Artemisa Yescas]]></dc:creator>
            <pubDate>Wed, 19 Apr 2017 20:19:28 GMT</pubDate>
            <atom:updated>2017-09-04T21:42:10.794Z</atom:updated>
            <content:encoded><![CDATA[<p>Todavía estamos lejos de alcanzar un número ‘balanceado’ de mujeres en la tecnología. Hoy en día, sólo el <a href="https://www.ncwit.org/sites/default/files/resources/womenintech_facts_fullreport_05132016.pdf">25% de las ocupaciones informáticas del mundo son ocupadas por mujeres</a>. Imaginemos el porcentaje para un país latinoamericano, donde nuestras tecnologías están emergiendo y la posibilidad de estudiar cualquier tema relacionado con la tecnología desde una edad temprana es prácticamente inexistente.</p><blockquote>Un dato de “viejo” trasfondo: En el 2003, cuando estudié Ciencias de la Computación, sólo el 10% éramos mujeres. Más adelante en 2014, durante mi grado de Maestría éramos aproximadamente 20–25%.</blockquote><p>ESTAMOS haciendo algo al respecto, estamos mejorando. Pero necesitamos más. Necesitamos continuar con el esfuerzo de llevar nuestro mensaje a cada esquina. Afortunadamente debido a las redes y la conectividad somos capaces de vincularnos con otras personas y crear comunidades. Cada vez más personas están involucrándose en el movimiento de mujeres en la tecnología y podemos notar su crecimiento <em>online</em>.</p><p>Desde que nacemos, hay una fuerte inclinación para diferenciar entre géneros: Lego y ciencia para niños, muñecas y electrodomésticos para niñas. Recientemente se ha encontrado que <a href="http://www.slate.com/articles/health_and_science/new_scientist/2014/04/girl_and_boy_toys_childhood_preferences_for_gendered_toys_are_not_innate.html">el sesgo de género no es innato, es algo que se enseña</a>. Entonces, ¿por qué las cosas siguen así? ¿Por qué las niñas y los niños no pueden ser criados de la misma manera?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vSv9EBkcOVJBOg0SglQMlQ.png" /></figure><p>Personalmente creo que la clave se encuentra en ese temprano momento de nuestras vidas. Acercar a las niñas a la tecnología desde el principio. ¿Recuerdas cómo era antes? Los niños aspiraban a ser bomberos, médicos, abogados, constructores o astronautas … porque esas eran las opciones disponibles y promovidas. Ahora los niños también deben saber que pueden convertirse en programadores, <em>testers, product owners, technical recruiters</em>, bio-ingenieros si así lo eligen … y esta orientación comienza no sólo en las escuelas, sino también por influencia directa de los padres o su entorno cercano. Hay una impresionante variedad de carreras profesionales y oportunidades estudiantiles en la tecnología y para apoyar su desarrollo, algo que es realmente fácil en nuestras posiciones, es facilitar el acceso a su conocimiento y herramientas.</p><blockquote>En la industria de alta tecnología, la <a href="https://www.ncwit.org/sites/default/files/resources/womenintech_facts_fullreport_05132016.pdf">tasa de abandono</a> es <strong>dos veces más alta </strong>para las mujeres que para los hombres:<br><strong>41% para Mujeres<br>17% para Hombres</strong></blockquote><p>Es fundamental tomar conciencia de que la clave también implica mantener a las niñas interesadas en la tecnología mientras crecen y cuando comienzan en sus primeras experiencias laborales. Actualmente hay enormes esfuerzos de las empresas que están dando talleres y charlas enfocadas a las mujeres jóvenes que cada vez se acercan más a la tecnología. Necesitamos esa visibilidad y apoyo porque muchas veces cuando llegas “allí”, cuando ya tienes un lugar en la tecnología, te enfrentas a muchos desafíos y obstáculos que quizás te pueden desanimar de continuar ese camino. Es por eso que la comunidad es tan importante; tener una red de seguridad fuerte puede funcionar como una guía.</p><p>Algunos de los esfuerzos que estamos haciendo en <a href="http://www.nearsoft.com/">Nearsoft</a>, en gran parte provienen de compañeros que apoyan activamente la inclusión de las mujeres en la tecnología. Por ejemplo, <a href="https://djangogirls.org/foundation/">Django Girls</a>, una organización sin fines de lucro y una comunidad que empodera a las mujeres organizando talleres de programación gratuita de un día, proporcionando herramientas, recursos y apoyo, se ha logrado celebrar en nuestras instalaciones de Ciudad de México, Hermosillo y Chihuahua durante 2015 y 2016. Varios de nuestros programadores han sido mentores de estas jóvenes.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BnP4lEi0-pXkgmIWFEwUPw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C4kABPfAaRxshg2GlvyO6g.png" /></figure><p>También estamos apoyando a comunidades locales como <a href="http://www.epicqueen.com/about.html">Epic Queen</a>, cuya misión es cerrar la brecha de género en tecnología.</p><p>Inspirados en el <em>Twitter hashtag</em> <a href="https://medium.com/startup-grind/ilooklikeanengineer-one-year-later-b599e0cae817"><em>#iLookLikeAnEngineer</em></a> que <a href="https://medium.com/@isisAnchalee?source=post_header_lockup">Isis Anchalee</a> compartió en 2015 y que dio origen a una campaña propia convirtiéndose en una fuente para la construcción de la comunidad, hemos iniciado nuestro propio movimiento. Éste además de usar el <em>hashtag</em>, incluye la bio de las ingenieras y detalles sobre su entrada al mundo de la tecnología . El <em>post</em> de cada ingeniera se publica semanalmente.</p><p>Estoy muy contenta de haber impulsado este movimiento en nuestra empresa porque ha tenido una bienvenida positiva y ha tenido resultados muy interesantes. He encontrado cosas sobre estas ingenieras —cabe destacar que convivo en la misma compañía— ¡que yo no sabía! Caí en cuenta de cosas como: “¡Oh, así es como yo empecé!”, “ah, mira, tengo la misma educación” o “¡Tengo los mismos intereses y aficiones!”. Esto me da una perspectiva diferente de su viaje personal y su camino hacia la tecnología; la verdad es que he llegado a valorar mucho el camino de cada individuo.</p><p>Todo esfuerzo es muy, muy apreciado. Les animo a que aprovechen oportunidades como conferencias, eventos, talleres, etc. para su beneficio, estableciendo redes y conociendo más a fondo a las mujeres que presentan sus historias y su trabajo exitoso / no exitoso.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CXOly4rimjELKxG3wY7Lyw.jpeg" /><figcaption>Mujeres empoderadas, empoderan a otras mujeres. Via: <a href="https://ithelpstodream.tumblr.com/post/156145942921">https://ithelpstodream.tumblr.com/post/156145942921</a></figcaption></figure><h4>Si disfrutaste de esta historia, por favor dale click al botón 👏 y compartela para que otros la lean.</h4><p><strong><em>Artemisa Yescas Engler, Software Quality Engineer @Nearsoft.</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8fcedae68ea9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/nearsoft-jobs/estamos-haciendo-suficiente-por-la-inclusi%C3%B3n-de-mujeres-en-la-tecnolog%C3%ADa-8fcedae68ea9">¿Estamos haciendo suficiente por la inclusión de Mujeres en la Tecnología?</a> was originally published in <a href="https://medium.com/nearsoft-jobs">Nearsoft Jobs</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are we doing enough for Women-In-Tech movement?]]></title>
            <link>https://arteyescas.medium.com/are-we-doing-enough-for-women-in-tech-movement-62e1c4f2da52?source=rss-5704a6d8bdde------2</link>
            <guid isPermaLink="false">https://medium.com/p/62e1c4f2da52</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[computer-science]]></category>
            <category><![CDATA[gender-equality]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[Artemisa Yescas]]></dc:creator>
            <pubDate>Wed, 19 Apr 2017 16:53:36 GMT</pubDate>
            <atom:updated>2017-09-04T21:32:57.862Z</atom:updated>
            <content:encoded><![CDATA[<p>We are still very far away from equality of women in technology. Today, only <a href="https://www.ncwit.org/sites/default/files/resources/womenintech_facts_fullreport_05132016.pdf">25% of the world’s computing occupations are held by women</a>. In Latin America, technology education is emerging and the possibility of studying any technology related topic from an early age is practically non-existent.</p><blockquote>A bit of an “old” background: 2003, when I studied computer science, only 10% were women; later in 2014, during my masters degree we were roughly 20–25%.</blockquote><p>We ARE doing something about it. But we need more. We need to continue taking our message to every corner. Thankfully due to networking we are able to connect to others and create a community. It is incredible to see how the women in tech movement is growing online.</p><p>Since we are born, there’s a strong advocacy to differentiate between genders: Lego and science for boys, and doll houses for girls. Recently it’s been found that <a href="http://www.slate.com/articles/health_and_science/new_scientist/2014/04/girl_and_boy_toys_childhood_preferences_for_gendered_toys_are_not_innate.html">gender bias is not innate</a>, it’s something that is taught. Then why do we continue doing it?</p><p>Why can’t girls and boys be raised the same way?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vSv9EBkcOVJBOg0SglQMlQ.png" /></figure><p>Kids would aspire to be firefighters, doctors, lawyers, and astronauts. Now kids should also know that they can become programmers, testers, project managers, scientific researchers if they choose to. This must start not only in schools, but from parents and family, too.</p><p>It is really easy for us to facilitate their access to knowledge and tools. Currently there are huge efforts by companies to support this. They are sponsoring workshops and talks focused on young women who are increasingly approaching technology.</p><p>There still a lot of work ahead because many times after women get “there,” they face many challenges and obstacles. That is why the community is so important, having a strong safety net that can operate as a guide.</p><h4>What We Are Doing</h4><p>We have great colleagues at <a href="http://www.nearsoft.com/">Nearsoft</a> who actively support inclusiveness of women in tech. For example, they host Django Girls meet ups. This is a <a href="https://djangogirls.org/foundation/">non-profit organization</a> and a community that empowers and helps women to organize. They hold free, one-day programming workshops that provide tools, resources, and support. These have been hosted in Mexico City, Hermosillo, and Chihuahua sinc 2015. Several of our programmers have been mentors to these girls and women.</p><p>We are also supporting local communities like <a href="http://www.epicqueen.com/about.html">Epic Queen</a>, which mission is closing the gender gap in technology.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BnP4lEi0-pXkgmIWFEwUPw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wlzaRzrqujX4mXrrnNyAqw.png" /></figure><p>The Twitter hashtag <a href="https://medium.com/startup-grind/ilooklikeanengineer-one-year-later-b599e0cae817">#iLookLikeAnEngineer</a> that <a href="https://medium.com/@isisAnchalee?source=post_header_lockup">Isis Anchalee</a> shared in 2015 gave birth to a campaign of its own and became a source of community building. We are supporting this movement by promoting our engineer’s bio and their path into technology. I am very happy to have started this at our company. And it’s had some surprising results.</p><p>I have found stuff about these engineers that I didn’t knew about — even though I work with them every day. Things like, “oh, that is how I started!”, “I have the same educational background” or “I have the same interests and hobbies!” This gives me a different perspective on their journeys and personalities. I have come to value each individual’s road.</p><p>Every effort is highly appreciated. I encourage all of you to use opportunities like conference, events, workshops, etc. to network. Find out more about the women giving presentations and the other just hanging around. Discover their stories and their triumphs and obstacles at work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CXOly4rimjELKxG3wY7Lyw.jpeg" /><figcaption>via: <a href="https://ithelpstodream.tumblr.com/post/156145942921">https://ithelpstodream.tumblr.com/post/156145942921</a></figcaption></figure><h4>If you enjoyed this story, please click the 👏 button and share to help others find it! Feel free to leave a comment below.</h4><p><strong>Artemisa Yescas Engler, <em>Software Quality Engineer </em></strong><em>@ </em>Nearsoft, Inc.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=62e1c4f2da52" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Being remote is wonderful]]></title>
            <link>https://arteyescas.medium.com/being-remote-is-wonderful-521c82bff7e8?source=rss-5704a6d8bdde------2</link>
            <guid isPermaLink="false">https://medium.com/p/521c82bff7e8</guid>
            <category><![CDATA[remote-working]]></category>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[wfh]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[distributed-teams]]></category>
            <dc:creator><![CDATA[Artemisa Yescas]]></dc:creator>
            <pubDate>Fri, 21 Oct 2016 00:35:39 GMT</pubDate>
            <atom:updated>2017-09-04T21:33:54.317Z</atom:updated>
            <content:encoded><![CDATA[<h4>HMM, AND IT ALSO SUCKS!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/344/1*7N1eBLhBWDDOidrknQ-1zg.png" /></figure><h4>YOU BECOME A MYTHOLOGICAL CREATURE</h4><p>Or worst case scenario… you are forgotten. It is really difficult to keep up with growing teams. When I started in Nearsoft we were around 50 people, now we are almost 250. Currently, our newbies could say: “Ah, yeah… Artemisa, she’s the first nearsoftian to use the #StudyRemote campaign, but I have never seen her”, and they can probably identify me by one or two things that I have contributed which are visible in our offices. But that’s it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/349/1*WM3I2cM5um_V0tn04ZWjcA.png" /><figcaption>BEWARE BUGS, I AM COMING FOR ALL OF YOU!</figcaption></figure><p>So, we can’t just sit back and relax. There are new faces, new people to meet and with whom you can create new bonds. But this depends entirely on the remote person’s will to be known by others.</p><h4>COMMON MISCONCEPTION OF WFH</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/1*8SkRSsGfpRS4m4UqbktIHQ.png" /></figure><p>NOPE. This is not what I search for all day long. Believe it or not, I <strong>AM</strong> working :D.</p><h4>LONELINESS EVENTUALLY GETS YOU</h4><p>I believe working remotely for around a year is still healthy — and obviously sparsely too. But, I am going to fulfill 3 years working remotely and it becomes dull, especially if you relocate alone to a new city. The shiny and mesmerizing new things dissipate. If you’re alone, you miss your family and friends, time zone difference affects communication with them, you can’t make it to personal events, etc. In the other hand, if you have kids or other people living with you, there can be times where they are constantly around your <em>workspac</em>e and this could be a little maddening and could alter your concentration #PersonalSpaceInvasionAlert.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/433/1*Os_96D5Zypw7YCwKqJib5A.png" /></figure><p>I truly started to miss simple interactions like small talk &amp; coffee with coworkers during short breaks, the ability to go to your teammate’s desk and show him that issues in his code are causing a weird scenario :P, even leaving my house and commuting to work.</p><h4>YOU THINK YOU NEED TO PROVE YOURSELF A LITTLE BIT MORE</h4><p>I mean, it’s awesome that we can push ourselves a little bit more every day, but in our own solitary bubble we start thinking that maybe our effort is not that visible, we start questioning why we haven’t been recognized and we start to increase our working hours. It is very easy to blur the office hours when you’re at home. We have to be very strict about timings or else we can fall into harmful patterns.</p><h4>LAST ONE TO LEARN OFFICE GOSSIP</h4><p>Wait, wait. It may sound a bit frivolous. But harmless gossip as:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*w_bSG06Lo0jGCj0lEVZzLQ.png" /></figure><p>is trivial stuff that you end up missing. We end up losing office camaraderie because there are events which are dependable of our physical presence. <em>“Oh, wow. John brought free donuts for everyone, he’s awesome!”</em></p><h3>ALRIGHT, WHAT CAN WE DO TO IMPROVE?</h3><h4>COMFORTABLE DESIGNATED OFFICE SPACE</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bps5xcEvJNhu-xj2exjvTQ.png" /><figcaption>I want to stand and work, I can. I want to sit and work, I can.</figcaption></figure><h4>STATUS, STATUS, STATUS!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2bIWJtF21b-iaW_wkgzupQ.png" /><figcaption>Continuous and clear communication is the key!</figcaption></figure><h4>DON’T BE INVISIBLE, BE AVAILABLE</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LGZgGu4TONVhMS4eC9apyw.png" /></figure><h4>FIND A PLACE TO BE PRODUCTIVE — OUT OF THE HOUSE!</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*n4TTAIqr4DIPtX_OkBeahA.png" /><figcaption>I can work anywhere if I have WiFi and Coffee!</figcaption></figure><h4>EXPERIMENT AND BREAK THE CYCLE</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YrJrSQuTWiRm_FgRyF_38A.png" /><figcaption>You will become an eggplant if you don’t exercise! Smashing bugs doesn’t qualify as exercise, ok?</figcaption></figure><h4>GET CONSTANT FEEDBACK</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yb40uCxXtMDnwCfmbxpCrQ.png" /></figure><h4>MAINTAIN TEAM CULTURE</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LrH5zT1Wp1C17vsGYQVo1w.png" /><figcaption>Team building, woooooh!</figcaption></figure><p>At the end, it is a combination of three holy, mystical factors:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ric15CEFYKaUpKNGEN7ziA.png" /></figure><p>And remember,</p><ul><li>It isn’t always easy.</li><li>It isn’t for everyone.</li><li>It is only a drag if you let it be a drag.</li></ul><h4>BONUS Recommendations:</h4><ul><li>Keurig Coffee Maker for 1 Cup</li><li>Healthy snacks: apples, nuts &amp; seeds, veggie chips, tea, etc.</li><li>Productivity techniques like <a href="http://pomodorotechnique.com/">Pomodoro</a>, <a href="http://gettingthingsdone.com/">Get Things Done</a>, etc.</li><li><a href="https://justgetflux.com/">f.Lux</a>: makes the color of your computer’s display adapt to the time of the day, warm at night and like sunlight during the day.</li><li><a href="http://soundrown.com/">Soundrown</a>: Relax. Focus. Escape.</li><li><a href="http://everytimezone.com/">Every Time Zone</a> clocks</li></ul><h4>If you enjoyed this story, please click the 👏 button and share to help others find it! Feel free to leave a comment below.</h4><p><strong>Artemisa Yescas Engler, <em>Software Quality Engineer </em></strong><em>@ </em>Nearsoft, Inc.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=521c82bff7e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sharing Agile knowledge with experienced testers]]></title>
            <link>https://arteyescas.medium.com/sharing-agile-knowledge-with-experienced-testers-c9380193c26e?source=rss-5704a6d8bdde------2</link>
            <guid isPermaLink="false">https://medium.com/p/c9380193c26e</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[team]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[testing]]></category>
            <dc:creator><![CDATA[Artemisa Yescas]]></dc:creator>
            <pubDate>Fri, 14 Oct 2016 22:13:43 GMT</pubDate>
            <atom:updated>2017-09-04T21:34:27.515Z</atom:updated>
            <content:encoded><![CDATA[<h4>… and not boring them into oblivion.</h4><p>Last month, I had the opportunity to teach the first <strong>iSQI® Certified Agile Tester️ </strong>training in México and very proudly at @Nearsoft headquarters where I currently work as a Software QA Engineer. It’s been quite a long road to reach this point, with obstacles along the way but it has been taught and trainees have taken the exam… yay (whew)!</p><h4>SOME BACKGROUND</h4><p>What’s the big fuzz about this training? Well, there are many training programs out there for<em> </em>developers, but for testers the scene is a little limited; likewise we must choose the right option based on specific objectives. After a lot of talks with a fellow QA about training options, I became interested especifically in CAT because it is <strong>not</strong> a foundation course, it is built around Agile (the majority of our projects use Agile practices) and it focuses on the most important element in Agile projects, each member of the team.</p><p>Let’s remember that the key to success in Agile projects strongly relies on individuals able to collaborate and self-manage and when rigid guidelines are exchanged for dynamic, constantly changing, communication-rich environments, a common language is a <strong><em>must</em></strong><em>. </em>Another positive attribute of this course is that it focuses on practical exercises and a hands-on approach, so it’s constantly changing the game.</p><h4>THE TRAINEES</h4><p>The group consisted of six Software QA Engineers with the following characteristics:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LjN6ryf7q4dH8pu5wm1w7A.png" /><figcaption>Note: this are averages.</figcaption></figure><p>As you can read, these engineers are quite competent and proficient in different projects and roles. This was very useful while teaching because they were able to contribute with their own experiences and generated rich discussions around the topics and issues explored.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jljKa9o3X-iHMztL50S7MQ.png" /></figure><h4>DYNAMICS AND COURSE OUTLINE</h4><p>We all know how continuous theory is dull and tiresome. Therefore, group discussions were encouraged at regular intervals. Also, the practical parts, were fun because the teams at first were very confident on their knowledge and experience <em>but</em> they had to deal with strict timeboxed periods. This caused surprise and sometimes frustration on the results they were obtaining at the end of each practical.</p><p>The trainees were able to relate to many of the subjects seen and were able to provide their own experiences to the group. For example, in <em>Version Management</em> sub-topic, we all shared stories about fixes being deployed to the wrong branch, or while going through <em>Pairing, </em>we discussed how can we use this technique with other roles than the common pair consisting of developer+developer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_wMp6ERVTKUa3BkDl_nO4w.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J9nJhgLyj9aNG1INw_9PAw.png" /></figure><h4>INTERESTING RESULTS</h4><blockquote>“Life is an Iteration Zero” <br>- J. García, C. Ramirez, 6/Oct/2016</blockquote><p>In the feedback session, I was impressed to find that Iteration Zero is <em>THE </em>topic, standing out amongst top important topics for the trainees. They were able to discover the real value of it during the practical activities and even personal quotes around the matter were established along training days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/822/1*C5PkXwoKI55qgHaQm_u5dg.png" /></figure><p>Other subjects in top five positions were Estimations, Planning, Definition of Done and Technical/Testing Debt.</p><p>Trainees were able to understand the principles behind the Agile approach to development of software and they clearly differentiate the testing role in traditional and Agile projects.</p><p>Relevant aspects that were consolidated:</p><ul><li>Appreciation of challenges and difficulties that come hand in hand with the activities that don’t involve testing in an Agile team</li><li>Proper acknowledge of a soft skills spectrum required by <strong>all</strong> the team.</li><li>The awareness of great value that a process like <em>Retrospectives</em> can give in return and how their adequate contributions to it will allow continuous improvement.</li><li>Importance of <em>Automation</em> in Agile projects (automating everything is <strong>not</strong> the key) and how to decide wisely which tests need to be automated.</li></ul><p>And at the end, we had a clear vision about Agile and how <strong>collaboration is its backbone</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NZ2UuGyosrUQqx34_3BTJw.png" /><figcaption>Happy and focused trainees</figcaption></figure><p>If you are interested in knowing more about the CAT training course and exam, please contact us. We are going to be very glad to support your team! :)</p><p>You can also visit the following sites to view next scheduled CAT training courses or other trainings available:</p><ul><li><a href="http://www.isqi.us/">International Software Quality Institute</a></li><li><a href="http://www.agile-teaming.org/products.html?desc1#desc1">Certified Agile Tester product description</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PHm8-Pft0UROHxiE9mQuzg.png" /></figure><h4>If you enjoyed this story, please click the 👏 button and share to help others find it! Feel free to leave a comment below.</h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c9380193c26e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>