Take My Liberty MGMT 690 Class

The Create text carries the case. Red Zuma is planned in the early weeks, then progress is entered and examined, and the case closes with analysis and reporting of the kind a sponsor would receive.

Jarocki's book is read over the first five weeks. It argues that many projects hit their deliverables yet miss their purpose because nobody planned for the people who must work differently afterward, so the two disciplines should be run as one.

Group discussion prompts follow the readings: why outputs do not always become outcomes, how scope slips, why estimates run optimistic, and what a capstone teaches a project leader.

Week five completes Jarocki, and the review is due. Weeks six and seven center on the PMO proposal, supported by a presentation and website on how such offices work. Week eight finishes the Create text with a last discussion.

Group threads fall in weeks one, three, five and eight, and replies to teammates follow in weeks two, four, six and eight. The industry for the proposal is picked in week two.

Because the course is the program's last, many instructors expect the polish of a professional report in every piece.

The first half of MGMT 690 belongs to Red Zuma and Jarocki; the second half belongs to the proposal; the group conversation runs throughout.

Red Zuma is worked strictly to the case instructions. The schedule is built with linked tasks, a working calendar and named resources, a baseline is saved before any progress is entered, and later parts compare actual work with that baseline and report what the gap means.

The book review spends little space on summary. Most of it weighs whether one combined method suits every project, whether it would overload a small team, how it sits with the PMBOK and newer practice, and how a Christian view of caring for affected people shapes the judgment.

The proposal picks an industry whose projects visibly struggle, for example county court systems moving to electronic filing or university research offices managing grant-funded builds, and argues for an office of the right type, with its services, staff and rollout.

Group posts take a position backed by journal research and Scripture, and replies to teammates bring something new. You post and submit everything yourself.

Students who completed earlier program courses with Microsoft Project will recognize the tools, but Red Zuma asks for them all at once, from task setup to cost reporting.

Capstone orders go to a seasoned project or program manager who has helped stand up, or worked inside, a project management office.

That background shapes the proposal. Offices that mostly coach and supply templates suit loosely run industries; offices that enforce standards suit regulated ones; offices that run projects directly suit firms where projects are the business. The proposal picks one and defends it.

It shapes the case files as well, where schedules use dependency logic instead of typed-in dates, and resource loading is checked before the baseline is set.

It also informs the review, since a writer who has watched a finished system go unused can test Jarocki's claim against real experience.

A colleague opens every schedule file to confirm it calculates, and reads each paper before you see it; one writer stays with your capstone throughout.

The proposal's industry research usually mixes trade reports, government data and journal studies, so the case for an office rests on evidence rather than opinion.

Your group discussion posts carry the same practitioner tone, drawing on real projects with names and details changed.

Software comes first. Many students last used Microsoft Project a year or more earlier, and calendars, links and resource settings eat hours.

Timing comes next, since two case parts and the first teammate replies all land in week two.

The proposal is the largest paper of the degree, with a long reference list and a faith perspective expected in several sections.

The review must argue rather than retell, which is harder than summarizing a book.

Group posts, with journal sources and Scripture every time, keep going through the whole term.

Students who have never seen a project management office in action also find it hard to describe what one would actually do day to day.

Because a group thread opens the course and two case parts follow a week later, arranging help before week one is easiest.

Case files arrive before the ends of weeks two, three and four, each with its schedule and its written answers.

The review arrives before week five ends, the proposal before week seven ends.

Group posts land at the start of their weeks, and teammate replies once others have posted.

The proposal and the case cost the most on the quote, then the review, then the discussions.

Students who join after the case is under way can send the parts already submitted, and the rest is built on them.