vabozed

• Jul 22nd, 2015

 

I include any details that the stakeholder wants to track.
I recently included % completed, what kind of bugs were found (department), number found and status of bugs logged, number of testing hours.

it really just depends on the type of testing and the focus of the results desired.
I included a running summary of the bugs, logged by department, severity (critical, important, low, resolved, unable to reproduce, closed)
I also included as much as I was able the number of testing hours spend that day as we had multiple resources in different departments executing testing.

Depending upon who the report is for, it might be as simple as % completed and an update as to present vs expected completion status.

devang

• Oct 18th, 2015

 

1. What did you do today?
2. What is your planning for tomorrow?
3. Is there any issue you faced today, How you did resolve or still it is open?
4. Do You need any input, from whom you need and what are they?

Nandini

• Nov 9th, 2015

 

1.What we did today?
2.What we will do tomorrow?
3.What obstacles are in our way?
This meeting ajanda is knowing problems but not solving problems

Vikas Salaria

• Jan 21st, 2016

 

In Daily status report we share the progress/work that we have done on the present date. It is made in an excel sheet and comprises of:
1.Date
2.Resource Name.
3.Reporting Manager.
4.Different color annotation for Work completed,yet to start and pending.
5.Tasks column is there.
6.Tasks completion percentage column.
7.Effort Estimated.
8.Remaining percentage.
9.Comments.

manikandan

• May 20th, 2016

 

Simply say scrum meeting called daily stand up meeting.