Overwhelmed with so much to done? Use a project tracker!

A Project Pivotal Tracker board

When I got the project specification and rubrics for the more-recipes app I was to design, it felt so overwhelming. I was like, how will I be given such an enormous project as this? Where do I start from? I have never even built a successful front end project before not to talk of its full stack elder brother!

But as I read through the project specifications, I began gaining some confidence, not because I figured it all out, but because I realized it was broken down into series of activities which will ultimately lead to the final product. I felt this is a good thing as it could give me the chance to do research specific to the part of the project that is most immediate, little did I know that the folks at Andela even got something to help me beyond this.

Yesterday, I was given some guidelines on how to use Pivotal Tracker app together with my git work flow. It was as easy as creating a story on pivotal tracker app, copying its story id and noting the type of story it is. This then form the basis for the work flow — the branch naming convention and the pull request title and description — how cool!

So, this morning, I decided to start using this model and the experience has been so trilling. The project now seems so streamlined that I only focus on one task per time and this has not only allay my worries of not being well equipped to achieve the goal, but also taught me the value of agile methodology for software design.

Interestingly, the use of such project tracker apps is not only meant for software design field — anyone and everyone can (and should) use it to manage their day to day and even year to year tasks.

So, I hope someone out there sees this post and understand the blessings of actually planning ones tasks before hand, breaking them into chunks and using a project manager app to monitor the execution of those chucks. It’s such a good thing!