October 23, 2025 Claire B 0 Comments

DeVry MGMT404 Week 1 Course Project Latest 2016 November

Week 1

Due Week 1: Project Proposal/Approval

Each professor will decide if the course will have project teams or be assigned to each individual student to complete the course project. Your professor will notify you of the decision and if the course is going to have project teams, you will be notified of your team assignment.

If the professor assigns individual projects, your Week 1 assignment will be to:

Provide an outline of your proposed project to your instructor for approval. The project you select will be the same project you will plan for the 8 week course.

If the professor assigns teams for the course project, your team will work together to complete the entire Statement of Participation template located in the doc sharing area. All sections for the entire 8 weeks must be completed.

Deliverables for Week 1:

If you are assigned individual projects:

  • A one-page document outlining your proposed project. This document should contain particulars, such as what will be created, why this project is important, how long it would likely take, and how much it would likely cost.

If you are assigned team projects:

  • Teams need to complete the entire Statement of Participation with the team and team leader assignments for Weeks 2–8. Lastly, teams need to update the status of participation for Week 1.

DeVry MGMT404 Week 2 Course Project Latest 2016 November

Week 2

Due Week 2: Project Charter

Provide a project charter of your selected project in accordance with the charter template found in Doc Sharing.

Please put this in proper business writing format. Consider me to be your boss. If working in a group, include the updated Statement of Participation for Week 2, describing how each person contributed to this project deliverable. Please place the updated Statement of Participation in your teams’ Doc Sharing area for review. A charter should be a minimum of 3–5 pages long.

Deliverables for Week 2:

  • Completed Project Charter (in MS Word)
  • Statement of Participation and status update

Project Name

Project Number

Project Team

Prioritization

Owner(s)

Start
Date:

Scheduled
Completion Date:

NOTE: Remove this note and all instructions in the
template for a business professional document.

Mission/
Purpose

What is your
project going to accomplish? How does this project relate to overall strategic
goals and objectives of the company?Is it part of a program or larger
project?

Project

Description and
Project Product

What will this
project create? What are the outcome products being created with this
project? At a high level, how do you plan on completing the work required for
this project?List at least five high-level deliverables (outputs) that will
be generated from the execution of this project. This section will help to
prepare for your project scope and WBS later in the course.

Objectives

What objective is
this project designed to meet? List a high-level objective statement for the
overall project and at least three to five goals required to meet this
objective. These must be measurable.For example, if an objective of the
project is the cut cost, then by how much will costs be cut?

Business
Need

Why should we do this project?What will be
gained, changed, or modified?Is there a financial or business reason to do
this project?Explain, in detail, how this project will be beneficial to the
project owner.

Milestones

What
are the key milestone dates associated with the project? Milestones may show
the completion of a set of major deliverables or phases.List at least 10
milestones and provide estimated end dates for each.Milestones must have
associated dates.

Budget

What
is the estimatedbudget for this project? Do not research your project cost;
this is an estimate. This does not need to be close to your project’s actual
costs when your project planning is complete in Week 6.This is an order of
magnitude estimate.

Estimated
Labor

Estimated
Materials

Estimated
Contractors

Estimated
Equipment and Facilities

Estimated
Travel

Total
Estimated Cost

User
Acceptance Criteria

What
are the minimum success criteria as defined by the key stakeholders?How will
you monitor and measure the project quality?How will the project owners
determine if the project is a success or not?These must be detailed and
measureable.

High-Level
Project Assumptions

What are the
assumptions on which the project is based? What 7–10 statements do you
believe to be true or will become true about the project during project
executionbut cannot be sure at this time?

High-Level
Project Constraints

What
are the major limiting factors that affect the project?What 8–10 rules, regulations,
requirements, laws, processes, or procedures are you bound by on this
project?

Exclusions
and Boundaries

What are the
boundaries of the project? To ensure that your project scope is properly constrained,
identify 8–10 things that will beexcluded from the project plans.What items
will be not be included in the project?

Major
Risks

What
are the major risks affecting the project? List a minimum of 7 to 10 risks.These
risks must occur during the project, not after the project finishes or before
the project starts. The risks defined should be directly associated with the
project implementation.


KEY
STAKEHOLDERS

Project Manager
Authority Level

Project Core Team

Subject Matter
Experts (SMEs)(What
resources will you need with special expertise?)

APPROVALS

