<?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 Daneez Owais on Medium]]></title>
        <description><![CDATA[Stories by Daneez Owais on Medium]]></description>
        <link>https://medium.com/@daneezo?source=rss-35b7e58dba35------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*kHh9J_dwaP275Kpc.</url>
            <title>Stories by Daneez Owais on Medium</title>
            <link>https://medium.com/@daneezo?source=rss-35b7e58dba35------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 00:24:02 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@daneezo/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[Part One: The peopleware of engineering management]]></title>
            <link>https://medium.com/@daneezo/the-peopleware-of-engineering-management-425acb04ae04?source=rss-35b7e58dba35------2</link>
            <guid isPermaLink="false">https://medium.com/p/425acb04ae04</guid>
            <category><![CDATA[management-and-leadership]]></category>
            <category><![CDATA[leadership-skills]]></category>
            <category><![CDATA[engineering-mangement]]></category>
            <dc:creator><![CDATA[Daneez Owais]]></dc:creator>
            <pubDate>Wed, 20 Mar 2024 23:30:18 GMT</pubDate>
            <atom:updated>2024-03-22T17:07:46.752Z</atom:updated>
            <content:encoded><![CDATA[<p>What is the role of an EM?</p><p><a href="https://en.wikipedia.org/wiki/Peopleware:_Productive_Projects_and_Teams"><strong>Peopleware </strong></a><strong>— what is it?</strong></p><p>Engineering managers possess people skills and are responsible for not just planning, organizing, and coordinating engineering activities but majorly concentrate on peopleware.</p><p>Peopleware is a term popularized by the authors of the book Peopleware: Productive Projects and Teams written by software consultants <a href="https://en.wikipedia.org/wiki/Tom_DeMarco">Tom DeMarco</a> and <a href="https://en.wikipedia.org/wiki/Tim_Lister">Tim Lister</a>. According to Wikipedia, “<a href="https://en.wikipedia.org/wiki/Peopleware">Peopleware can refer to anything that has to do with the role of people in the development or use of computer software and hardware systems, including such issues as developer productivity, teamwork, group dynamics, the psychology of programming, project management, organizational factors, human interface design and human–machine interaction</a>.”</p><p>When I first heard the term “peopleware”, my first thought was that it meant to be “people AWARE” meaning managers need to be aware of their team members feelings at all times. I recently read and I am paraphrasing here, being given the title of manager does not automatically make you a manager you need to have respect; in order to gain that respect you have to earn it. And you earn respect by building trust and delivering what you promised to your team.</p><p><strong>Be Intentional about things!</strong></p><p>Being aware/conscious in the context of management means many aspects.</p><ul><li>I wonder if my team members are content.</li><li>If they are experiencing a challenging week, is it due to personal matters or workplace issues?</li><li>Am I equipping them with the necessary resources and do they know me? Are they acquiring new skills?</li><li>Am I providing them with leadership opportunities?</li><li>Am I delegating tasks or handling everything independently?</li><li><em>Most importantly,</em> do they feel psychologically secure in the team and the company?</li><li>Is their feedback reaching the leadership?</li><li>Am I allowing them to express themselves during our one-on-one meetings, or am I dominating the conversation?</li><li>Am I emphasizing the significance of maintaining a healthy work-life balance?</li><li>Are they flourishing and contributing ideas?</li><li>Are they burdened with excessive workloads?</li><li>Am I advocating for them within the organization?</li><li>Am I recognizing and showcasing their contributions?</li><li>Do they feel isolated and desire more collaboration when working on a project?</li><li>If they are working remotely, do they feel included in casual conversations about projects taking place among colleagues physically present in the office?</li></ul><p><strong>Birth of em_managment_trail channel</strong></p><p>I assure you that this article is not focused on self-inquiry but rather on sharing insights and real-life anecdotes about how I tackle some of these scenarios and maybe gather insights along the way from my readers on things I maybe missing.</p><p>Being a manager, whether in engineering or any other field, involves a multitude of responsibilities. My viewpoint is primarily shaped by my background in engineering. These ideas arose when I initiated an “em_managment_trail” channel on Slack within the CallRail workspace for individuals venturing into management or aiming to become engineering managers. It led me to consider the type of management practices I want to promote in the future. Am I experienced enough as a manager to impart these skills effectively? I sincerely hope so!</p><p><strong>Feelings matter!</strong></p><p>Let’s dive into how my week starts. I address these questions on a weekly basis: Are my team members content? If they are experiencing a challenging week, is it due to personal matters or workplace issues? Enter into the picture 15five! It has a tool called pulse check that asks employees how they are feeling on a scale of 1–5; A rating of 1 indicates the worst week ever, while a rating of 5 signifies an exceptionally positive week and a 3 means neutral week neither too good or too bad.</p><p>If I notice a rating below 3, my concern escalates, prompting me to contact the individual to inquire about their well-being and offer assistance in improving their situation. the issue may not always be work-related; it could stem from personal circumstances. In such instances, I delicately inquire about the issue, and if they prefer not to disclose, I concentrate on finding ways to reduce their workload to assist them in managing the situation. The objective is to assure them that I am there to support them unconditionally, regardless of the circumstances.</p><p>Now you may ask, is this support genuine? Yes! This is part of being an empathetic leader. Gone are the days when employers said, you have to deliver in spite of the realities of your life. Shit happens in everyones life and it is time to acknowledge it. I always think about what my expectations would be of my manager if I was in the same situation. I would expect understanding and strong support and positive mantras.</p><p><strong>Finding resources</strong></p><p>Providing resources is not as tough as it may seem. When I was interviewing for some of the jobs and I was asked how will I provide my team technical resources? My response was simple, I am a very resourceful and curious person and I will hunt down the person in the office who can answer this question for me. Yes curiosity truly does kill this cat and one of my initial things I do when I join the company, I make friends! Not just with peers but also with the leadership. I identify who is approachable for what questions.</p><p><strong>Introduce yourself to your team</strong></p><p>As far as getting to know me is concerned, somebody created an idea of “My user manual” and that should be a good place to start when starting with new team members. Prepare and present a presentation to your team outlining details about yourself, addressing topics such as preferred working conditions, preferred work hours, preferred communication methods, preferred feedback reception, essential needs, preferred learning methods, and any other relevant information you wish to share. Unfortunately for me this idea came across one year into working with my current team but fear not my fearless reader, it is never too late and so we are working on these presentations within our team now to share with each other.</p><p><strong>Psychological security is important!</strong></p><p>Providing psychologically security also requires work. Once your team gets to know you, you have to give them the feeling that they can share anything without any fear of judgement. Inclusive leadership rules recommend that we periodically ask individuals questions like Do you feel you can take risks on this team? Do you feel you can share any idea with your team as in are you comfortable speaking up without the fear of retaliation? If the answers to these questions are negative then my friend you have failed in creating psychological security. Of course, the diverse teams have diverse personalities; some quiet and introverted, some outspoken and extroverted. What I have found helpful is that during meetings, if I am suggesting a change in a process or an idea, I ask every single team member not whether they agree but what they think. This open ended question forces a response out of them and gives the quiet ones the opportunity to contribute. I once received valuable advice that encouraged individuals to mimic crabs in a bucket. Instead of competing and climbing over each other to reach the top, the focus should be on lifting and supporting everyone to the top together. This collaborative approach fosters fulfillment and growth for all involved.</p><p><strong>Build camaraderie by passing on feedback!</strong></p><p>Another approach I have found helpful is once a month asking team members, who on the the team do you think is doing a great job? Once they share, make it a point to share that feedback with the individual mentioned. This practice also nurtures camaraderie and helps individuals recognize that their team acknowledges and appreciates their efforts.</p><p>I know that this may be a lengthy read! Join me on my journey through engineering management as I share the tips and tricks I utilize to maintain engagement within my team.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=425acb04ae04" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Lessons learned in Agile QA testing]]></title>
            <link>https://medium.com/@daneezo/lessons-learned-in-agile-qa-testing-4b9456223dfd?source=rss-35b7e58dba35------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b9456223dfd</guid>
            <category><![CDATA[qa-testing]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[quality-assurance]]></category>
            <dc:creator><![CDATA[Daneez Owais]]></dc:creator>
            <pubDate>Thu, 17 Aug 2017 22:31:41 GMT</pubDate>
            <atom:updated>2017-08-17T22:32:51.069Z</atom:updated>
            <content:encoded><![CDATA[<p>Quality Assurance is a fun job especially if you are an inquisitive person like me because when curiosity doesn’t actually kill the cat; it makes a better product. Quality Assurance allows you to learn &amp; develop techniques for looking at a product in new ways. Each product requires a different approach to testing. As my previous manager used to say:</p><p>“How many ways can you sketch a picture of a cup? Each time you look at it, you will see a different side to it!”</p><p>My journey started roughly 10 years ago when I worked at a traditional software development company. I started with testing sales reports for the clients. Many hours and days were spent making sure that each report was just right. But, is a product ever going to be <em>just right</em>? No! that’s because a product evolves over the course of its development and it continues to evolve after the release when your users feel that they can get better results with some changes. Gone are the days when you create a product and present it to the clients on a platter stating, “This is all we can give you so learn to work with it”.</p><p>My journey then progressed to moving to an Agile development environment. Alice was truly lost in Wonderland! Fast paced, collaborative, and learning new concepts while always on the go. When in Agile your entire mindset needs to be flexible and ready to evolve. After all that IS the definition of “agility”. For me personally, I ended up <em>wanting</em> to log in to work all the time wondering what will happen now? Was some new bug found? I wanted to know and I wanted to reproduce it. (No don’t worry I did not log in all the time!).</p><p>So, in this journey of testing in Agile, here are the lessons learned:</p><p>1. <strong>Find bugs — </strong>A bug is a bug ONLY if it can be reproduced multiple times, not just by you, but also others in your team.</p><p>2. <strong>Be clear &amp; concise — </strong>Be very clear and concise in writing the bug tickets! The developer who is reading the ticket was not sent the login credentials that you used, in a dream the previous night. Help the poor chap by putting that in the ticket along with every step you took to get to the problem.</p><p>3. <strong>Pick and choose your battles — </strong>Some product changes are mere enhancements so accept them as that. There may be other projects with greater priority so don’t bother the developers about your idea just yet, but always document it.</p><p>4. <strong>Stick to your guns — </strong>When you have chosen your battle and decided that it is worth standing up for, then chase the developers all the way into the kitchen while they make their coffee and try to hide from you. Prove your point with example scenarios of how you are visualizing the issue.</p><p>5. <strong>Meetings and meetings and then some more meetings — </strong>Daily standups (no, I was sitting in my chair because I worked remotely) and multiple ones! Oh boy you better have your status on what you have been doing every day ready for those scrum masters, product owners and then, your own manager. They mean business when they want to know where you are in your testing and what the delays are and no this is not the same as micromanaging. It is an awesome way to keep all the teams in the loop.</p><p>6. <strong>Story points? What story are points?</strong> Grooming meetings are where you look at the backlog together with the developers, and the scrum masters to decide priorities. Where the scrum master keeps asking “how many story points?” (and you secretly (and) quickly google what story points or what scrum poker is — oh wait it is just an estimation of how long it will take to test?)</p><p>7. <strong>Understand the issue or requirements even if means harassing people — </strong>In the traditional environment, it was very common to get a ticket or a print out of the screen shot of the issue with a written instruction “pls test” and not be able to understand it (because it was not clear and yes, a picture is worth a thousand words but NOT in this case). Then you walk up to the developer’s desk and demand an explanation of the problem that was fixed. Not in Agile, you will learn to document each question you have. Make sure it is written down on the ticket so people can see where there is a delay. Although I do miss watching the developer run out the door as I am walking towards his desk (here comes the witch either on the beam <em>(google beam robot)</em> or in person), or the developer (you know who you are) who snuck in from another door of the office to avoid crossing his managers office (who would suspect that he was walking to my desk because I had found a problem), to quietly ask me what I had found so he could fix it on the side without his manger knowing. Alas, the sad part was that it was part of my job to keep the managers in the loop.</p><p>8. <strong>Gotta love those DevOps guys — </strong>Can’t log into the QA environments at all? Where are those DevOps guys? Oh no, they are all on vacation this week. What did they do to the environments now? Uh-oh, it wasn’t them at all but the developer in charge of the environment making code changes and breaking the environment in the process. Be patient and wait for them to fix it. Make your request and then forever hold your peace.</p><p>9. <strong>Works in QA but not in stage?</strong> If it works in a QA environment, that doesn’t necessarily mean it will work in stage so check it again on stage! Remember drawing a cup and getting a different result each time? Just like proof reading a document, it never hurts to read it 50 times (I think I got tired of reading this one after the 20th time)</p><p>10. <strong>Browsers, browsers &amp; more browsers </strong>— Make sure the website works in all the new browsers out there. Do not give the client a response like, “Sorry our site only works in Google Chrome so download it!” The user comes first. Your intention has to be to make it easy for them, not easy for you (<em>success I</em> only need to test it one browser and <em>do the happy dance</em>). Is it responsive? Hmm what is that? Does it work on all different screen sizes mobile and web? Mobile companies keep on releasing new bigger and smaller devices. The product should work in all otherwise you be in trouble.</p><p>11. <strong>Project overload or actually increase in knowledge base?</strong> Work in cross-functional teams on different projects. It helps to understand and know the product inside out.</p><p>12. <strong>Walk down the memory lane — </strong>Retrospective meetings — what went well in the sprint? l I think the QA team did great (I am part of that team so that is the first thing to point out!) What went wrong? Where do I start? The user story is supposed to be small and concise not a book about the requirements. Lessons learned? Keep user stories short and make sure the UI/UX design matches what you are stating in your ticket in words. Oh, and in future please don’t tell me at 3 pm that you want this to go out tomorrow at 9:00 AM.</p><p>13. <strong>Sharing IS caring — </strong>Don’t keep it all to yourself! Share knowledge even if it means sharing something someone might already know. Maybe they have a different perspective to the knowledge. Share knowledge about the product and its features or a new bug you discovered while doing ad-hoc testing. You never know maybe somebody else found the same issue and already added a ticket — this helps avoid duplication.</p><p>So all in all whether traditional or agile, be nice to your developers and product teams. They have feelings and ideas too. Don’t build your own 2.5 inch temple on the side and stand alone in it (as they say back home — curious where that is?). Creating a better product requires teamwork and a passion for the product. Quality Assurance is an important job from start to the end — know it and believe it. Don’t just follow a straight path, make left or right turns and sometimes U-turns too and you may just run into an undiscovered bug. Think outside the box and help others do it too.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b9456223dfd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Strangely Amazing Experience Of Strange Loop 2016]]></title>
            <link>https://medium.com/@daneezo/the-strangely-amazing-experience-of-strange-loop-2016-a7d3a691a4cb?source=rss-35b7e58dba35------2</link>
            <guid isPermaLink="false">https://medium.com/p/a7d3a691a4cb</guid>
            <category><![CDATA[strangeloop]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[progressive]]></category>
            <dc:creator><![CDATA[Daneez Owais]]></dc:creator>
            <pubDate>Thu, 22 Sep 2016 17:20:34 GMT</pubDate>
            <atom:updated>2016-09-22T17:20:34.730Z</atom:updated>
            <content:encoded><![CDATA[<blockquote><strong>The Strangely Amazing Experience Of Strange Loop 2016</strong></blockquote><p><strong>St. Louis, MO </strong>— It was my first time attending Strange Loop and it turned out to be an enchanting treat. Started from the airport — I landed late in the evening and caught the Metro to the Union Station. In the Metro, I came across other Strange Loopers, some from Canada and others all the way from Australia. The idea that I was attending something this big, started registering as I found out how far people were coming in from.</p><p>The Double Tree Hotel is in an old train station at the Union Station. The ambience was just beautiful. I walked into the lobby and saw a huge crowd in the lobby, all sitting with laptops heavily involved in networking. It was overwhelming at first because even though there were a lot of people flying in from Atlanta, I only knew one person in the crowd from my Girl Develop It group, little did I know that this would change within these 3 days.</p><p>The next 3 days were just crazily busy but good with all the different talks. I met a lot of new people and learned a lot of things. Out of all the talks I went to, my favorite one was “Is it a bug or is it a story?” by Nicola Hughes from Thoughtworks, London. She had a very interesting way of explaining how data is measured and maintaining audience interaction.</p><p>The two hour workshop of “Swiftly create a mobile app” was a great learning experience and went by real <em>swiftly</em>. It added the idea of learning a new language to my objectives for myself for the year!</p><p>All in all I would greatly recommend anyone that is part of the tech industry to try and attend this conference. It is held every year in September in St. Louis! Way to go Strange Loop and thank you for the grant! Maybe next time, somebody else will not <em>accidentally</em> win my Echo!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a7d3a691a4cb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>