Nine weeks of drafting, each task tagged by whether it waits on someone else, plus a written rule for absorbing a missed week: that is the second MGMT 8910M deliverable. Searches like "mgmt 8910m week 2 assignment example", "mgmt8910m week 2 sample" and "mgmt 8910m week 2 example" land here.
What a finished MGMT 8910M Week 2 writing plan looks like
Two to three pages: a schedule table, a dependency note and the missed-week rule. The table runs from Week 3 to Week 11, one row per week, with columns for the task, its expected output in pages, and a flag marking whether it can proceed without anyone else. Literature review subsections on schedule flexibility, on turnover intention and on the history of utility call-center staffing carry the unflagged rows. Two rows are flagged as waiting: committee comments on the prospectus and permission to survey agents at a partner utility. Page targets are set from the author's actual pace over the past month, stated in the plan, rather than from a hoped-for rate. The rule follows the table as two if-then sentences, and a buffer week sits at Week 9 with nothing assigned to it.
How a MGMT 8910M Week 2 example is structured
The plan is ordered by dependency before it is ordered by date. Tasks that wait on other people are placed first in the reasoning and scheduled so their waiting overlaps with work the author controls, which is why the prospectus goes to the committee in Week 3 and the review subsections fill the weeks while comments are pending. The table then presents everything by week. The missed-week rule comes next, written as implementation intentions in Gollwitzer's sense, a named situation linked in advance to a response: if a week produces nothing, its task moves to the buffer week rather than doubling the next one; if the buffer is already spent, the lowest-priority subsection drops to the following term, and the plan says which one that is. A closing paragraph states the one assumption the whole schedule depends on.
Waiting tasks placed first
Committee comments and site permission cannot be hurried, so the plan starts them early and schedules controllable work over the gap. A schedule that places the waiting items late turns every delay by someone else into a delay of the whole document.
Targets from observed pace
Page targets come from what the author produced over the past month, and the plan states that figure. Estimates built on intended pace fail in a familiar direction, since people planning their own work routinely underestimate how long it will take.
The missed-week rule as if-then
Two conditional sentences decide in advance what happens to a lost week. The displaced task moves to the buffer, never onto the following week, because a doubled week is the one most likely to be missed next.
A buffer with nothing in it
Week 9 carries no assignment. An empty week looks wasteful on paper, but a plan without one has already spent its slack before the first missed week arrives, and the rule then has nowhere to send the work.
What gets dropped, named now
If the buffer is used and another week is lost, the subsection on the history of call-center staffing moves to the next term. Naming the casualty in advance keeps the decision from being made in a panic, and in favor of whatever feels easiest.
Where marks go in MGMT 8910M Week 2
Graders test the plan against a bad week before they read it for a good one. A schedule that assumes every week delivers, with no rule for a miss, has planned the easy case only, and that is where most submissions lose ground. Credit rises for the dependency ordering: placing committee review and site permission early, with controllable work over the wait, demonstrates a grasp of which parts of the timeline belong to the author. Targets are compared with the stated pace, and a plan promising twice the observed output reads as aspiration. The if-then rule is judged on specificity, since doubling next week is not a rule at all. Naming the subsection that would be dropped earns distinct credit, because it proves the priorities were set before pressure could set them.
Get a MGMT 8910M Week 2 example written to your instructions
Attach the Week 2 prompt and rubric and describe the chapters in front of you, plus anything that depends on someone else's approval. A dated plan with its dependency note and missed-week rule returns in 24-48h, free as a first sample. Its study is made up, so the weeks on your own calendar are still yours to fill.
MGMT 8910M Week 2 questions, answered
How detailed should a dissertation writing plan be?
Detailed enough that a missed week has a visible consequence. Weekly rows with a named task and an expected output are usually right; daily schedules tend to collapse on first contact with a real week, and monthly ones hide slippage until it is large. The dependency flags matter more than the granularity, because they show which delays the author can absorb.
Why not just make up a missed week the following week?
Because the following week already has its own task, and doubling it creates the week likeliest to fail next. One missed week becomes two, then a backlog. Moving the displaced task into a reserved buffer keeps every other week at its planned size. When the buffer is gone, dropping a named low-priority piece is more honest than pretending to double.
Should the plan include time for committee review?
Yes, as a dependency rather than as the author's task. Review windows vary by committee and by term, so the plan states an assumed turnaround and flags it. What the plan controls is the work scheduled around the wait. A plan that leaves the author idle while comments are pending has scheduled the least productive weeks of the term.