Type Name

Signature

Date

Project Manager
Approval

Customer/Sponsor
Approval

DeVry MGMT404 Week 3 Course Project Latest 2016 November

Week 3

Due Week 3: Scope Statement

Prepare a scope statement using the template in Doc Sharing. Remember to be tangible, measurable, and specific. Be sure to include all sections required in the Week 2 Lecture. A scope should be a minimum of 3 pages long.

Deliverables for Week 3:

  • Project Scope Statement (in MS Word)
  • Statement of Participation and status update

Project Scope
Statement

Project Name

Project Number

Project Manager

Prioritization

Owner(s)

NOTE: Remove this note and all
instructions in the template for a business professional document.

Statement
of Work—Project Descriptionand

Project Product

In
this section of the scope statement, we specifically elaborate on what the
project will create. One should also discuss here how the project team plans
to accomplish this project. This section should be quite detailed, because it
creates the basis for the entire project and prepares you for development of
your upcoming WBS. Here you should list the high-level tasks and describe how
each task will be executed for the project. This section should be based on
information found in the project’s charter. For example,a software
development project would have an overall description (two to three
paragraphs explaining the project product).This would be followed by 7–10
pages going into detail about the work being completed on the project.

Project
Deliverables

What are the tangible outputs or services
of this project? What big-picture items will have to be created or performed
in order to accomplish the statement of work?These are a list of items that
will be the result of the execution of the project work packages in the WBS.
For example, if your task is to develop software program for application A,one
of your deliverables will be software application developed. The project
examples in this class normally have 10 to 15deliverables.

Project
Objectives

What
are the cost, schedule, and quality objectives of this project? Your
objective statement is likely to be the same or similar as in your project
charter, based on any new knowledge. Here you might add goals for the
project. Objectives can and often do look past the end for the project, such
as an example of cutting costs in operations by 15%.It is highly possible
that your project objective will have some subobjectives or goals. For
example, the project objective for the software project might be as follows.

The
objective of this project is to develop a new programming application for the
payroll department that will interface with the existing Kronos system by
10/12/2014 at a budgeted cost of $50,000. The goals of the project include
the following.

·
Create a
newly developed program that will be installed and tested by users.

·
Install
and load server hardware required for the application and database
environment.

Project
Assumptions

What
are the assumptions on which the project is based? Project assumptions are
those things we believe to be true without proof for planning purposes. For
our software development, we might assume that users will be available to
test when needed. We have no way to know this for sure during project
planning; thus, it is an assumption for our project. You should have at least
15–20 assumptions.

Project
Constraints

What are the major limiting factors that
affect the project?Project constraints are limitations placed upon the
project. Many of them are placed by individuals outside of the project. These
limitations could be laws, regulations, rules, policies, procedures, or
customer or sponsor requirements.Let’s say we are limited to access for 10
users to test the new application. Thiswould be a constraint of resources
available to test the project. You should have at least 10–15 constraints.

Exclusions

What
are the boundaries of the project? What is not going to be included in the
project? This helps the project manager to set boundaries on the project scope.
For example, on our software development project, we might exclude some
specific functionality on the program. Let’s say Internet access for credit
card payments will not be included in the programming for this project. You
should have at least 10–15 exclusions.

Acceptance
Criteria

Develop a checklist that will be used by
the customer to measure your performance for the project. This includes the
following: What must the product be able to do when completed to be
acceptable to the customer?What standards or regulations must the product
meet? What performance specifications must the product meet to be acceptable
to the customer?For example, the new application developed must be installed
in accordance with the standard equipment and specifications; functionality
tested by the user and accepted prior to implementation.

Technical
Requirements

What is needed to make this project
functional in terms of equipment, computers, cash registers, and so forth?What
functionality must it have? In our example, there would be specific types
of hardware required, such as 2 HP Proliant DL580 G7 high performance
servers are needed for the application software program execution and
database storage.This section should be three to five pages, depending on
the project you selected.

APPROVALS

Type Name

Signature

Date

Project Manager Approval

Customer or Sponsor
Approval

DeVry MGMT404 Week 4 Course Project Latest 2016 November

Week 4

Due Week 4: Work Breakdown Structure

According to the PMBOK® Guide, “the WBS is a deliverable-oriented hierarchical decomposition of the work to be executed by the project team, to accomplish the project objectives and create the required deliverables.” In other words, it lists the project’s deliverables and work packages. For this week, you will create a work breakdown structure (WBS) for the project you selected during Week 1.

