As the train neared completion, the GTA threw a party. The tunnel was dug. The tracks were laid. But Mira wasn't celebrating the steel. She was celebrating a quiet folder on the server: the Lessons Learned Register (Section 4.4.1).
Next came . The existing Gantt chart was a lie. Mira introduced the concept of the critical path using a new feature in the 6th Edition: the emphasis on agile iterative scheduling. She didn't force pure waterfall. Instead, she used the guide’s newly harmonized approach—creating a hybrid model where the tunnel boring was predictive, but the software integration for the signaling system was agile, with two-week sprints and a refined backlog. Pmbok 6th Edition.pdf
Harold went pale. That would cost a month and ten million dollars to mitigate. Mira didn't flinch. She opened in the PDF. “Probability of 0.3, Impact of 0.8. Priority score: 0.24—High. We escalate this to the steering committee now .” As the train neared completion, the GTA threw a party
Three weeks later, that “minor” realignment conflicted with a newly installed electrical substation. Because the change wasn’t logged or assessed for dependencies (using the PMBOK® ’s emphasis on traceability), it caused a cascade of rework. The project lost two weeks and $800,000. But Mira wasn't celebrating the steel
Silence. Then, a junior geologist raised a hand. “The soil three kilometers east of the river… the samples are inconsistent. There’s a 30% chance of a methane pocket.”
“You don’t manage iron and concrete,” she told the chief engineer, a man named Harold who trusted torque wrenches more than people. “You manage interest .”