Planning means more than just staying organized
IT project management is hard to imagine without planning. Planning orchestrates the work of different project departments (software development, marketing, sales, etc.). Having a plan enables business decision-makers to manage software development budget and stay focused on where they go and see the vector of product development clearly. Planning cannot work without estimating the time of execution for each of your tasks. Developing a habit of splitting your tasks into subtasks while defining the estimated time of execution for all of them is not easy. This sin can be common not only with Junior developers but more experienced professionals can also avoid estimates.
In this article, I’ll explain how we encourage our developers to estimate tasks using simple & smart Jira configuration.
Where the problem originates from?
To quickly start a new project in JIRA, our PMs often use the default settings for workflow, fields, screens, etc. These settings are a good fit for a broad variety of projects, which is excellent! However, if you have a more specific task to complete, you’ll need to go deeper into configurations, like in our example. You will have to learn something new, too.