-
Notifications
You must be signed in to change notification settings - Fork 11
Project Management Guide
Work is currently track in the following Github Project : https://github.com/orgs/RolnickLab/projects/8
The status of an issue should be updated accordingly. At the very least, when an issue is detailed enough, status should be set to Ready to be picked up.
Priority is a very important field and should always be set. Priority helps the team manage and select future issues to work on and allows the team to have more autonomy overall.
Priority should be in relation to how urgent an issue is in the context of current project goals.
Ex:
- A feature that has already been committed to by the team and/or is required by a partner in their day-to-day operations would be High priority.
- A feature that has been requested but is an improvement (but not a blocker) for existing workflows would be Normal priority.
- A bug that prevents a core feature of the platform from working would be of Critical priority.
- A bug that is an annoyance or affects a only tiny part of the code base would be Low priority
This is the first level of estimation and is required for all new issues. This estimate is a general, non-committing ball-park estimation.
This should be filled after an preliminary analysis of the task has been done. Its usefulness is to help plan at the sprint level and help with timeline projections and project tracking.
The estimate should be in person-days and should include appropriate time for the applicable steps (analysis, implementation, tests, documentation, review and deployment).