Mango

A solar panel installer's team has built an optimistic project estimate based on how fast they believe this project will go. Comparable Public Edition implementations at similar companies have consistently taken considerably longer than the team's estimate assumes. The project manager must produce a credible plan, weighing the team's inside-view optimism against the consistent track record of similar projects. He must decide how to set the estimate. How should the project manager set the estimate?. Use the team's optimistic estimate, since they know this project best. Average the team's estimate with a small buffer. Anchor the estimate on how comparable projects have actually gone. Ask the team to re-estimate more carefully.

A Turkish building-materials group is at its cut-over readiness gate for a public cloud go-live. Two workstreams present conflicting readiness signals from the lifecycle management tool. The warehouse workstream reports that all of its UAT test cases passed, but the project manager notices those cases were executed against sample data the testers keyed in by hand rather than the migrated data set. The finance workstream reports several open UAT failures, but those were run against the actual migrated data. The commercial director, pushing to protect the launch date, argues the go decision should follow the workstream showing green and treat the finance failures as overly cautious. The project manager understands that a pass produced on hand-made sample data gives weaker readiness assurance than a failure produced on real migrated data, because the sample-data pass may not reflect how the system behaves on the data the business will actually run. Her recommendation will drive whether the group goes live. She must decide how to weigh these two signals. How should the project manager weigh the two conflicting readiness signals in her recommendation?. Treat the warehouse passes and finance failures as equally weighted evidence, and recommend go only once the two workstreams report the same status. Give more weight to the finance failures on migrated data and flag the warehouse passes as needing re-execution on the migrated set before a go decision. Follow the warehouse workstream's all-pass result and recommend go, treating the finance failures on migrated data as the more pessimistic of the two signals. Average the two workstreams into a single overall readiness score and recommend go or no-go based on whether that combined figure clears the agreed bar.

Midway through a hotel-supply distributor's project, a genuinely valuable new capability is proposed that the team is excited about. Adding it now, however, would pull effort from the committed scope and put the agreed go-live at risk. The capability is good, but it was not planned. The project manager must protect the committed scope and date without dismissing a real opportunity, recognizing that even good ideas carry an opportunity cost against what is already promised. He must decide how to handle the proposal. How should the project manager handle the proposal?. Pause to redesign the plan around the new capability. Swap it in by dropping a committed item of similar size. Log it for a later phase to protect the committed scope. Add it to the current scope because it is clearly valuable.

Midway through a mining company's Public Edition project, the project manager learns that a critical legacy dataset will not be ready in time for the planned migration, putting the timeline at risk. A status report is due to the steering committee, and there is pressure to keep reporting the project as on track. She must handle a risk that is real but politically inconvenient, knowing project governance depends on surfacing risks early rather than hiding them. She must decide how to handle it. How should the project manager handle the data-readiness risk?. Report the project as on track and hope the dataset is ready in time. Pause the whole project until the dataset is completely ready. Quietly extend the team's hours to absorb the slip without telling the committee. Raise the risk to the steering committee with options and a replanned path.