LAMOverse Waits While the Core Work Takes Priority
After the hiring freeze, adding staff could no longer resolve the pressure of pushing two lines of work at once. The team postponed LAMOverse indefinitely and put the core work first. The decision gave limited staff a clear priority, while moving LAMOverse from an imminent delivery to an unscheduled task.
A creative chronicle combining project history with imagined scenes. Story events are not verification of network activity.
After the hiring freeze, adding staff could no longer resolve the pressure of pushing two lines of work at once. LAMOverse had also been moving toward completion. The people setting schedules now had to choose between it and the core work already under maintenance.
The team postponed LAMOverse indefinitely and put the core work first. Some did not want work already done on it to lose its place; others pointed out that problems arising during the public beta needed attention every day. The meeting ended without a new completion date. Each group would first list what the core work required, then identify which LAMOverse tasks could be set aside for now.
The decision gave limited staff a clear priority, while moving LAMOverse from an imminent delivery to an unscheduled task. People who had expected it to follow the earlier timetable had to rearrange their work. How to maintain the set-aside parts, and when work on them could resume, remained unanswered.