CMGT/410 - Project Planning and Implementation
Course Description
This course provides the foundation for successful project planning, organization, and implementation within the realm of information technology. The course uses real-world examples and identifies common mistakes and pitfalls in project management. Topics covered include project scoping, estimating, budgeting, scheduling and staffing, tracking and controlling, and software tools for project management.
This undergraduate course is 5 weeks.
PLEASE NOTE:
Attendance and participation are mandatory in all university courses, and specific requirements may differ by course. If attendance requirements are not met, a student may be removed from the course. Please review the Course Attendance Policy in the Catalog for more information.
Course Objectives
Week 1
- Define project, project lifecycle, and software development lifecycle.
- Explain the roles on a project team.
- Describe the critical differences between managing IT and non-IT projects and how these differences affect project management.
- Compare the Agile and waterfall project management approaches.
Week 2
- Explain the benefits and drawbacks of off-the-shelf vs. a custom approach to software development.
- Isolate the challenges associated with managing the beginning of a project.
- Relate the role of project definition and scope to documentation in the context of the project lifecycle.
- Create either a business requirements document and work breakdown schedule (waterfall project), or a product requirements document and user stories/scenarios and acceptance criteria (Agile project).
Week 3
- Compare the benefits and drawbacks of top-down and bottom-up budgeting.
- Illustrate the five most common project hazards and consider approaches for mitigating each.
- Identify project documents that support the goals of project-related communication.
Week 4
- Analyze how scope creep can negatively affect project success, and how it can be identified and managed.
- Construct at least two approaches to testing and bug reporting.
- Explain how to identify and mitigate problems that commonly appear in the middle or near the end of a project.
Week 5
- Outline a plan for user acceptance testing.
- Create a strategy for accepting, differentiating between, and handling bug and feature requests.
- Categorize each of the components of performance testing in terms of their contribution to overall project success.
Prerequisites
NoneDisclaimers
The University of Phoenix reserves the right to modify courses.
While widely available, not all programs are available in all locations or in both online and on-campus formats. Please check with an Enrollment Representative.
Transferability of credit is at the discretion of the receiving institution. It is the student’s responsibility to confirm whether or not credits earned at University of Phoenix will be accepted by another institution of the student’s choice.