Document the requirements for your project. At a minimum, you should identify three-to five-high level requirements, functions, and features and fifteen-to twenty-five-detailed requirements. The requirements you identify will be used as the basis for the WBS.

Note. Provide the appropriate level of detail while maintaining a reasonable number of requirements since you will base your planning and scheduling on these requirements.

Format your requirements in one of two ways:

Simple Sentence format that outlines the high-level parent requirements and then breaks these down into multiple user requirements, which then flows into system requirements. "The system SHALL..."

User Stories format, you will have high-level requirements known as Epics and in each Epic, you will have multiple User Stories that follow the formatted language: As a ROLE, I need a FUNCTION, so that I can, BUSINESS VALUE.

Prepare your requirements documentation for both Simple Sentence format and User Stories format in any format you would like: Word document, Excel worksheet, Visio diagram, online drawing tool.

Note. Remember, your requirements should represent ALL the deliverables in your project.

Part II: Work Breakdown Structure

Create a WBS that identifies the following:

Summary tasks

Detail tasks

Milestones

Project management deliverables and tasks

Note. While there is no minimum or maximum number of tasks, the expectation is that you will have between 55 100 tasks in your WBS. If you intend to use the MS Project tool to complete your project plan, your WBS should be created in Excel. MS Project can import the Excel document to create the initial project plan.

Cite any research or templates used consistent with APA style guidelines.