Project planning and importance of estimates

No matter the size of the project and its budget, project planning is essential to allocate the resources – people in the team, tasks, timeline, budget.

Once you have an approximate estimate ready – it can be used as a certain straight line that you need to follow and rely on during the development path. Project development will become concise as you’re going to know your next steps, how long each one should take, who will be working on what, as well as you will be able to sort out the budget properly.

In order to create a working estimation that you can rely on, you need to know your team players well (their strengths and weaknesses – I mean from a professional perspective, so don’t get too hard on this point), project goals/details.

Also, you should be willing to define the parts that are not yet completely clear by asking questions. The trick is that you may not know that there are still parts that were not defined. If done correctly, you may be surprised at how many points from the specification or mockups structure were not thought-out. It often happens that some unevident UX, etc moments hide in the shadow. The creation of an estimate helps to fill out these gaps as well.

Know your team and allocate the tasks based on a person’s strong sides.

The next point is that you need to have a clear understanding on the project management process. There are different ways to handle the workflow: Agile, Scrum, Waterfall etc.

Usually, it’s the combination of all that works the best. Like having a project plan, tasks in Jira/Trello etc, and put them into little or large sprints (depends on the project). Daily reports from the team members as well as an issue-tracking board make a huge impact. You can also include regular stand-ups, however, I don’t really recommend doing it on a regular basis (since it may be disruptive and time-wasting) if you acquire a practice of actively using Jira/Trello/etc + putting daily reports into a Slack channel.

quality.code recommendation is to be proactive at asking questions and trying to keep everything simple and documented so that you can always check on the current progress and timeline.