Note: Do not pull from this branch; for project-related files, pull from project-components branch.
Deliverable | Deadline |
---|---|
Beta of Component 1 | Sunday 10-16 |
Beta of Components 2 and 3 | Thursday 10-20 |
Project Version 1.0 | Tuesday 10-25 |
Team Evaluation | Friday 10-28 |
Progress Report | Due |
---|---|
1 | 10-11 |
2 | 10-18 |
3 | 10-20 |
4 | 10-24 |
Focus Points:
-
Using rich media content in Github markdown syntax/ correcting beta of component 1
-
Using screenrecorders and other tools for component 2 of the project
-
Introduce Git bash/Github desktop and advanced technical project management
Deliverables:
- Progress Report 2 (including individual team member status reports)
Focus Points:
-
Review Audience Profile and Analysis
-
Introduce guidelines and specifications for technical documents
-
Issue team progress report 1 (master template --> https://github.com/adavis46/writ350-fa16/blob/project-components/team_documents/reports.md)
Deliverables:
-
Audience Profile
-
Progress Report 1
Resources:
Focus Points:
-
Understand audience and purpose for technical documentation, learning modules, and lesson plans
-
Understand how to research purpose and develop a specific product outline/pitch
Deliverables
-
Task List and Summary Pitch (commit to your master repo)
-
Team Progress Report 1 (commit to your master repo)
Focus Points:
-
Understanding Git
-
Understanding team roles and project management
Deliverables:
- Team Charter (commit to GitHub group repo)