We are using Scrum for more than a year now for a mobile game project. We use a printed Excel sheet pinned on cork board almost similar to one here on mountaingoatsoftware website. During the sprint we need to take customer approval mostly for design to mark that task as done.

We put a question mark in the progress cell when task owner finishes the task, to remind us that it is pending for approval (it works same as zero on burndown chart except that we know that work is not approved yet), if work is approved we put zero, otherwise if customer needs some changes then designer has to incorporate those changes but we are facing a unique problem that we are unable to find a solution online.

The whole team is collocated except the product owner who gives feedback via email or chat. Now consider the following senario and help me solve the problem:

1. on Day-4 We have conducted today's daily scrum, a task owner marked task-A as pending for approval by putting a question mark (i.e. he has consumed estimated hours and finished work from his end)

2. Scrum Master has taken notes from the sheet and generated Daily Burndown chart and disseminated reports to stakeholders

3. During the day the customer reviews the completed task and ask for some changes via email/chat

4. the task owner spends a few hours and completes those changes and send for review again

5. on Day-5 daily stand up meeting the task owner inform the team about the work done

My question is

a) how do we report it on the sprint backlog? if we put a question mark on Day-5 then we will miss the hours spent on the burndown chart

b) should we put hours spent on Day-5 progress? but then work is in approval not in progress

c) should we add another task, record time spent in actual estimate column and question mark on the Day-5 progress cell? but then task-A remains incomplete. it also doesn't sound feasible as it happens to many tasks, and the approval cycle happens several times until task is finally approved.

d) this additional work/changes certainly shorten the time for other stories pending, therefore how do we deal with this situation.

We are using Scrum for more than a year now for a mobile game project. We use a printed Excel sheet pinned on cork board almost similar to one here on mountaingoatsoftware website. During the sprint we need to take customer approval mostly for design to mark that task as done.

We put a question mark in the progress cell when task owner finishes the task, to remind us that it is pending for approval (it works same as zero on burndown chart except that we know that work is not approved yet), if work is approved we put zero, otherwise if customer needs some changes then designer has to incorporate those changes but we are facing a unique problem that we are unable to find a solution online.

The whole team is collocated except the product owner who gives feedback via email or chat. Now consider the following senario and help me solve the problem:

1. On Day-4 we have conducted the daily scrum, a task owner marked task-A as pending for approval by putting a question mark (i.e. he has consumed estimated hours and finished work from his end)

2. Scrum Master has taken notes from the sheet and generated Daily Burndown chart and disseminated reports to stakeholders

3. During the day the customer reviews the completed task and ask for some changes via email/chat

4. the task owner spends a few hours and completes those changes and send for review again

5. on Day-5 daily stand up meeting the task owner inform the team about the work done

My questions are:

• How do we report it on the sprint backlog? if we put a question mark on Day-5 then we will miss the hours spent on the burndown chart

• Should we put hours spent on Day-5 progress? but then work is in approval not in progress

• Should we add another task, record time spent in actual estimate column and question mark on the Day-5 progress cell? but then task-A remains incomplete. it also doesn't sound feasible as it happens to many tasks, and the approval cycle happens several times until task is finally approved.

• This additional work/changes certainly shorten the time for other stories pending, therefore how do we deal with this situation.

we are using Scrum for more than a year now for a mobile game project. we use a printed excel sheet pinned on cork board almost similar to one here on mountaingoatsoftware website. during the sprint we need to take customer approval mostly for design to mark that task as done. we put a question mark in the progress cell when task owner finishes the task, to remind us that it is pending for approval (it works same as zero on burndown chart except that we know that work is not approved yet), if work is approved we put zero, otherwise if customer needs some changes then designer has to incorporate those changes but we are facing a unique problem that we are unable to find a solution online. the whole team is collocated except the product owner who gives feedback via email or chat. now consider the following senario and help me solve the problem

1. on Day-4 We have conducted today's daily scrum, a task owner marked task-A as pending for approval by putting a question mark (i.e. he has consumed estimated hours and finished work from his end)

2. Scrum Master has taken notes from the sheet and generated Daily Burndown chart and disseminated reports to stakeholders

3. During the day the customer reviews the completed task and ask for some changes via email/chat

4. the task owner spends a few hours and completes those changes and send for review again

5. on Day-5 daily stand up meeting the task owner inform the team about the work done

now my question is

a) how do we report it on the sprint backlog? if we put a question mark on Day-5 then we will miss the hours spent on the burndown chart

b) should we put hours spent on Day-5 progress? but then work is in approval not in progress

c) should we add another task, record time spent in actual estimate column and question mark on the Day-5 progress cell? but then task-A remains incomplete. it also doesn't sound feasible as it happens to many tasks, and the approval cycle happens several times until task is finally approved.

d) this additional work/changes certainly shorten the time for other stories pending, therefore how do we deal with this situation.

We are using Scrum for more than a year now for a mobile game project. We use a printed Excel sheet pinned on cork board almost similar to one here on mountaingoatsoftware website. During the sprint we need to take customer approval mostly for design to mark that task as done.

We put a question mark in the progress cell when task owner finishes the task, to remind us that it is pending for approval (it works same as zero on burndown chart except that we know that work is not approved yet), if work is approved we put zero, otherwise if customer needs some changes then designer has to incorporate those changes but we are facing a unique problem that we are unable to find a solution online.

The whole team is collocated except the product owner who gives feedback via email or chat. Now consider the following senario and help me solve the problem:

1. on Day-4 We have conducted today's daily scrum, a task owner marked task-A as pending for approval by putting a question mark (i.e. he has consumed estimated hours and finished work from his end)

2. Scrum Master has taken notes from the sheet and generated Daily Burndown chart and disseminated reports to stakeholders

3. During the day the customer reviews the completed task and ask for some changes via email/chat

4. the task owner spends a few hours and completes those changes and send for review again

5. on Day-5 daily stand up meeting the task owner inform the team about the work done

My question is

a) how do we report it on the sprint backlog? if we put a question mark on Day-5 then we will miss the hours spent on the burndown chart

b) should we put hours spent on Day-5 progress? but then work is in approval not in progress

c) should we add another task, record time spent in actual estimate column and question mark on the Day-5 progress cell? but then task-A remains incomplete. it also doesn't sound feasible as it happens to many tasks, and the approval cycle happens several times until task is finally approved.

d) this additional work/changes certainly shorten the time for other stories pending, therefore how do we deal with this situation.