My Way to the Position of Project Manager. Recommendations for Beginners
My transition from QA Engineer to QA Team Lead, then to QA Manager, and occasionally taking on the role of Technical Writer, eventually led me to become a Project Manager. In this narrative, I will elaborate on why and how this progression occurred, with the hope that it can offer insights and guidance not only to aspiring Project Managers but also to those at various stages in their careers.
I embarked on my career journey as a Quality Assurance Engineer with a passion for entering the realm of Information Technology. Pursuing my IT studies at university was a pivotal step in my journey. Working on numerous projects at an outsourcing company was instrumental in honing my knowledge, skills, and expertise.
At a certain point, I transitioned to a product company and engaged in a substantial project. This proved to be a wiser choice as it provided me with valuable insights into my future career path. This project faced several management challenges, but at that time, I lacked a clear vision for change.
The project continued to evolve with a growing client base, expanding teams, and a seemingly random influx of development tasks. It was challenging for new team members to assimilate due to a lack of comprehensive project information. Only a few individuals grasped the project’s entirety.
Eventually, we collectively decided to implement documentation, comprehensively describe functionality, and optimize QA documentation. I took on the task of creating documentation, even though it was initially meant to be handled by a Technical Writer and the entire team expressed skepticism.
Despite the initial resistance, the documentation initiative proved successful. Team members, especially newcomers, had better insights, and the Support team had fewer queries, thanks to the clear instructions and algorithmic descriptions for new features and improvements.
However, as the project grew, my dual role as a tester and documenter became overwhelming. The constant changes in tasks made it challenging to maintain documentation.
Recognizing the need for improved management, I delved back into the subject and found my passion for it. I reduced my testing responsibilities and began mentoring QA students, drawing from my academic experience. Unfortunately, management failed to grasp that my time was divided, and the product was not receiving thorough testing.
I then realized that while I had innovative ideas, there was no one to implement them. Gradually, I trained my QA Trainees to handle testing, allowing me to engage more with management. This led to a moment when I was asked to assume the role of Project Manager.
Reflecting on this journey, I wish to offer advice to newcomers and anyone in this field:
➡️ Your theoretical knowledge from books and courses holds little value if you do not immerse yourself in projects and genuinely enjoy your work.
➡️ No planning tools can assist you if you cannot effectively manage your own time.
➡️ Employees will not follow your lead if they lack motivation and view their work as merely fulfilling working hours.
➡️ Managing people is a skill that can be learned, but it requires active listening and empathy.
➡️ Flexibility is a cornerstone of effective management, especially when dealing with diverse teams. Consider psychology courses if you’re a newcomer or have recently joined a new project or team.
➡️ Familiarize yourself with the project, even if you don’t delve into every detail. You must have a clear understanding of who does what and the consequences of tasks left undone.
➡️ As a Project Manager, you should advocate for your Development Team, ensuring they have the most conducive working conditions to minimize issues.
➡️ Understand that risks are an inherent part of any project, and mistakes are bound to occur. Our role is to address and resolve these issues.
I express my gratitude to all my previous employers for the invaluable experiences that have shaped my journey.
