watchers

Schedule

The anticipated duration for Q1-3 Features is eight months. Development will begin at the start of Q1, and must be completed no later than the end of Q3. Current estimates are listed on the tables below, and are subject to change.

Summary

Documentation Development Schedule

M indicates a milestone in the software development process. It is the goal of Documentation to work in-step with Software throughout the development of **Q1-3 Features.

January

February

March

April

May

June

July

August

1

2

3

4

5

1

2

3

4

1

2

3

4

1

2

3

4

5

1

2

3

4

1

2

3

4

1

2

3

4

5

1

2

3

4

Research and Planning

Project Plan

PM

x

Content Plan

Editor

x

Minor changes (if appl.)

Editor

x

Approval of the Project Plan

M

Interviews of SMEs

Researcher

x

x

Gathering of information

Researcher

x

Analysis of information

Writers

x

Creation of point-form draft

Writers

x

x

x

x

x

x

Revision of point-form draft

Editor

x

x

x

Creation of complete draft for reusable content

Writer 1

x

x

x

Term definition

Writer 1

x

Feature definition

Writer 1

x

Feature use overview

Writer 1

x

Step-based task

Writer 1

x

Benefits overview

Writer 1

x

Product specification

Writer 1

x

Troubleshooting

Writer 1

x

Approval of the Content

M

Creation of graphic layout

Writer 2

x

x

x

x

Integration of video content

Writer 2

x

x

Revision of graphic layout

Writer 2

x

x

Generation of content

Writer 2

x

User manual

Writer 2

x

Help file

Writer 2

x

Quick start guide

Writer 2

x

Tooltips

Writer 2

x

Datasheet

Writer 2

x

Marketing brochure

Writer 2

x

Marketing website

Writer 2

x

Education/e-learning content

Writer 2

x

Review of generated content

Editor

x

Approval of the Final Review by Editor

M

Implementation

Implementation in wiki

Writers

x

Review of implementation

Editor

x

Content Implemented in Wiki

x

M

Quality Control and Testing

Document is Sent to QA for Testing

M

x

x

Review of QA notes

Editor

x

Changes based on QA notes

Writers

x

x

Review

Editor

x

Final Approval

M

Final production

Editor, Project Manager

x

Dependencies and Risk Mitigations

The Documentation plan stands on its own, until the quality control and testing need to be done. This milestone depends on the Software Development team to be ready to test the software at least before the Development team is ready to test the documentation. Listed below are possible risks (along with their likelihood and impact) and mitigation strategies to minimize the risks.

Risk and Mitigation

Risk

Likelihood

Impact

Mitigation Strategies

Unanticipated additional work

Low

High

Include additional time in the schedule;
Inform VP of Documentation if additional work causes delays or additional costs

Disruption in software used to complete work

Med

Med

Carry the work into after-hours periods

Disruption in team members' availability

Med

High

Shifting of responsibilities;
Add temporary team members to cover the basic responsibilities