<?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 MaoMrtnz on Medium]]></title>
        <description><![CDATA[Stories by MaoMrtnz on Medium]]></description>
        <link>https://medium.com/@maomrtnz?source=rss-fc6d29402b4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*b9RhJfajjxHTRnWQueIAYg.jpeg</url>
            <title>Stories by MaoMrtnz on Medium</title>
            <link>https://medium.com/@maomrtnz?source=rss-fc6d29402b4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 20:35:43 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@maomrtnz/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["Stress is not bad. Burnout is a state of mind."]]></title>
            <link>https://maomrtnz.medium.com/stress-is-not-bad-burnout-is-a-state-of-mind-fc569b9f6d83?source=rss-fc6d29402b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc569b9f6d83</guid>
            <category><![CDATA[mental-health]]></category>
            <category><![CDATA[working]]></category>
            <category><![CDATA[mental-health-awareness]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[work-life-balance]]></category>
            <dc:creator><![CDATA[MaoMrtnz]]></dc:creator>
            <pubDate>Thu, 28 Mar 2024 09:53:14 GMT</pubDate>
            <atom:updated>2024-03-28T10:03:42.167Z</atom:updated>
            <content:encoded><![CDATA[<blockquote>Context: I saw a 23year old stating this after receiving his bachelor degree and &quot;Working full time the last two years&quot; his words.</blockquote><p>My first reaction, &quot;Ok kiddo!&quot;</p><p>Is true that stress isn’t inherently bad and can even be a motivator in certain situations, it’s important to recognize that prolonged or excessive stress can lead to burnout, which is more than just a state of mind.</p><p>This is a sad reality of our new world, we are constantly exposed to loads of information, ideas and overwhelming work.</p><p>Ignoring the signs of burnout and dismissing it as merely a “state of mind”, can be dangerous to your professional and more importantly your personal life.</p><p>Recognizing the difference between manageable stress and burnout is key to maintaining overall well-being.</p><p>This like many other will be lessons that for more you try to advice people they will not understand until they have experienced it.</p><p>It takes time, you will not find the right rhythm on your first year, or maybe you will, <br>I always give the same advice to those joining the workforce:<br>Right now you are young, take advantage of your metabolism, your energy, learn a lot, don’t be afraid to make mistakes, but take care of your personal life.</p><p>And as Always this is of course just my opinion.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc569b9f6d83" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[I’m Mao, your next QA Engineer.]]></title>
            <link>https://maomrtnz.medium.com/im-mao-your-next-qa-engineer-a05583be2405?source=rss-fc6d29402b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/a05583be2405</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[job-hunting]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[MaoMrtnz]]></dc:creator>
            <pubDate>Mon, 05 Dec 2022 09:58:31 GMT</pubDate>
            <atom:updated>2022-12-05T09:58:31.326Z</atom:updated>
            <content:encoded><![CDATA[<h4>About me.</h4><p>I enjoy writing articles and now that I’m looking for a new challenge, I thought it would be nice to write one about me.</p><p>I’ve been working as QA Engineer for more than 10 years, during that time I’ve been Junior, Senior, Lead and even Head of QA.</p><p>I think of myself as a QA Engineer with deep interest in DevOps, Security and infrastructure.</p><p>And I Love My Job, even though it is a constant struggle to educate other people and companies to see the importance of what we do.</p><p>One of the perks of my job is to be able to adapt, to see the product not only as a QA but also as a Developer, Stakeholder and Consumer, to be able to achieve that version of Quality that will give us that satisfied feeling.</p><p>Whenever I join a new company my first goal is to understand how the company and projects are currently working, get to know it’s people, learn their processes, structures, understand the business needs and goals, for when the time is right tweak them to increase the Quality.</p><p>I take my job very seriously. I don’t focus only on the tasks as QA but for me Quality is a wider and bigger word we don’t give enough credit to, I bring QA to every corner of the company, from improving User Stories, Workflows, Documentation, to making sure the company knows what QA is doing, how we are improving performance and reachability and to get more people motivated and interested in raising the bar.<br> <br>I’m a person that thrives on Transparency and Communication, I will push for this to be a daily thing with the people I work with, and by so creating a healthier, more confident team and environment.<br>I bring Quality to a new definition where everyone not only understands why we need it but they get behind the wheel to make sure we get there on the best terms.<br> <br>I definitely put my Agile Certification to use, to make sure we are moving forward in a rhythm that is maintainable and successful.<br> <br>When it comes to processes, I’ll be the first one to read them, criticise them, and transform them.<br>If we talk about new processes I’ll write them, implement and follow up on them, of course not alone.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fz3XK-Qr5vmLMTseMcpI_A.png" /></figure><p>The experience I’ve acquired over the last years puts me somewhere between backend and QA, this angle has given me great advantages when it comes to finding what is causing an issue and not only that but has also help me to offer, understand and implement it’s solutions.</p><p>I enjoy a challenge, always jumping in for high incident bugs, doing this has given me an edge and keen eye for solutions, by getting involved with as many teams as possible, being inquisitive and thorough with my tasks is part of my routine, again communication is key for any relationship in and outside work.</p><p>I’ve always been one to speak my mind and help others to achieve this, we all lead different lives which means our points of view are many and full of wisdom, I learned to channel that and show others by example how to get there.<br> <br>Being involved and talking with Dev, Sales rep, Stake-holders, even with VP of engineering has helped me to create a trustworthy environment, where everyone’s opinions are welcomed and mistakes are celebrated, you see I am one of those that understand how important failures are and more than that to be true to yourself. <br> <br>The best thing someone can do is make mistakes, there lie the best lessons for life.</p><p>Data is the new gold rush, but instead of keeping that stored somewhere I believe in sharing information, the more I learn and the more I get to know a product the more I’d talk about it, why? <br>It’s quite simple, every time you learn something it is proven that your retention will increase as soon as you start talking or explaining it to someone else and another reason is that you get to share the knowledge.</p><blockquote>Knowledge is meant to be shared not contained.</blockquote><p>Being in the constant process of evolution, keeping up with latest technologies and trends is part of my life, there is so much still to learn and achieve. <br> <br>No candidate is going to be perfect for a job and I’m not trying to be perfect.</p><p>I’m trying to demonstrate that I’m a person worth investing in. <br> <br>So let me show you what we can create together! <br> <br>Pura vida! *</p><blockquote>Mauricio is a great specialist with a strong knowledge base, who is always eager to learn more and always ready to share his knowledge with others. Also he is a brilliant team player and it’s been a pleasure for me to work with him in the team. He goes not only the extra mile to achieve the team‘s goals but also he actively participates in company life, for example, he was successfully leading a team at one of the biggest sport events in the company. I can only recommend Mauricio and will be happy if our paths cross again one day.<br>Aida Kasanova — <a href="https://www.linkedin.com/in/mauriciomartinezcr/">LinkedIn Recommendation</a></blockquote><figure><img alt="Profile picture, Man wearing black shirt." src="https://cdn-images-1.medium.com/max/320/1*GCDa6WrJ8lAwwUH74xRpoQ.jpeg" /><figcaption>Mauricio Martinez, <a href="https://www.linkedin.com/in/mauriciomartinezcr/">LinkedIn</a></figcaption></figure><p><em>* Simply translated, it means “simple life” or “pure life”, but in Costa Rica, it is more than just a saying — it is a way of life. Costa Ricans (Ticos) use this term to say hello, to say goodbye, to say everything’s great, to say everything’s cool</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a05583be2405" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Tired of spillovers? 
Don’t forget to estimate meetings while planning.]]></title>
            <link>https://maomrtnz.medium.com/tired-of-spillovers-dont-forget-to-estimate-meetings-while-planning-6ae911a7537f?source=rss-fc6d29402b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/6ae911a7537f</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[MaoMrtnz]]></dc:creator>
            <pubDate>Sun, 24 Jul 2022 14:55:22 GMT</pubDate>
            <atom:updated>2022-08-03T15:49:32.707Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6M3snVEpBVauoNcEkxyNHw.jpeg" /></figure><h3><strong>Tired of spillovers? <br>Don’t forget to estimate meetings while planning.</strong></h3><p>We go to planning thinking of certain availability for the next sprint but forget to expect the unexpected.</p><p>&lt;Take a read on this POV:&gt;<br>Review the tasks and user stories, make sure all of them are properly estimated before we start the planning. I’ve taken 10 points in different stories so I know I’m going to be busy.<br>End of the sprint comes and I rushed to sent tickets out to accommodate the end of sprint, how did I got here?<br>I estimated everything.<br>Turns out I forgot THE MEETINGS!<br>&lt;/end of POV.&gt;</p><p>If Previously I’d would have taken 8 Points for the sprint, there is a possibility that I would have completed everything on time, of course there are times that even with 10 points per sprint, I manage without problem to finish before end of sprint.</p><p>We work on a sprint by sprint basis and most of us just book our weeks according to our tickets/tasks but forget to include things such as:<br> — Meeting’s times.<br> — Next sprint preparation tasks.</p><p><em>Factor in all protocol meetings and non-regular meetings that might pop-up during the week.<br></em> <br> Add the end of the sprint, when we sum up all the time we did not estimated but end up using due different factors, we notice that is a sizeable amount of time.<br> Because of this sometimes certain tasks are not completed hence spillovers happen.</p><p><em>This can be avoided if proper estimation is done in the first place.</em></p><p>How to solve this?<br> Action and Reaction can’t be measured 100% accurate but we can learn from previous sprints and try to estimate an average time spent on such tasks.<br> On a scenario where the sprint is two weeks, while planning if your capability is of 10 points, make sure to leave free space to be able to use that time for tasks of next sprint, <br> review backlog, create user stories and of course include the protocol meetings inside this time.</p><p><em>Estimate the meetings &amp; other tasks.</em></p><p>Each passing sprint the team will be able to understand and apply better this pattern, which lead to less spillovers leading to a healthier sprint.</p><p>Creating a buffer during the planning session will lead us to not only have room to work on valuable tasks for the next sprint but also use that time when an unexpected event comes out.</p><p>That’s at least how this Engineer believes it.<br>Have another opinion? Feel free to reach out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6ae911a7537f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bring Back QA to Product teams!]]></title>
            <link>https://maomrtnz.medium.com/bring-back-qa-to-product-teams-ab3e7b739a1c?source=rss-fc6d29402b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/ab3e7b739a1c</guid>
            <category><![CDATA[quality-software]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[MaoMrtnz]]></dc:creator>
            <pubDate>Wed, 23 Mar 2022 15:44:35 GMT</pubDate>
            <atom:updated>2022-03-23T15:44:49.056Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*gE271I5r4bjBSkIReetNOA.png" /></figure><p><em>[Destroying the misconception that QA is the responsibility of only a few.]</em></p><p>Let’s start by acknowledging that QA is not a person or a team responsibility but instead should be a company’s effort to thrive on good standards, a goal for all Tech companies to start an all hands approach, and in Order for anyone to perform any kind of assistance in testing we need to work on having the basic security rules and testing frameworks cleared.<br>This will create a more confident structure,where QA it’s owned by anyone inside the product engineering team, and thus creating a space where the QA team can maintain and improve such structure, to provide the right tools for those that would and like to support testing.</p><p>Anyone in the Product Engineering team is a great fit but may lack the tools or proper QA knowledge, which can be taught and with time improved. I’m talking about creating and sharing a basic set of rules based on QA knowledge from which the Product Engineering Team or even better the entire company can benefit from.</p><p>Including testing done for those that know the product the best will help increase the structure and end to end quality of our product. At the same time this will create a more transparent process across teams.</p><p><em>Anyone should be able to do QA</em></p><p>And why not have a <em>How to Test</em> tutorial being part of the onboarding process for anyone that joins the Product Engineering team?</p><p>This will build and create more awareness towards our QA processes, not everyone in the tech team knows about the company QA processes and structures. <br>Sharing this information could be part of the basic onboarding requirements, and this will benefit us all. <br>There is value in preparing our teams to adapt certain practices that will not only make the company’s code better but also will enrich the team’s background.</p><p>Everyone can benefit from learning code.<br>The same goes to learning how to properly test such code.</p><p>I’m talking about having the developers included not only in unit testing but also in manual testing, for them to be able to understand the need of testing, I’m not asking for them to run a full regression test but to be aware of the benefits of testing their own code before sending out the tickets for last QA evaluation.</p><p><em>I wrote about specific developer testing on: </em><a href="https://maomrtnz.medium.com/the-red-wall-analogy-b25c06b5e702"><em>The Red Wall Analogy</em></a></p><p>To be clear, my point of view is not like we don’t need QA teams, <em>otherwise I’ll be out of work</em>.<br>My reasoning behind this is the following:<br>When we share and create a baseline of testing as part of our culture, where Quality it’s included in the daily mindset of Anyone in the Product Engineering team; Our team can focus more beyond this testing culture and create more robust and secure tools, meaning more complete testing frameworks, more time for deep exploratory testing or even to try new types of testing, I’m thinking of focusing more on automation, testing strategies and security, that will benefit the health, culture and growth alongside the company goals.</p><p>We can start working on better solutions to make the best out of testing and Quality Assurance, having new testing strategies, processes and structure improvement being constantly a priority for the QA team.</p><p>And with this new mindset a more self-aware Product Engineering team, that will deliver a more polished product, based on Quality guidelines, less bugs, less ping-pong and more secure coding that would at the end benefit the entire culture.</p><p>That’s at least how this QA Engineer believes it.<br>Have another opinion? Feel free to reach out.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ab3e7b739a1c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Deadlines, nightmare and how to make it less painful….]]></title>
            <link>https://maomrtnz.medium.com/deadlines-nightmare-and-how-to-make-it-less-painful-7d32ad080166?source=rss-fc6d29402b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/7d32ad080166</guid>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[qa]]></category>
            <dc:creator><![CDATA[MaoMrtnz]]></dc:creator>
            <pubDate>Mon, 18 Jan 2021 13:53:10 GMT</pubDate>
            <atom:updated>2021-02-19T15:20:31.534Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*gE271I5r4bjBSkIReetNOA.png" /></figure><h3>Deadlines, nightmares and how to make it less painful….</h3><h3>|how to overcome the nightmare and make it an achieved dream.</h3><p>When we talk about deadlines, we are talking about a full commitment not only for the IT crew but also for all the other teams in the company(marketing, business, press, etc)</p><p>So why is always so difficult to find a fit date to deliver?</p><p>When we talk about a fixed released or delivery date we are talking about a scenario where every single team involved in such project is at a confident level to be able to face any difficulties that. might come ahead.</p><p>One tiny-big problem on tech, is estimations done by mostly Business and marketing team without involving much of the development team or given second thought to the work in hand that would have to be done to be able to meet such estimations. Hence is part of the life cycle to speed up more than once to meet certain deadlines.</p><p>Let’s for instance talk from the marketing side, if we are talking about a new product they have to plan everything around it regarding exposure, newsletter, advertising, planing, consumer reach etc…</p><p>When wrong estimations are made, deadlines seem tight, I’ve seen the development Department pushing the extra mile to be able to deliver at least something so the entire marketing investment does not go in vain, just due poor Communication and involvement in the corresponding teams.</p><p>But this is something <em>normal.</em></p><p>In a perfect scenario such negotiations should always included someone from the engineering team, that will be capable to give a more realistic estimation and/or more options that could even increase the value and quality of what needs to be done.</p><p>Is not witchcraft, is just simple a sharing and communicative culture will solve most of todays problem.</p><p>That’s at least how this QA sees it.</p><p>Also check out:<br><a href="https://medium.com/@maomrtnz/getting-qa-back-in-the-game-cd0a44428c6b">Getting QA back in the Game<br></a><a href="https://medium.com/@maomrtnz/whats-a-qa-architect-9efc98037255">What’s a QA Architect?</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d32ad080166" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Red Wall Analogy]]></title>
            <link>https://maomrtnz.medium.com/the-red-wall-analogy-b25c06b5e702?source=rss-fc6d29402b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/b25c06b5e702</guid>
            <category><![CDATA[software-testing]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[qa]]></category>
            <dc:creator><![CDATA[MaoMrtnz]]></dc:creator>
            <pubDate>Fri, 07 Feb 2020 09:09:15 GMT</pubDate>
            <atom:updated>2020-02-07T09:09:15.941Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*gE271I5r4bjBSkIReetNOA.png" /></figure><p>How to properly QA your work to avoid ping pong effect.</p><p>For any project local environments are part of the development cycle with that they become a key element in our lives, (Dev, QA, Product people) we spend a lot of time to set up local environments for us to do our work, we are not looking for perfection but we need a scenario as equal as possible from Production; Yet we failed in understanding that such effort will not equal testing or the fact that <em>works on my machine</em>, it’s not a direct reflection of how will it behave once is deployed.</p><p>Some years ago I started to tell this story:</p><p>Your ticket today is to paint a wall, such wall is the one at the end of the living room, make sure you get all the requirements right: position, colour to be painted(red), and tools.</p><p>Now go ahead and paint that wall. Next part might sound silly, but before you call the contractor make sure of the following: Did you paint a wall? The right wall? Great! Now just make sure the paint was the right red tone, no? Well, it happens, try again…</p><p>Has it been fixed? Awesome! Now as last detail, make sure you painted that Red Wall in the same house as the rest of the team. With this I mean, make sure that your work is compatible and will be successfully deployed and merge with the least of inconvenience.</p><p>Maybe you think this is silly, but let me tell you that a big amount of bugs that come up can be prevented by simply taking a second look at your own assignment and with this we save time and minimize that so fear ping pong effect, where for small details a story or ticket is not yet approved and keeps bouncing back and forth</p><p>Your time is valuable, but so is everyone else’s.</p><p>By spending some more minutes checking what was just built with this we save time and minimize that so fear ping pong effect, were for small details a story or ticket is not yet approved and keeps bouncing back and forward, with reason but that could have been easily avoided. This will help the QA team to focus on more deep details, remember QualityAssurance is not a person or a team, it’s a way of work having in mind the best results ahead, QA depends on everyone.</p><p>The QA as such should exist to create the starting guidelines and improve them with time as well as looking for better approach to minimize conflict.</p><p>Also check out: <br><a href="https://medium.com/@maomrtnz/getting-qa-back-in-the-game-cd0a44428c6b">Getting QA back in the Game<br></a><a href="https://medium.com/@maomrtnz/testers-analysts-quality-control-and-quality-assurance-bdadf377541">Testers, Analysts, Quality Control and Quality Assurance</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b25c06b5e702" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s a QA Architect?]]></title>
            <link>https://maomrtnz.medium.com/whats-a-qa-architect-9efc98037255?source=rss-fc6d29402b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/9efc98037255</guid>
            <category><![CDATA[quality-software]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[MaoMrtnz]]></dc:creator>
            <pubDate>Tue, 05 Dec 2017 18:27:26 GMT</pubDate>
            <atom:updated>2022-12-05T09:49:15.330Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*QIJQFjLaUnaJ9RyUwwP0zA.png" /></figure><p>Well by my understanding will be a person in charge of doing research, implementation and following best practices when it comes to the QA team. Whether is Manual or Automation, the QA Architect will be there to work directly with the entire engineering team, in order to guarantee a stable and clean process. Some of the responsibilities that could be attached are:</p><p>• To create a QA Role model based on the needs of the company</p><p>• Improving QA work procedures, guidelines, <br> strategies and working environment for the team.</p><p>• Understand deeply the product implementations, the requirements world and the relevant market in which we operate.</p><p>• Wide knowledge of the whole product including all developments (multiple teams).</p><p>• Comprehension of the product’s architecture.</p><p>• Create, improve and implement organization goals for the QA team.</p><p>• Create, improve and implement Agile Basic rules of engagement</p><p>• To create an environment where the QA can be included <br> in the whole development cycle</p><p>• Create, improve and implement QA goals and review of processes in the team.</p><p>• Continue learning and sharing knowledge with the rest of team<br> over small training sessions</p><p>• Be always aware of new changes and challenges that come in the organization</p><p>• Create responsible guidelines for estimations</p><p>• Responsible for test execution and results.</p><p>• Work directly with the entire team under the manager supervision to make sure beneficial changes can be applied</p><p>• Understand planning and building of automatic tests scenarios.</p><p>• Work very closely under the professional guidance of the QA Management body.</p><p>• To improve the image of QA member inside the organization</p><p>• To help the QA grow and set professional milestones</p><p>QA Architect will help the organization to create a solid, strong and valuable QA Team.</p><p>QA is sometimes an unappreciated member of the engineering team, but we have a very important step on the cycle. <br> <br>QA is the last one to check functionality success and when it fails is the first one to take the looks.</p><p>Our jobs as any is also evolving, now the need of automation frameworks and languages is more than before, with this more hybrid positions will be created to fit what the new development technologies will bring.</p><p>I’ve heard about QA Architect during an interview process a while ago, my opinion is based on own research, feel free to call it BS.</p><blockquote>Check also: <a href="https://medium.com/@maomrtnz/getting-qa-back-in-the-game-cd0a44428c6b">Getting QA back to the game!</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9efc98037255" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[[Change] Is a daily used word.]]></title>
            <link>https://maomrtnz.medium.com/change-is-a-daily-used-word-deaabaa6629c?source=rss-fc6d29402b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/deaabaa6629c</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[engineering]]></category>
            <category><![CDATA[silicon-valley]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[MaoMrtnz]]></dc:creator>
            <pubDate>Fri, 10 Nov 2017 10:29:28 GMT</pubDate>
            <atom:updated>2017-11-10T10:29:28.370Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*QIJQFjLaUnaJ9RyUwwP0zA.png" /></figure><p>Working for Startups and Startup-alike companies change is a daily used word, new features added, old features updated, removed etc, same apply with the best engine any company has, its people.</p><p>Management of resources is not an easy task less if you are working with limited budget, you need to revaluate if the structure you have is working perfectly or if you could improve it, been aware the qualifications of each member in your company is a must, if you know what a skill-set they have, finding a new project it would not be that complicated.</p><p>For this type of companies the ventures and partners are important but nowadays the resources you have is a big influence on the company’s reputation, hence been aware of the structural health of your personal must be a top priority.</p><p>When its time to relocate team members you have to take in consideration that you are changing someone’s environment and the speed up curve is going to be affected, adaptation and getting to know not only the new project but also its members, I’ve said this many times all projects work better if your team is on the same ‘page’.</p><p>How can you make the change less complicated?</p><p>By defining the right process for it, is not the first time and is not going to be the last time you’ll have to make this changes, but by being prepared you can easily minimise the impact on the resources involved.</p><p><strong><em>Good documentation is sign of a healthy project</em></strong>, by having updated information about the project and the ‘how to’ of it, when a new resource is added it would be easier &amp; faster to catch up with the team.</p><p>And most important get used to change an evolve. Some changes might be scary, but there is a reason is happening.</p><blockquote>Clients Do not come first, Employees come first.<br>If you take care of your employees they will take care of the clients</blockquote><p>Sir. Richard Branson</p><blockquote><a href="https://www.facebook.com/TrustMeImQA">Trust me IM a QA</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=deaabaa6629c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How good is your game? — Poker planning]]></title>
            <link>https://maomrtnz.medium.com/how-good-is-your-game-poker-planning-7868b1e3e523?source=rss-fc6d29402b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/7868b1e3e523</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[development]]></category>
            <category><![CDATA[engineering]]></category>
            <dc:creator><![CDATA[MaoMrtnz]]></dc:creator>
            <pubDate>Mon, 06 Nov 2017 09:20:16 GMT</pubDate>
            <atom:updated>2017-11-06T09:20:16.820Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*QIJQFjLaUnaJ9RyUwwP0zA.png" /></figure><p>We all have this shameful backlog that we keep dragging from sprint to sprint, maybe because the manpower is not enough or the planning is not the best one for our case.</p><p>Poker planning using modified Fibonacci is going to help to continue the normal work but also start losing some weight on the backlog chain.</p><p>Like poker you have a dealer and players, how many players? Every member of the team must play.</p><p>Using the user stories for the project we are going to go one by one.</p><p>Poker planning becomes a necessity to avoid losing time on tasks that do not belong to us or can be done quicker; It saves time and help to achieve more knowledge for the players. The rules are not complex but must be followed to avoid waste.</p><ul><li>Make sure all players have access to backlog stories</li><li>All user stories must have clear description</li><li>Read at least the stories you know belong to you</li><li>Be straight forward in your points</li><li>Justify with a reason not with a simple ‘Because is like that’</li><li>Defend your cards</li></ul><p>How to play?</p><p>Roles:</p><p>Moderator — Scrum master or PM</p><p>Players — Team members</p><p>The meeting proceeds as follows:</p><ul><li>A Moderator: PM or Scrum master, who will not play, chairs the meeting.</li><li>The Moderator provides a short overview. The team is given an opportunity to ask questions and discuss to clarify assumptions and risks.</li><li>Each individual lays a card face down representing his or her estimate. This case will use Story points based on modified Fibonacci {instead of SP they can be days duration or ideal days}. During discussion, numbers must not be mentioned at all in relation to feature size to avoid anchoring.</li><li>Everyone show their cards simultaneously by turning them over.</li><li>People with high estimates and low estimates need to offer their justification for their estimate and then discussion continues.</li><li>Repeat the estimation process until a consensus is reached. The developer who was likely to own the deliverable has a large portion of the “consensus vote”, although the Moderator can negotiate the consensus.</li><li>To ensure that discussion is structured; the Moderator or the Project Manager may at any point turn over the egg timer and when it runs out all discussion must cease and another round of poker is played.</li></ul><p>When using story points remember the numbers are not <strong>time equivalent </strong>but <strong>EFFORT </strong>estimation, and it shall include development, review and QA.</p><p>Why do we need it?</p><p>Is going to help the team know a clear scope of this sprint and it would minimize time wasted.</p><p>When do we have it?</p><p>Starting the sprint or right after the retrospective meeting of the last one.</p><p>Why everyone is involved?</p><p>Even back-end developer can give his opinion on a Front-end story, this meeting is to try to simplify the effort, some members may know a faster/better way to do something, and assigned member can verify if they are truly understating the task and everything that involves it.</p><p>The first meetings are going to take long, but as any new process is just matter of time to get it right and move on faster.</p><blockquote>Trust me Im QA</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7868b1e3e523" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microservices outtake]]></title>
            <link>https://maomrtnz.medium.com/microservices-outtake-2225407f2dce?source=rss-fc6d29402b4------2</link>
            <guid isPermaLink="false">https://medium.com/p/2225407f2dce</guid>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[system-administration]]></category>
            <category><![CDATA[it]]></category>
            <dc:creator><![CDATA[MaoMrtnz]]></dc:creator>
            <pubDate>Fri, 08 Sep 2017 14:53:22 GMT</pubDate>
            <atom:updated>2017-09-08T14:53:22.785Z</atom:updated>
            <content:encoded><![CDATA[<p>Some people claim this is a very innovative way of work it might surprise you that actually is not. <em>{so I’ve heard}</em></p><p>Tech companies like amazon and google have being aware of the need of independency towards software, of course not before having or facing big loses after system crash.</p><p>Every consult made on google go under a lot of different MS to deliver an fast and correct answer accordingly to what was asked.</p><p>Also think way back, industrial revolution and the need of produce in big numbers without compromising quality of product, having everything on one single line might not be good idea, what if that line collapses?</p><p>However having different lines for assembling products that can continue working even if one source failed, that’s a contingency worth trying.</p><p>Now by “definition” Microservices is pretty much that, focused and small services that together accomplish the full functionality of an application.<br>Every service is fractured in a way that individually they represent different responsibilities of the application, this along with fractured teams and its independency makes them fast and easy to be better <em>deployable</em> and <em>testable</em>.</p><blockquote>What used to take a lot of time now can be simplified and speed up better than before.</blockquote><p>Now, Why?</p><p>Simple, Microservices are small and independent, their respective responsibility will be always important, but will not cause major <em>downtime </em>and fatal failures when broken and will be easier to track, fix and contain.</p><blockquote>Knowing almost exactly what and when a service failed will give a faster access on the Why<strong>.</strong></blockquote><p>What can be moved up to Microservices?</p><p>Pretty much anything you have, now the question is <em>should be? Do I need it?</em><br>Some companies have jump into the wagon just because of the hype and they seem to think is needed, when what they needed was actually to improve their development process, something the Microservices might help, for a short time.</p><p>The abuse and misusage of Microservices can be really annoying and having to look on thousands of different services to find out what happened is not big change on how used to be.</p><p>As a way of work it must be thought well and be applied when is really need and the proven value of leaving monolithic structure is way significant for the entire application.</p><p>Pros?</p><p>Independency<br>Less cost after failure<br>Quick recovery of operation<br>Faster deployment<br>Faster Testing <br>Increase of Operations</p><p>Cons?<br> <br>Major documentation for each service is needed<br>it will take time to adapt<br>Disperse Data Sources<br>Big changes required on API<br>Be ready for some refactoring<br>Needs constant and frequent updates.</p><p>When talking about costs, the ideal would be to bring on board a team that digest MS better than anyone,<br>Investing in proper trainings to improve the skills of everyone involved should never be a downside.<br>We all know would represent a good investment towards the sanity of the application.</p><blockquote>://About_me:</blockquote><blockquote>I wrote this article based on experience I’ve had in different companies and projects that have gone from monolithic approach to micro-services. <br> Call BS if you feel like it Im also learning on the process.<br> <a href="https://www.linkedin.com/in/mauriciomartinezcr/">https://www.linkedin.com/in/mauriciomartinezcr/</a></blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2225407f2dce" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>