How to use Taskomat™ if you are a programmer?
If you are a programmer, or developer, Taskomat™ is simply the perfect software to manage your workflow.
Structuring a development project with Taskomat™ is both very simple and useful, since with Taskomat™ you can track the time and budget of every single part of the project.
To create a project in Taskomat™ it is necessary to create the work units, i.e. all the parts of the project needed to complete it, each with its own budget and time limit.
The total budget and time limit of the project will be determined by the sum of the individual budgets and time limits of the work units that make up the project.
When you go to set up your development project, you will have to create as many work units as there are phases you need to complete your project, for example: preliminary analysis, back-end development, front-end development, etc.
Let's see now a small example of a development project created and managed with Taskomat™, in order to make the process clearer.
Project: Mobile app development
Project phases: Preliminary analysis; Back-end development; Front-end development.
Let's suppose that your reference rate is 50€, each of these 3 phases will have a budget and a time limit calculated on the basis of the reference rate.
Work unit: Preliminary analysis (2 days to collect the information):
- budget: 800€
- time limit: 16h
Work unit: Back-end development (5 days to develop the back-end):
- budget: 2000€
- time limit: 40h
Work unit: Front-end development (5 days to develop the front-end):
- budget: 2000€
- time limit: 40h
In total you have a project with a budget of 4800€ and a time limit of 96 hours.
Once you have created the work units, you will have to create timed tasks to schedule on your days.
Preliminary analysis (time limit: 16h):
- Meeting with client (2h)
- Preliminary Requirements Analysis (8h)
- Meeting with client (2h)
- Review of requirements analysis (4h)
Schedule on: Monday 8 April, Tuesday 9 April, Monday 15 April, Tuesday 16 April
Backend development (time limit 40h):
- Database creation (4h)
- Data model creation (8h)
- API Gateway creation (8h)
- Payment setup (8h)
- Registration and login (8h)
- Bugfixing (4h)
Schedule on: Monday, April 22, Tuesday, April 23, Wednesday, April 24, Friday, April 26, Saturday, April 27, Monday, April 29, Thursday, May 2, Friday, May 3
Frontend development (time limit 40h):
- UI structure creation (8h)
- Form creation (8h)
- JS animation creation (8h)
- Error management (8h)
- Cross platform testing (8h)
- Bugfixing (4h)
Schedule on: Tuesday, April 30, Thursday, May 2, Friday, May 3, Monday, May 6, Tuesday, May 7, Wednesday, May 8, Thursday, May 9, Friday, May 10.
Once the tasks are scheduled, you can decide whether to do time tracking or just declare them as completed.
In our example, you can time-track and measure your performance on all the tasks that are not related to the client meetings, while for the meetings you can simply declare them as completed.
By structuring your work in this way, you will be able to understand how long it takes you to complete the various project phases that are not tied to client meetings, and whether this time is in line with your budget and revenue goals.
