Overview |  | Roles |  | Work Items |  | Views |  | CMMI |  | Index |  | Glossary |

Project Portal
| See Also Documentation Plan Template |
| ### Next Steps Write Documentation |
| Create Documentation Plan ( 2 : GG : 2 : 2.2 ) User Education Specialist
Activity: Create Documentation Plan
User Education Specialist
|  |  |  | Deploy |  |
|  | Participating Roles Responsible: User Education Specialist
### Overview A documentation plan allows you to publish all of the details about the documentation, including planned content, format, scheduling, and resources, to the team so the documentation plans can be aligned with the product plans and agreed upon by the entire team before you start writing. # Entry Criteria Documentation Outlines Outlines are approved for all planned documentation deliverables. Personas Personas are complete. Scenarios Scenarios exist that describe the key user experience scenarios. Iteration Plan Iteration plan for the product is complete. Complete Functional Specifications Functional specifications are complete and provide details on the intended user experience. # Sub-Activities
1 | Estimate Resources and Schedule | From the documentation outlines, determine the amount of work required to create the product documentation. Estimate the resources required to complete the work. Determine what resources are available to complete the work. Map documentation deliverables to milestones on the iteration plan. Develop an estimated documentation schedule.
2 | Determine Documentation Deliverables | Choose a release format. Decide on deliverables (work products). Choose documentation template. Create a project style guide and terminology list.
3 | Write Documentation Plan | Provide schedule and resource estimates for the documentation project. If art will be developed, provide resource needs and art estimates. If documentation will be localized into other languages, provide information on schedule and resources needed. Identify reviewers who will participate in the peer review. Summarize the constraints, assumptions, and dependencies for the documentation project. Include documentation outlines, along with the planned delivery format, and pointers to documentation templates and the project style guide.
4 | Get sign-off on the documentation plan from the team | Hold a meeting to discuss planned documentation deliverables. Send the documentation plan to key project stakeholders. Provide a deadline for comments. Incorporate review comments and publish final documentation plan to project portal.
# Exit Criteria
| Documentation plan complete.
| Project style guide is available.
© 2005 Microsoft Corporation. All rights reserved. MSF for CMMI Process Improvement: 1.00.0000.00 |