What are the difference between Jobs and Tasks in GroupCamp
This GroupCamp FAQ explains the differences between the project tasks and the jobs of the Scheduling module.
To describe the work to be done by your teams you have the jobs of the Scheduling module and the Tasks application of each project. Depending on your projects and resource types, you can only use jobs, only tasks, or combine both.
Note: There are no links or relations between Tasks/Milestones and Jobs/phases in a project.
In this article:
- Objective of the Scheduling module and jobs: the management of the Resource plan
- Overview of jobs and tasks
- Combine jobs and tasks
- Agile methods and Scrum framework
When you want to have a global view of the workload of your operational resources: the jobs and the Scheduling module are adapted to your needs.
Missions / assignments that are longer than 1/4 of a day.
Ex. A developer on projects, a machine or a person on building sites, a researcher on experiments, etc.
Note: all your colleagues or guests are not necessarily resources. Ex. People in charge of administrative functions, assistance, support, possibly project managers, etc.
Jobs of the Scheduling module allow to book the working capacity of one or more resources for a project.
Examples of jobs (Duration of the working day = 7 hours):
- Need Abby 7 hours / day for 5 days from October 12th to 16th.
- Need a resource that has the Designer role 3.5 hours / day for 5 days from October 12th to 16th
- Need Abby 7 hours / day and John 3.5 hours / day for 5 days from October 12th to 16th.
- Need Abby 7 hours / day and a resource that has the Designer role 3.5 hours / day for 5 days from October 12th to 16th.
The Scheduling module allows to manage:
- The workload of resources: availabilities and overloads.
- Time off and absences of the resources.
- The need of resources with generic roles.
- The Phases to group the jobs.
- The dependencies between the jobs (Finish to start, Start to start, etc).
The jobs work in "Fixed capacity not driven by the effort". Changing the Duration of a job causes the decrease or increase of the Work. Adding capacity (Resource with a load: x hours / day) increases the amount of Work of the job.
Everything is managed according to the well-known formula: Work = Duration x Capacity.
Tasks describe "things to do" with or without assigned users, with or without start or end dates.
Examples of tasks:
- "Homepage of the website".
- "Homepage of the website" assigned to Abby.
- "Homepage of the website" with October 16 as the due date.
- "Homepage of the website" assigned to Abby and John.
- "Homepage of the website" assigned to Abby and John with October 16 as the due date.
- "Home page of the website" assigned to Abby and John from October 12 as the start date and October 16 as the due date.
The Tasks application allows:
- To group the tasks by list.
- To associate an estimated time to each user.
- To manage priorities and natures of tasks with tags.
- To manage the progress of tasks, 10%, 20% ... 100%.
With the jobs you manage the booking of resources on the sites (1 site = 1 project).
Ex .: Week 17, team of 2 painters, 1 platrier and 1 maneuver.
The Scheduling module allows you to manage the availability of your resources and the contents of your projects.
Tasks are used to list and manage the progress of the work to be done.
Ex .: "Kitchen", "Dining Room", "Bedroom 1", etc.
or more detailed: "Kitchen Plaster", "Kitchen First coat of paint", "Kitchen Second coat of paint", etc.
The Scrum framework is mainly used for IT developments but can be applied to other types of projects.
In a Scrum framework, the team is usually in the same room and uses a white board and post-it. The use of software allows the "Scrum master" to prepare and share items and sprints with the team - and - to postpone changes in the software. In the case of a virtual team, the use of software is mandatory to synchronize project members.
With the Tasks app:
- You create your Scrum Item list: "Product Backlog", "Sprint Backlog", "In Progress", "Test", "Completed".
- When a developer starts a new task, he moves the "Sprint Backlog" task to the "In Progress" list and assigns the task.
You can use the Scheduling module and the jobs to manage the duration of your sprints (Phases of the Scheduling module) and resources allocation.