Dummy Project
HEOR-GLP1-88
Analytic definition changes become scope and budget pressure.
Project Story
What readers should notice
HEOR-GLP1-88 is written as a case a working PM can recognize, not as a sterile protocol summary. The project sits in HEOR/RWE as a Database study study, but the real teaching point is this: a database study can still behave like a pressured project when analytic definitions, payer questions, scope changes, and budget assumptions keep moving. When readers compare HEOR-GLP1-88 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.