Difference between revisions of "Project Manager"

From LMU BioDB 2019
Jump to navigation Jump to search
(Guild Members: added member)
(Guild Members: paste in team names)
 
(2 intermediate revisions by the same user not shown)
Line 5: Line 5:
 
== Guild Members ==
 
== Guild Members ==
  
* Naomi Tesfaiohannes
+
* [[Sulfiknights]]: Naomi Tesfaiohannes
* Michael Armas
+
* [[FunGals]]: Michael Armas
* Aby Mesfin
+
* [[Skinny Genes]]: Aby Mesfin
  
 
== Milestones ==
 
== Milestones ==
Line 17: Line 17:
 
# In consultation with your team, work backward from the final deadline to set intermediate deadlines for each deliverable. In particular you need to set deadlines for what you will accomplish by the journal deadline for [[Week 11]], [[Week 12/13]], and [[Week 15]].
 
# In consultation with your team, work backward from the final deadline to set intermediate deadlines for each deliverable. In particular you need to set deadlines for what you will accomplish by the journal deadline for [[Week 11]], [[Week 12/13]], and [[Week 15]].
 
# Organize management tools for your team:
 
# Organize management tools for your team:
 +
#* Communication tools
 
#* Workflow narratives
 
#* Workflow narratives
 
#* Action items
 
#* Action items
Line 28: Line 29:
  
 
# Get periodic updates on progress; in particular, the project’s “place” in the overall flow should be known at all times (transparency). Team members will be giving a status reports in class for the rest of the semester.  However, the instructor will expect you to know and be able to report on the status of each member of your team at any time.
 
# Get periodic updates on progress; in particular, the project’s “place” in the overall flow should be known at all times (transparency). Team members will be giving a status reports in class for the rest of the semester.  However, the instructor will expect you to know and be able to report on the status of each member of your team at any time.
# Familiarize yourselves with the specific milestones of [[Quality Assurance|each]] [[Coder|team]] [[Data Analysis|member]] so that you know how to monitor the team’s overall progress.
+
# Familiarize yourselves with the specific milestones of [[Quality Assurance|each]] [[Coder/Designer|team]] [[Data Analysis|member]] so that you know how to monitor the team’s overall progress.
 
# Monitor the status of the report-in-progress and other related documentation.
 
# Monitor the status of the report-in-progress and other related documentation.
 
# Coordinate team decisions and action items addressing any unforeseen delays or roadblocks.
 
# Coordinate team decisions and action items addressing any unforeseen delays or roadblocks.

Latest revision as of 14:40, 18 November 2019

Final Project Links
Overview Deliverables Guilds Project Manager Quality Assurance Data Analysis Coder/Designer
Teams FunGals Sulfiknights Skinny Genes

The project manager makes sure that individuals are fulfilling their roles and performing the tasks on time.

Guild Members

Milestones

Milestone 1: Project “Scaffolding”

This milestone pertains to setting up an initial schedule and any resources that your team will use for the duration of the project. It will be useful to get an overview of every team member’s own milestones so that you have an accurate big picture view.

  1. In consultation with your team, work backward from the final deadline to set intermediate deadlines for each deliverable. In particular you need to set deadlines for what you will accomplish by the journal deadline for Week 11, Week 12/13, and Week 15.
  2. Organize management tools for your team:
    • Communication tools
    • Workflow narratives
    • Action items
    • Testing results/reports
      • Bugs/feature requests
      • Question/answer sequences

Milestone 2: Periodic Updates

Not as much a milestone as an on-going task, once the project is up and running the Project Manager is responsible for keeping track of everyone’s progress.

  1. Get periodic updates on progress; in particular, the project’s “place” in the overall flow should be known at all times (transparency). Team members will be giving a status reports in class for the rest of the semester. However, the instructor will expect you to know and be able to report on the status of each member of your team at any time.
  2. Familiarize yourselves with the specific milestones of each team member so that you know how to monitor the team’s overall progress.
  3. Monitor the status of the report-in-progress and other related documentation.
  4. Coordinate team decisions and action items addressing any unforeseen delays or roadblocks.


Final Project Links
Overview Deliverables Guilds Project Manager Quality Assurance Data Analysis Coder/Designer
Teams FunGals Sulfiknights Skinny Genes