CIS599 STRAYER WK1

Overview

The purpose of this activity is to expose you to the Microsoft Project tool for the purpose of developing a project plan and Gantt chart for a hypothetical 30-day hobby project of your choice. Examples include building a deck, painting the garage, or planting a vegetable garden. Completing this activity will help to jump-start your successful completion of the project deliverables throughout the course.

This activity consists of two parts:

Part 1: Project Introduction or Project Plan

You will outline the project specifics, such as its key objectives, scope, functional requirements, technical requirements, and key components.

Part 2: Gantt Chart

You will use Microsoft Project to create a Gantt chart for your hobby project. Download Microsoft Project to your computer if you don’t already have it installed and familiarize yourself with its features.

• Note: Microsoft Project is available at no cost to Strayer University students. For more information, refer to Microsoft Azure for Education on iCampus.
• You are to create or assume all necessary assumptions to successfully complete this activity.
• You must submit both parts as separate files to the assignment area. Label each file name according to the appropriate part.

Instructions

Part 1: Project Introduction or Project Plan

Write a 3–5 page document in which you:

1. Document the hobby project’s key objectives and scope.
2. Develop the hobby project’s functional and technical requirements.
3. Design the hobby project’s components, including size, shape, and quality.
4. Implement the project according to the chosen design and components.

Part 2: Gantt Chart

Use Microsoft Project to create a Gantt chart in which you:

1. Identify the major and minor tasks, illustrating dependency relationships between activities.

Formatting

This course requires the use of Strayer Writing Standards (SWS). The library is your home for SWS assistance, including citations and formatting. Please refer to the

Library site

for all supports. Check with your professor for any additional instructions. Note the following:

• The preferred method is for the project plan portion of your activity to be typed, double-spaced, using Times New Roman font (size 12), with one-inch margins on all sides.
• Include a cover page containing the assignment title, your name, your professor’s name, the course title, and the date. The cover page is not included in the required page length.
• You are not required to include a source list page for this introductory activity. You will, however, be responsible for citing sources and including a source list page for all of the assigned course project deliverables.

View Rubric

Week 1 Activity – Introduction to Project Management Tools

Document the hobby project’s key objectives and scope. (15%)view longer description

Develop the hobby project’s functional and technical requirements. (20%)view longer description

Design the hobby project’s components, including size, shape, and quality. (20%)view longer description

/ 16 pts

Implement the project according to the chosen design and components. (20%)view longer description

/ 16 pts

Identify the major and minor tasks, illustrating dependency relationships between activities. (15%)view longer description

/ 12 pts

Clarity, writing mechanics, and formatting requirements. (10%)view longer description

Week 1 Activity – Introduction to Project Management Tools
Criteria	Ratings	Pts
12 to >10.79 ptsExemplaryDocumented the hobby project’s key objectives and scope.10.79 to >9.59 ptsCompetentDocumented the hobby project’s key objectives and scope with 1–2 errors or omissions in defining the key objectives and scope.9.59 to >8.39 ptsNeeds ImprovementAttempted to document the hobby project’s key objectives and scope, but left out either the key objectives or scope, key objectives did not meet SMART criteria, or did not specify what was not included in the scope.8.39 to >0 ptsUnacceptableDid not document the hobby project’s key objectives and scope.		/ 12 pts
16 to >14.39 ptsExemplaryDeveloped the hobby project’s functional and technical requirements.14.39 to >12.79 ptsCompetentDeveloped the hobby project’s functional and technical requirements with 1–2 errors or omissions in developing the project’s functional and technical requirements.12.79 to >11.19 ptsNeeds ImprovementAttempted to develop the hobby project’s functional and technical requirements; however, left out either the functional or technical requirements, functional and technical requirements did not meet SMART criteria, or key requirements were missing.11.19 to >0 ptsUnacceptableDid not develop the hobby project’s functional and technical requirements.			/ 16 pts
16 to >14.39 ptsExemplaryDesigned the hobby projects components, including size, shape, and quality.14.39 to >12.79 ptsCompetentDesigned the hobby project’s components, including size, shape, and quality with 1–2 specifications missing.12.79 to >11.19 ptsNeeds ImprovementAttempted to design the hobby project’s components, including size, shape, and quality; however, the components do not include key specifications or key design components are omitted.11.19 to >0 ptsUnacceptableDid not design the hobby project’s components, including size, shape, and quality.
16 to >14.39 ptsExemplaryImplemented the project according to the chosen design and components.14.39 to >12.79 ptsCompetentImplemented the project according to the chosen design and components with only 1–2 components missing without documentation.12.79 to >11.19 ptsNeeds ImprovementAttempted to implement the project according to the chosen design and components; however, result deviated from the chosen design without documentation as to why and failed to include more than five components without documentation as to why.11.19 to >0 ptsUnacceptableDid not implement the project according to the chosen design and components.
12 to >10.79 ptsExemplaryIdentified the major and minor tasks, illustrating dependency relationships between activities.10.79 to >9.59 ptsCompetentIdentified the major and minor tasks, illustrating dependency relationships between activities, but missed 1–2 tasks, subtasks, resources, or time related to the project.9.59 to >8.39 ptsNeeds ImprovementAttempted to identify the major and minor tasks, illustrating dependency relationships between activities; however, chart was not developed in accordance with the systems development life cycle (SDLC), failed to outline key aspects of the planning, analysis, design, and implementation phases, and missed more than five tasks, subtasks, resources, or time related to the project.8.39 to >0 ptsUnacceptableDid not identify the major and minor tasks, illustrating dependency relationships between activities.
8 to >7.19 ptsExemplaryError-free or almost error-free in terms of clarity, organization, writing mechanics, and formatting requirements (0–2 errors).7.19 to >6.39 ptsCompetentMostly free of errors in clarity, organization, writing mechanics, and formatting requirements (3–4 errors).6.39 to >5.59 ptsNeeds ImprovementPartially free of errors in clarity, organization, writing mechanics, and formatting requirements (5–6 errors).5.59 to >0 ptsUnacceptableSerious and persistent errors in clarity, organization, writing mechanics, and formatting requirements (more than eight errors).	/ 8 pts
Total Points: 0

Choose a submission type