ROSSyndicate_best_practices/04-Project-Management.Rmd at main · rossyndicate/ROSSyndicate_best_practices · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
---
editor_options:
  markdown:
    wrap: 80
---

# Project Management and Tracking with GitHub Projects

We use GitHub Projects to track progress and assign tasks to collaborators. A
project is a user interface that integrates with your issues and pull requests
on GitHub to help you plan and manage your work effectively. For Matt R, this
will be where he can go to see quickly where a project is at on its
deliverables, so it is important to keep it up to date. Projects have immense
flexibility and can be tailored to fit the needs of any project.

## Github Project best practices

-   Frame the Project tasks around the statement of work/objectives of the
    project.

-   Take advantage of tags to easily filter and peruse different types of tasks.

-   Break down large tasks into GitHub issues that can [ideally] be completed in
    a single pull request.

See also [GitHub's
document](https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/best-practices-for-projects)
of best practices.

## GitHub Project additional reading

GitHub Projects:
<https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects>

Example *Project*: <https://github.com/orgs/ROSSyndicate/projects/4>

```{r, echo = F}
knitr::wrap_rmd('04-Project-Management.Rmd', width = 80, backup = NULL)
#note, this will not wrap text that are prefaced by any special characters (like bullets!)
```