Date: Tue, 19 Mar 2024 13:27:14 +0000 (UTC) Message-ID: <680051001.2193.1710854834989@docs.stiltsoft.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2192_1859536252.1710854834989" ------=_Part_2192_1859536252.1710854834989 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Project Performance Dashboard is a tool which can give you valuable insi= ghts into how your project evolves and how your team performs.
The app automatically calculates the reporting data for your software pr= ojects and generates the following charts:
Chart | What it shows |
---|---|
|
Sprint Structure per Issue TypeThi= s chart type shows the distribution of issue types across last eight sprint= s. This way you can track the scope of your sprints and identify whether yo= u create new functionality or address issues and refactor code from older s= prints. Normally, each sprint should contain at least 50-60%% of stor= ies and new features, 20% of bugs or less, 15% for improvements. If there&n= bsp; |
|
Story ThroughputThis chart is similar to= Sprint Velocity and helps you to count the number of stories finished in a= sprint. Within this metric, stories should be included into the sprint the= y were completed, not started in. Story Throughput= is a highly useful metric. If all your stories are similar in size, you ca= n use ST instead of Velocity. If your stories have a normal distribution (o= ne part of your stories has a specific average size, and the other part goe= s below and above that average), you can also use ST instead of Sprint Burn= down and Sprint Burnup. |