Drafted 'project management' section with an emphasis on brevity (hop…

…efully still clear enough)

CONTRIBUTING.md

@@ -1,6 +1,6 @@
 # SSECR Contributing Guidelines
 
-## Accessing SSECR Materials
+## Accessing Course Materials
 
 ### GitHub
 
@@ -12,10 +12,18 @@ Contact Marty Downs and/or Nick Lyon to be added to the SSECR GitHub Team. This
 
 Contact Marty Downs and/or Nick Lyon for access to the Google Drive. The Shared Drive is named "LTER-Grad-Course".
 
-## Project Management
+### Communication
+
+Communicating via email is fine though we also have a channel (`#lter-grad-course`) in [NCEAS](https://www.nceas.ucsb.edu/)' Slack organization if that is preferable.
 
+## Project Management
 
+- Individual tasks should be tracked as [GitHub Issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/quickstart)
+    - Be sure that each task is **SMART** (i.e., specific, measurable, achievable, relevant, and time-bound)
+- Use the issue template and try to document your progress as you work on a given task
+- Strategic planning (i.e., across all tasks) should use the [SSECR GitHub Project](https://github.com/orgs/lter/projects/6/views/1)
+    - Task lifecycle can be tracked by dragging an issue's "card" among columns that correspond to major steps in task completion
 
 ## Style Guide
 
-As much as possible, use snake case (i.e., all_lowercase_separated_by_underscores). If in doubt, maintain consistency with the naming convention and internal structure of other files in the same directory/repository.
+As much as possible, use snake case (i.e., all_lowercase_separated_by_underscores). When in doubt, try to maintain consistency with the naming convention and internal structure of other files in the same directory/repository.