Remember that the WBS starts with your major deliverables (that you stated in your scope management plan) at the highest level. The lower levels have the work package required to complete those deliverables. Review the textbook (and the PMBOK® Guide, if you have it) for some suggestions on how to create a WBS. From your work breakdown structure, develop a project task list with dependencies and add durations, using MS Project.

Develop the Work Breakdown Structure

  • Your WBS should have a minimum of 100–150 line items in MS Project and be three levels deep.
  • Make sure to use verb-object task names (for example, “Develop software”).
  • Enter tasks in MS Project.
  • Create the predecessor relationships.
  • DO NOT LINK SUMMARY TASKS OR ASSIGN RESOURCES!

Deliverables for Week 4:

  • Statement of Participation and status update
  • The MS Project file (.mpp) saved from the Tracking Gantt chart screen

DeVry MGMT404 Week 5 Course Project Latest 2016 November

Week 5

Due Week 5: Risk Management Plan

Remember, risk is an uncertain event or condition that can have a positive or negative impact on the project. This week, you will be identifying and analyzing your project risks and developing a risk management plan to monitor and track your project. You will evaluate each task in your project schedule to identify any risk factors associated with the execution of the deliverable. You will then add your list of risk to the risk register template in Doc Sharing. The number of risks will depend on the project deliverables in your schedule; however, 20–25 positive and 20–25 negative risks would be considered the minimum. Review the instructions on the first sheet of the template and complete your risk register in its entirety.

Deliverables for Week 5:

  • Use the Risk ter Template spreadsheet found in Doc Sharing (there is a separate tab for each portion of the risk management plan).
  • Statement of Participation and status update

MGMT-404 PROJECT MANAGEMENT
STATEMENT OF PARTICIPation

This document will contain the information needed for your team operations, guidelines and commitment. It should be kept in doc sharing and each update should have a version control identifier (e.g., Team A SOP v1, v2, v3, etc.).
IMPORTANT NOTE:The statement of participation must be posted in the team’s doc sharing area and the final submission must be available for the team to review and approve each week. Approval can be achieved by downloading the document. If you have disagreements, it is critical to contact your project leader and get a correction posted immediately. The professor should be notified of any disagreements. If the statement of participation is not submitted, the entire team will receive the same grade (including any point loss from other team members).
I. Team Information

PROJECT NAME:

MEMBER NAME

#

PHONE #

EMAIL

MEETING AVAILABILITY

1

2

3

4

5

6

7

II. Weekly meeting schedule

The most successful teams schedule at least (2) meetings a week throughout the course. Scheduling standing meetings allows everyone to schedule this time in advance and coordinate other activities around the scheduled meeting times. Meetings can change, based on the project leader for the week, however, it is highly recommended that you set a meeting based on the majority team availability. In addition to setting meetings, the most successful teams also set a deadline for drafts to be turned into the project leader each week. Putting this structure in place early in the course will help the team to achieve a high level of organization and success.

MEETING

DAY

TIME

Review weekly assignment

Deadline for weekly drafts

Review Draft

III. PROJECT Description

Brief synopsis of your proposed project in 200 words or less. Describe the overall project with enough information to gain approval for your team to use this project as the course project. If you are working on a project in the instructions, you do not need to gain approval. Approval is only needed if you select a project outside of the list in the course project instructions.

IV. Team Management Plan

a. Team Leadership: Designate the project leader for each major deliverable. Project leader can be rotated so that each team member experiences the leadership responsibilities or you can establish one primary project leader with a back-up to assist.The project leader has specific responsibilities each week as follows:

a. Schedule the weekly meetings in i-Connect, facilitate and record the meetings.

b. Set the deadlines for submissions each week.

c. Compile the team submissions into one document and submit to the dropbox. “ONLY ONE” submission is required and this is submitted by the project leader.

d. Update the statement of participation status each week and submit to dropbox for the team review.

e. Place the final submission and updated statement of participation in the team’s doc sharing area each week.

f. Contact the professor with any team questions, issues, or conflicts.

Weekly Deliverable

Due

Weekly Project Leader Assignment

Statement of Participation

Week 1

Project Charter

Week 2

Project Scope Statement

Week 3

WBS and Network Diagram

Week 4

