Skip to main content

Open Project Management

User Roles​

Product Owner​

  • A Product Owner must be indicated for each project.
  • The Product Owner is responsible for:
    • Set and check the project deadlines and the progress of the work.
    • Open the tasks and assign to developers.
    • Keep aligned tasks on Open Project with issues/stories/tasks on Taiga

Developer​

  • A project can have one or more developers.
  • A Developer is responsible for take charge of the tasks and implement what is required.

QA​

  • A QA user is responsible for testing the task after the developer set it on "QA (to be tested)" and confirm it or reopen it.

Task Status​

Standard Task Workflow​

  1. A Product Owner create a new task with status "Backlog".
  2. A Product Owner sets task as "Approved for development" and assign it to a developer that can start to work on it.
  3. The Developer sets a task as "In progress" when start to work on it.
  4. The Developer sets a task as "QA (to be tested)" when he finish to work on it.
  5. The QA sets a task as set the task in "In progress" again when the test result is KO.
  6. The QA sets a task as set the task in "Ready for release" when the test result is OK.
  7. A Product Owner sets the task as "Staging" or "Production" when it has been released.
  8. A Product Owner sets the task as "Closed" after it was released in production and we don't have any bugs reported for at least 5 working days.
  9. A Product Owner can set a task as "Abandoned" if it is no longer needed for some reason.
  10. A Product Owner or a Developer can set a task as "On hold" if it is blocked for some reason (missing information, dependency on other tasks, ...).

Kind of tasks​

We have 4 types of tasks:

  • Feature: To be used for complex activities, which can be broken down into smaller tasks.
  • Task: The single activity to be carried out
  • Bug: Task linked to an error
  • Generic Task: Finally, there is a special type of task called "Generic Task" which should be used as little as possible. It is used for those tasks not directly related to development that don't have a complex workflow with tests and releases. For example tasks like "onboarding" or "set up local development environment" can be set as "Generic Task". This kind of task has only 3 states: Backlog, In Progress and Closed.

Timesheets​

Tracking working hours​

It is essential that the hours worked on the various tasks are reported by the end of the working day to allow correct reporting to customers, especially for maintenance projects or with fixed hours / days.

Warning​

  • When marking hours, fractions of an hour go on a base 100, not on a base 60.
  • To understand, an hour and a half should be marked as 1.50 and not as 1.30.
  • We keep half an hour (0.5) as the minimum unit of time.
  • If you really can't do without it because there are micro tasks, you can mark the quarter of an hour as 0.25.