Take My Liberty MGMT 625 Class

Wilson's guide is read one or two chapters a week. The first chapters set out why schedule and cost control matter and how most schedule failures start with weak planning rather than poor execution.

The next chapters turn to scope and the work breakdown structure: decomposing deliverables into work packages, the hundred percent rule that the children of each element must add up to the whole, and the habits that make a WBS easy to schedule and cost.

By the middle weeks the book is constructing the schedule: listing the activities each work package needs, linking them in logical order, sizing their durations, tracing the longest path and guarding the slack around it.

Later chapters cover resources, cost and the control of a schedule once work begins, including how to measure slippage and respond to it.

Each module has one or two short presentations. Discussions open in odd weeks and close in even weeks; the blog falls in week two, the plan in week four, the WBS in week six and tests in weeks three, five and eight.

MGMT 625 is carried around a single project chosen in week one from the five sectors the course allows: construction, information technology, higher education, city government or health care.

A good choice is concrete and mid-sized, such as a community college fitting out a nursing simulation lab, a city replacing its building-permit software, or a clinic adding an urgent care wing.

The plan is written in Word for that project. It describes the project, sets its scope, cost and objectives, names team roles and responsibilities and key stakeholders, lists assumptions and constraints, and includes plans for communication, risk and change management, each written for this project rather than copied from a template.

The WBS then decomposes the plan's scope. Its top box is the whole project, the next tier holds the main deliverables and the lowest tier holds packages of work, each coded so it points back to a line of the plan. It can be delivered as a hierarchy chart, a mind map or a Gantt chart built in Excel, Word or Project, kept to one or two pages.

Discussion answers run past five hundred words with a pair of scholarly citations and a Bible reference, and every reply, about half that length, cites a source of its own.

You post and submit every item, and the tests and blog are yours.

MGMT 625 work goes to a scheduler or project manager who builds baselines for a living, often holding the PMP or PMI's scheduling credential.

That experience shows in the WBS, where deliverables are nouns, work packages are sized so one team can own them and the numbering stays clean across levels.

It shows in the plan too. The change management section sets who can approve a change and how its effect on the schedule is assessed, and the communication plan names which reports go to which stakeholders and how often.

Discussion threads draw on real scheduling problems, such as why a schedule with no float on its last month is a warning sign, or how a dependency missed in planning surfaced as a delay months later.

Before either reaches you, a colleague lays the breakdown beside the plan to confirm they agree, and the same scheduler stays with you all term.

If the plan is ordered here but you build the WBS yourself, the plan's scope list is written so it can be lifted straight into the breakdown.

The plan is the first difficulty. Eight sections in eight to ten pages, all specific to one project, is a substantial professional document for week four.

Alignment is the second. The WBS in week six must follow from the plan's scope, and gaps between the two are easy for graders to spot.

WBS quality is the third. Students often list activities instead of deliverables, or break some branches down to tiny tasks while leaving others at a high level.

The tests are the fourth, three of them at 75 points, in weeks three, five and eight.

The discussions are the fifth, each needing scholarly sources and Scripture in the thread and a scholarly source in every reply.

Tests ask for precise terms such as lag, lead, free float and total float.

Choosing the project in week one keeps the plan and the WBS on track, so the course is easiest to hand over early.

Discussion threads arrive at the start of weeks one, three, five and seven, and replies once classmates post in the following weeks.

The plan arrives before week four closes, and the WBS before week six closes.

The quote lists each discussion, the plan and the WBS separately, with the plan the largest.

A student joining after week four sends the graded plan, and the WBS is built from it.

Payment follows each piece on delivery.