Escalation team added Bi-Weekly Performance Reviews in their Escalation Cycle about a year ago to track the amount of work the team is doing in each cycle (Each Escalation Cycle is 2 weeks long). We started off with an experiment to add transparency to our work. The successful experiment resulted in the measurement of the work we deliver in each cycle. The need of these Performance blogs was to statistically highlight the nature of work we do during a month (i.e. the total of 4 weeks and a set of 2 Escalation cycles) to effectively do a comparison and analysis with Mavericks Dashboard. Performance Blogs will be an extension to the Performance Reviews in which we will answer questions like "Why the number of resolved issues gone down in a month?".
Performance Blogs will take input from Mavericks Dashboard and provide a reference to the basic questions which may raise observing the graphs. Additionally, we will also document what were the heat points of the platform during the month and track the kind of incoming issues.
| Page Properties Report |
|---|
pageSize | 12|| Iframe |
|---|
| src | https://docs.google.com/spreadsheets/d/e/2PACX-1vS-xT9vTwv4BZoRLtbPnPA8nkUBbE-TWCfx9aYW2rwRRS5lSsnVWy6wasfQp4IR9YB_E8TCVoBNYRXj/pubchart?oid=507691982&format=interactive |
|---|
| width | 800 |
|---|
| frameborder | show |
|---|
| title | Escalation Review |
|---|
| align | middle |
|---|
| height | 600 |
|---|
|
>> SOURCE <<
| Page Properties Report |
|---|
| pageSize | 12 |
|---|
| headings | Triaged Issues, Closed w/o Fix, Fixed, Stories / Tasks % |
|---|
| sortBy | Date DESC |
|---|
| cql | label = "performance-blog" and space = currentSpace ( ) and ancestor = currentContent ( ) |
|---|
|
| Child pages (Children Display) |
|---|
|