Difference between revisions of "Project Manager"
From LMU BioDB 2015
(Initial transcription of this page.) |
(→Milestones: Give names to milestones.) |
||
| Line 10: | Line 10: | ||
== Milestones == | == Milestones == | ||
| − | === Milestone 1 === | + | === 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. | ||
# 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 12]], [[Week 14]], 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 12]], [[Week 14]], and [[Week 15]]. | ||
| Line 17: | Line 19: | ||
#* Action items | #* Action items | ||
#* Testing results/reports | #* Testing results/reports | ||
| − | #** Bugs/ | + | #** Bugs/feature requests |
#** Question/answer sequences | #** Question/answer sequences | ||
| − | === Milestone 2 === | + | === 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. | ||
| + | |||
# Get periodic updates on progress; in particular, the project’s “place” in the overall flow should be known at all times (transparency). You and your team will be giving a status report in class for the rest of the semester. | # Get periodic updates on progress; in particular, the project’s “place” in the overall flow should be known at all times (transparency). You and your team will be giving a status report in class for the rest of the semester. | ||
# 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. | ||
<!--http://www.stellman-greene.com/ interesting blog posts | <!--http://www.stellman-greene.com/ interesting blog posts | ||
Revision as of 00:29, 2 November 2015
| Gene Database Project Links | |||||||
|---|---|---|---|---|---|---|---|
| Overview | Deliverables | Reference Format | Guilds | Project Manager | GenMAPP User | Quality Assurance | Coder |
| Teams | Heavy Metal HaterZ | The Class Whoopers | GÉNialOMICS | Oregon Trail Survivors | |||
Contents
Guild Members
- Species 1:
- Species 2:
- Species 3:
- Species 4:
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.
- 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 12, Week 14, and Week 15.
- Organize management tools for your team:
- 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.
- Get periodic updates on progress; in particular, the project’s “place” in the overall flow should be known at all times (transparency). You and your team will be giving a status report in class for the rest of the semester.
- Monitor the status of the report-in-progress and other related documentation.
- Coordinate team decisions and action items addressing any unforeseen delays or roadblocks.
| Gene Database Project Links | |||||||
|---|---|---|---|---|---|---|---|
| Overview | Deliverables | Reference Format | Guilds | Project Manager | GenMAPP User | Quality Assurance | Coder |
| Teams | Heavy Metal HaterZ | The Class Whoopers | GÉNialOMICS | Oregon Trail Survivors | |||
