WGU MGT2: IT Project Management

What MGT2 IT Project Management is really about

MGT2 IT Project Management is a graduate-level course at Western Governors University that teaches you how to plan, launch, run, and close an information-technology project without letting it spiral out of control. It shows up in WGU's IT-management graduate programs, so most people who take it are working professionals who already touch technology projects in some way and now need the vocabulary, tools, and discipline to lead them formally. If you have ever watched a project balloon past its deadline or budget, this is the course that gives you the language to explain why and the frameworks to prevent it.

Direct answer: MGT2 is assessed by a performance assessment, meaning you submit written project deliverables that an evaluator scores against a rubric, not a timed multiple-choice exam. To pass, treat the rubric as your checklist, apply core project-management concepts (charters, scope, scheduling, cost, risk, and Agile) to the case scenario you are given, and address every single aspect line before you submit.

Because the assessment is task-based, "studying" here means something a little different than it does for a proctored test. You are not cramming to recall facts under a timer; you are learning the concepts well enough to apply them correctly in a document, and then you are writing clearly and completely enough that an evaluator can check off each rubric requirement. That distinction shapes everything about how you should prepare.

What the tasks cover

The course blends traditional (predictive) project management with Agile approaches, so you are expected to move comfortably between both worlds. Based on publicly available course outlines, the topic areas you should be solid on include:

• Project initiation: business cases, stakeholder identification, and writing a clear project charter that defines objectives and success criteria.
• Scope and requirements: gathering requirements and building a work breakdown structure (WBS) that decomposes the work into manageable pieces.
• Scheduling: sequencing activities, network diagrams, the critical path, milestones, and Gantt charts.
• Cost management: estimating techniques (such as analogous, parametric, bottom-up, and three-point) and budgeting.
• Risk management: identifying risks, assessing likelihood and impact, and planning responses and mitigations.
• Agile and Scrum: sprints, product and sprint backlogs, roles, burndown charts, and retrospectives.
• Monitoring and controlling: tracking schedule and cost performance, earned value analysis, and interpreting project metrics to make decisions.
• Project management tools: evaluating and selecting the right software or method for a given project's needs.

You can confirm the current, official topic list on WGU's own materials. Start at the WGU website and your course page in the learning platform, since the exact task prompts and rubric wording are updated periodically.

How hard it is and how long it takes

Many students describe MGT2 as manageable rather than brutal, especially if they already have workplace exposure to projects. The difficulty is less about intellectual depth and more about thoroughness: performance assessments reward completeness and precision, so the students who struggle usually lose points on missed rubric requirements, not on misunderstanding the material.

Prep time varies widely. Students who move quickly report finishing the deliverables in a week or so of focused effort, while others spread the work across several weeks, particularly when tasks come back for revision. Build in buffer time: evaluations are not instant, and a returned task means another writing-and-review cycle. If this is your first exposure to formal project management, plan for the longer end and give yourself room to learn the concepts before you start drafting.

A study plan that fits a task-based course

Because MGT2 is a performance assessment, your plan should combine genuine concept learning with disciplined, rubric-driven writing. Here is a sequence that works:

1. Read the task and rubric first. Before you study anything, print or copy the task prompt and its rubric. This tells you exactly what deliverables you must produce and what "competent" looks like for each one. Everything you learn afterward has a clear destination.
2. Learn the concepts with active recall. For the terminology-heavy areas (estimating techniques, Agile roles, earned value formulas, network-diagram terms), quiz yourself instead of rereading. Make a short deck of prompts like "What does schedule variance tell me?" and answer from memory. Spacing these reviews over several days locks the vocabulary in far better than one long session.
3. Practice by applying, not just reading. The equivalent of "practice testing" in a PA course is drafting. Take the case scenario in your task and actually build a mini charter, a small WBS, or a simple earned-value calculation. Applying a concept once beats reading about it five times.
4. Draft against the rubric line by line. Write your response with the rubric open beside you. Use the rubric's own language as subheadings in your draft so nothing gets buried, then confirm each aspect is genuinely addressed, not just mentioned.
5. Self-review before submitting. Reread each rubric aspect and ask, "Would an evaluator who has never met me be able to point to the exact sentence that satisfies this?" If not, add it.

MGT2 pairs naturally with other management and operations courses. If you want context on how projects fit into broader technology and business operations, the concepts here connect well with C215 Operations Management, C927 Managing Technology Operations and Innovation, and D370 IT Leadership Foundations. You can also browse the full guide index or the School of Technology hub for related courses.

Common mistakes students make

• Skimming the rubric. The single most frequent cause of a returned task is missing a required aspect. Evaluators score what the rubric asks for, so treat each line as mandatory.
• Answering generically. Tasks are built around a specific case scenario. Writing about project management in the abstract instead of applying it to the given company or situation reads as incomplete.
• Confusing predictive and Agile approaches. If a task asks you to plan sprints, do not hand in a traditional Gantt-driven plan (or vice versa). Match your method to what is asked.
• Math without the work shown. For cost estimating or earned value, show your formulas and inputs. A bare number is hard for an evaluator to verify against the rubric.
• Weak or missing citations. If your program requires sources, follow the expected format. Uncited claims and formatting slips can send a task back even when the content is right.
• Submitting without a self-check. Rushing to submit before mapping every rubric aspect to your text is how strong understanding still earns a revision.

MGT2 Readiness Checklist

Before you submit, make sure you can honestly say yes to each of these:

• Can you write a clear project charter that states objectives, scope, and success criteria for the case scenario?
• Can you build a work breakdown structure that decomposes the project into logical, manageable deliverables?
• Can you sequence activities and identify the critical path on a simple network diagram?
• Can you choose an appropriate cost-estimating technique and explain why it fits the project?
• Can you calculate and interpret basic earned-value measures to judge schedule and cost performance?
• Can you identify project risks and propose realistic responses or mitigations?
• Can you plan and describe an Agile sprint, including backlog, roles, and how progress is tracked?
• Can you point to the exact place in your draft that satisfies each rubric aspect?
• Have you proofread for clarity, formatting, and any required citations?

FAQ

Is MGT2 an OA or a PA?

MGT2 is assessed by a performance assessment. Instead of sitting a proctored objective exam, you submit written project deliverables that an evaluator scores against a rubric. Always confirm the current format on your official WGU course page.

How hard is MGT2?

Many students report that it is manageable, especially with some real-world project exposure. The challenge is thoroughness rather than difficulty: points are usually lost to missed rubric requirements, not to misunderstanding the material.

How long should I expect it to take?

It varies. Some students finish the deliverables in about a week of focused work, while others take several weeks, particularly if a task returns for revision. Give yourself buffer time for evaluation turnaround.

Do I need prior project management experience?

No, but it helps. If the concepts are new to you, learn the fundamentals first (charter, WBS, scheduling, cost, risk, and Agile) and then apply them to the case scenario in your task.

What is the best way to study for a performance assessment like this?

Read the task and rubric before anything else, learn the concepts through active recall, practice by drafting real deliverables, and then write with the rubric open so every required aspect is clearly addressed and easy for an evaluator to find.

What happens if my task is sent back?

A returned task is normal and not a failure. The evaluator explains which aspects need more work; you revise those sections and resubmit. Treat the feedback as a precise checklist for your next pass.