Risk Management Plan

Week 5

Resource Management Plan

Week 6

Communications Plan

Week 7

Final Project

Week 8

b. Task assignments: How will tasks be assigned? Every team member should have an active role in creating the tasks for each major deliverable. All (8) weeks of assignments must be completed.

Week 1: Statement of Participation

Team Member Responsible

· Team Information

Each team member submit to project leader

· Project Leadership

Each team member submit to project leader

· Task Assignments Weeks 1-8 (Each project leader can assign the task for their week or team members can select what they want to work on each week).

Project leader for Week 1

· Commitment statement

Each team member submit to project leader

· Weekly Status Update

Project leader for Week 1 update the status update at the end of the SoP document and submit to dropbox and place copy in doc sharing for team review.

Week 2: Project Charter

Team Member Responsible

· Mission/Project Purpose

· Project Description, Product and deliverables

· Objectives

· Business Need

· Milestones

· Budget

· User Acceptance Criteria

· Project Assumptions

· Project Constraints

· Exclusions and Boundaries

· Major Risks

· Project Stakeholders

· Weekly Status Update

Project leader for Week 2 (submit final assignment and SoP to dropbox and place copy in doc sharing for team review)

Week 3: Scope Statement

Team Member Responsible

· SOW and Project Product

· Project Deliverables

· Project Objectives

· Project Assumptions

· Project Constraints

· Exclusions

· Acceptance Criteria (includes table format for quality signoff).

· Technical Requirements

· Weekly Status Update

Project leader for Week 3 (submit final assignment and SoP to dropbox and place copy in doc sharing for team review)

Week 4: WBS /Project Schedule

Team Member Responsible

The best approach to divide the work task and assign each team member a section or responsibility (e.g., Planning phase, Purchasing Phase, etc.). Then assign someone to setup durations, dates and predecessors. Resources can be defined on the resource sheet, but remember…no resources are assigned to the project tasks at this point.

· Project Schedule WBS (task definitions, durations, dates, predecessors, etc.)

· Weekly Status Update

Project leader for Week 4 (submit final assignment and SoP to dropbox and place copy in doc sharing for team review)

Week 5: Risk Management Plan

Team Member Responsible

The best approach to divide the work is to assign each team member a specific number of risk, for example John has negative risk 1-5, Jane has negative risk 6-10. This information is needed in order to assess each “individuals” contribution.

· Risk ter

· Weekly Status Update

Project leader for Week 5 (submit final assignment and SoP to dropbox and place copy in doc sharing for team review)

Week 6: Resource Management Plan

Team Member Responsible

· Assign resources and costs to the project with any materials, equipment or fixed cost allocations.

· Project Budget Report

· Resource management report

· Weekly Status Update

Project leader for Week 6 (submit final assignment and SoP to dropbox and place copy in doc sharing for team review)

Week 7: Communications Plan

Team Member Responsible

This is a short assignment because of the quiz. There is no division necessary, however each team member must provide input to the person responsible for completing the form. The best approach is to have a team meeting in i-Connect and discuss completing the template. All team members must attend the meeting and provide input to receive credit for this section. The project leaderer for this week should complete the template and submit it to the dropbox.

· Communications Plan Template

· Weekly Status Update

Project leader for Week 7 (submit final assignment and SoP to dropbox and place copy in doc sharing for team review)

Week 8: Final Project Package

Team Member Responsible

· Executive Summary (Overview of the project and current updates in 2-3 pages)

· Project Charter

· Scope Statement

· Work Breakdown Structure

· Risk Management Plan

· Project Schedule and Budget (.mpp file)

· Communications Management Plan

· Weekly Status Update

Project leader for Week 8 (submit final assignment and SoP to dropbox and place copy in doc sharing for team review)

NOTE FOR WEEK 8: If the assigned person places the updated component in the template each week after grades are complete, you will be building the final project. If everything works out with the updates, the only thing to do in week 8 review the contents, format the document for consistency and professionalism and you’ll be ready for submission.

V.TIPS FOR CONFLICT MANAGEMENT RECOMMENDATIONS

a.Think about potential barriers and coping strategies such as barriers to the achievement of the assigned goals, e.g. time zone,time management, language skills, and identify coping strategies.

b.

Order a similar assignment, and have writers from our team of experts write it for you, guaranteeing you an A

Order Solution Now

Categories: