Task Management Tracker
There will be a many-to-many relationship between tasks and users, so you will need a table, perhaps ASSIGNED_TASK, that will have FK to the user and task tables. You will likely have some attributes, e.g. user role (task lead, minion, etc), due date, etc.
I recommend that you make your status columns be a string. Using opaque integers is nice from a computer science perspective, but humans find them annoying.
The updated column can be problematic in its meaning. Often the updated date is actually a property of the event (task completion, change in requirements, etc). I recommend that updated be removed from project and task and you track the date of the action in a child table.
Finally, I recommend that your table names be singular not plural. The name of the table should reflect what is being stored in a row and it is independent of whether the table has 0, 1, or a million rows.