rse/procedures/project-management: Misc project flow updates

Author: rkdarst

rse/procedures/project-management.rst

@@ -6,8 +6,6 @@ Project management
    This page is still a working document, discuss anything that
    appears like it should be improved.
 
-
-
 Unfortunately (fortunately?), we need to track where our time goes in order
 to justify the benefits of what we do.  There are two main uses of the
 data:
@@ -24,61 +22,55 @@ data:
    be used to make this reporting a bit easier.
 
 
+Typical project flow
+--------------------
+
+* Someone will contact us somehow.  We try to get them to the garage
+  or a real chat as soon as possible.
+
+* Initial discussion.  If it seems this should be a tracked project,
+  then make the issue
+
 
 Finance time tracking
 ---------------------
 
-For projects with their own funding (external or internal funding), they
-should be marked in Halli.  All other projects (funded by the
+For projects with their own funding (external or internal funding),
+you should get instructions about how to use them.  One thing may be
+marking them in Halli.  All other projects (funded by the
 department's/school's basic funding) is marked to the standard RSE
 project (ask for it), and this time is accounted for at the end of
 each year (using internal corrections).
 
 
 
-Internal time tracking
-----------------------
+Internal tracking
+-----------------
 
 (This section is for our RSEs)
 
 GitLab is used to track all projects and time we spend on them.
-Projects have labels that describe them, and GitLab ``/estimate`` and
-``/spend`` commands are used to record time spent.
+Projects have labels that describe them, there are some Gitlab
+commands, and there are custom commands.
 
 * Be aware that it takes some time to get up to speed with a project.
   This should be considered when making the initial estimate, during
   the first consultation.  When recording time spent, include the time
   it takes to get up to speed and learn whatever else is needed for
   the project.
 
-* Include typical daily overheads into project time (imagine you are a
-  researcher - how much time do you spend doing other support
-  activities?  Use that model).
-
 * When being paid by projects (in the Finance systems), we need to
   *only* record time actually
   spent on that project.  Thus, the rest of your time should still be
   recorded to the common RSE project in the finance system.
 
+
 Day-to-day procedure
 ~~~~~~~~~~~~~~~~~~~~
 
-* Record new projects in GitLab.  Most short garage consultations are
-  not recorded in GitLab, unless there is some sort of extra
-  communication about it.
-
-  * Look through the list of labels and set any relevant labels onto
-    the project.  Use ``/estimate`` to make some time estimate (wild
-    guess - hour? day?  week?  month?)
-
-  * There is an issue template that can be used for basic starting
-    info (and also it is also in :doc:`templates`).
-
-* We discuss the next steps in a weekly meeting, if it's not obvious.
-
-* Each time you spend time on a project, use ``/spend`` to record
-  time.  (for example, ``/spend 4h`` or ``/spend 2d``).
-
+See `the rse-timetracking repository
+<https://github.com/AaltoRSE/rse-timetracking>` for info on how to use
+Gitlab.  But the actual data is in **rse-projects**.
 
 
 Gitlab commands and project metadata