Project Story
What readers should notice
GI-520 is written as a case a working PM can recognize, not as a sterile protocol summary. The project sits in Gastrointestinal as a Pilot study, but the real teaching point is this: a pilot can either answer a modest question well or sprawl into a rescue project that no longer knows what it is trying to learn. When readers compare GI-520 with their own project, they should look for the same pressure points: what the protocol assumes, what sites can actually do, what vendors must prove, what data must remain credible, what safety or ethics concern could change the plan, and what Daniel Liang's team would ask before accepting a green dashboard as truth.
Lifecycle Coverage
Book Mentions
How to read this case
Look for the moment when ordinary project language stops being enough: a date slips, an assumption fails, a vendor signal loses meaning, or a clinical concern changes the work. Then follow the chapter links, toolkit examples, glossary terms, and packet artifacts to compare this fictional pressure pattern with a real project you manage.