My Project Management Experience as a Beginner
So, our team @ OneNull Softwares has completed yet another project. Here’s a breakdown of what I personally have done and learnt during this 3 week of working on this particular project.
𝗜𝗻𝘁𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻
This was a follow-up functionality enhancement project given to us by Gnosis Labs for their Application Launcher project for their cutting-edge educational virtual simulation application which were also assigned to us back in March 2023. For those who might not heard of us yet, we @ OneNull Softwares specializes in custom software development for a wide range of platforms, ranging from desktop to mobile.
𝟭. 𝗦𝗰𝗿𝘂𝗺
Although I’m relatively new to the concept of Scrum, I’m giving it a shot in this project so as to gain experience.
In the planning phase, we break down the entire project into various user stories to ensure all developers are aligned. Each of these user stories is assigned specific story points. Then, we make predictions about how much we can accomplish in our one-week sprints.
To accommodate our schedules as students, we hold daily “virtual standup” meetings around 7:30 pm MMT instead of the morning. In these daily sessions, we share what we’ve accomplished during the day and address any obstacles we’ve encountered. I realized that Scrum meetings shouldn’t be lasting more than 20 mins, but our meetings usually lasted around 1–2 hours since we were trying to debug issues that arose. Reporting was also done almost daily on our communication channel (on Discord) in the form of displaying the how much progress we had made every single day.
https://clickup.com/ was the tool we used to manage.
Overall, I recognize that I might not be utilizing Scrum to its full potential, even though I’d like to believe that everything is going smoothly.
𝟮. 𝗖𝗼𝗻𝘃𝗲𝗻𝘁𝗶𝗼𝗻𝗮𝗹 𝗖𝗼𝗺𝗺𝗶𝘁
I have been using Git for quite sometime for my personal projects, but I often found that my commit message were not standard. So for this particular project, we used conventional commit. Conventional commits is just a set of guidelines to guide us to write meaningful, descriptive and beautiful messages that can allow the reader or reviewer knows what a commit does at a single glance. We believe that by following this guideline, it would introduce readability to our commits and allow any potential future developers to know what we have actually done in the repository.
For example, a new feature would be added as (feat); a bug fix as (fix)
𝟯. 𝗜𝗻𝘀𝗶𝗴𝗵𝘁𝘀 𝗼𝗻 𝗺𝘆𝘀𝗲𝗹𝗳
Lastly, I gain further insights on myself into my capabilities as a leader. I realized some of my strengths and weaknesses through practical experience. I wrote that down through a mini SWOT analysis
All in all, it was a great experience working for Gnosis Labs and with my team-mates Kyaw Zin Thant and Linus Walker, and I would love to collaborate with them more in the future.
Thanks for reading, Ethan.
