Do My Liberty MGMT 620 Course for Me

Week one opens the Create reading with the checklist, introductions and the first 50-point quiz.

Week two keeps reading and brings the first 100-point discussion.

Week three reaches the measurement chapter, and the first application exercise is due.

Week four stays on measurement, with the second discussion and the second exercise.

Week five finishes the Create reading with the third discussion.

Week six switches to Thomas's second and third chapters, and the 200-point research paper is due.

Week seven reads four more Thomas chapters and has the second quiz.

Week eight reads the final Thomas chapters, with the 150-point training deck and the last quiz.

Quizzes fall in weeks one, seven and eight, so the middle weeks are given to writing and calculation.

The switch to Thomas in week six brings a different voice, focused on practice rather than measurement.

Thomas's chapters are read out of order in week seven.

The exercises begin with the status data each question supplies. It is laid out in a Word table by reporting period, so the grader can see where every figure comes from.

Calculations follow a fixed order, variances, then indices, then forecasts, each shown as formula, figures and result. A cost index of 0.88, for instance, is explained as the project earning eighty-eight cents of planned work for every dollar spent.

Status questions are answered the way a controls lead would brief a steering committee: what has happened, what it means for the finish date and budget, and what corrective action is proposed.

For the paper, the search covers project and evaluation journals and documented cases, such as an inspector general's review of a federal IT program or a published post-mortem of a construction overrun.

The paper then arranges current practice into a few clear principles and tests each case against them, ending with what a project office should change.

The deck is built as a session a PMO could run: why lessons are lost, a short template for capturing one, a practice round with a sample incident, a place to store lessons so teams can find them, and a step that writes them into the next plan.

Discussion answers draw on the week's chapter, journal research, a course text and Scripture; replies take up a classmate's point with something new.

Where an exercise asks which assumption fits, the answer weighs whether the causes of past overruns are likely to continue.

Each case in the paper is introduced with its goal, budget and outcome before the evaluation itself is discussed.

The deck's practice round uses a sample incident, such as a vendor delivering late twice on similar projects, and asks teams to turn it into a planning rule.

Each discussion reply quotes the classmate's main point briefly and then responds to it.

Every journal entry in the paper's reference list carries its DOI where one exists.

Biblical points in each answer support the argument, such as stewardship of resources in a thread on cost control.

The work is done by someone who runs project controls or a PMO: building baselines, reporting variances and leading close-out reviews.

They have seen forecasts go wrong because the wrong formula was used, which is why each exercise explains the choice of method.

They have also facilitated lessons-learned sessions that changed later projects and some that did not, which shapes the deck's practical design.

Their research for the paper draws on audit reports and journals rather than general web articles.

A colleague recomputes every figure, and one writer stays with the course from start to finish.

Several have trained project managers in earned value, so the explanations are written for someone learning the method.

They are comfortable bringing Scripture into a professional argument without forcing it.

Their own lessons-learned registers inform the template in the deck.

They write status explanations in the plain language sponsors prefer.

One writer handles the full term.

The first application exercise arrives in week three, before most students have used earned value even once.

Forecast questions often leave the assumption implicit, and picking the wrong one gives a precise-looking but wrong estimate.

Documented evaluation cases are harder to find than success stories, which slows the paper.

A twenty-slide deck needs a design, not just content, and the one-page summary must still fit everything on a page.

Weeks four and eight each combine two graded items, and week eight adds the final quiz.

Students also find it hard to find five peer-reviewed sources specifically on project evaluation rather than on project management in general.

The deck's speaker notes take as long to write as the slides, since they carry the substance.

Earned value questions on the quizzes reward students who studied the exercise solutions.

Stakeholder questions ask whose view of success counts, which has no formula and needs careful argument.

The training's summary must fit on one page, which forces hard choices.

Week five's discussion ends the Create reading.

Discussion answers come at the start of weeks two, four and five; replies follow once classmates post.

Each exercise arrives a few days before its week ends, the paper before week six closes and the deck before week eight closes.

The paper and the deck carry the highest prices, then the exercises, then the discussions.

Booking everything at the start of the term costs less overall; students who join later pay only for what is still due.

You pay for each piece as it arrives.

The coordinator confirms each date against your sub-term calendar.

Single exercises or discussions can be booked for any week.

Late starters send what is already graded.