Artifact: Burnup vs Burndown Recommendation

Aurora Checkout Redesign -- chart recommendation -- exercises co-09, co-11.

To: Aurora stakeholder group From: Aurora PM

Switch the shared status chart from burndown to burnup for the remainder of the project.

A burndown chart plots only remaining work: if a scope change is accepted mid-project, remaining work jumps back up, and on a burndown chart that jump is visually indistinguishable from the team simply falling behind. A burnup chart plots two separate lines -- completed work and total scope. An accepted scope change shows up as an explicit step on the total-scope line, separate from the completed-work line, so a stakeholder can see "scope grew" without it looking like "the team got slower."

This matters now specifically because a scope-change request (the Google Pay addition) is under active discussion.