blob: cc58407126e63bbbaac599fc543b1b2806fca33a [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0"
xmlns:xmi="" xmlns:org.eclipse.epf.uma=""
xmlns:epf="" epf:version="1.5.0" xmi:id="-5ZwUAb_042ViuoKsGdsWmw"
name="new_term_definition,_YCtMUF5eEd22Gu98eFOlrQ" guid="-5ZwUAb_042ViuoKsGdsWmw"
On a Scrum project, the team tracks its progress against a release plan by updating a release burndown chart at the end&#xD;
of each sprint. The horizontal axis of the release burndown chart shows the sprints; the vertical axis shows the amount&#xD;
of work remaining at the start of each sprint.&#xD;
The scope of this chart is a single release; however, a product burndown chart spans all releases.&#xD;