How to keep history of the scrum mettings?
Hi,
It is there a way to allow scrum team members to allow them to fill scrum meeting information? - What did you do yesterday? - What are you going to do today? - Do you have blockers in your tasks? This to keep a history of the daily scrum meetings and allow scrum master to check previous scrum meetings and allow team members that can not attend scrum meeting to fill this information. Thanks for any help. |
Accepted answer
sébastien etter (216●8●7)
| answered Sep 10 '08, 3:12 a.m.
edited Mar 15 '19, 3:18 a.m. by Ralph Schoon (63.6k●3●36●46) I wrote a detailed article about a Meeting Work Item Type. Not Scrum oriented but it could be easily adapt .
Ralph Schoon selected this answer as the correct answer
|
7 other answers
Is there a plugin to add this functionallity?
|
We have a team here have a best practice to record down the answers to the 3 questions before the stand-up daily scrum meeting:
- What did you do yesterday? - What will you do today? - Is anything in your way? They created a small web application to record down every team members' answers to the above three questions. It's also a commitment from every team member. The historic records help everybody keep his/her commitment as well as follow up. I hope Jazz provide this Daily Scrum meeting record as a build-in function. |
marcosal wrote:
Hi, To keep a history of the scrum meetings, you could use additional attached pages of the corresponding iteration plan. It is meant to capture unstructured information. For instance, the Jazz-PMC uses additional pages to write down planning notes (https://jazz.net/jazz/web/projects/Jazz%20Project#action=com.ibm.team.apt.viewPlan&page=wikiPage_PlanningCallNotes&id=_DO2HgEHxEd277OW8h_kVIQ). -- Cheers, Johannes Agile Planning Team |
zrlrke,
Yes it's a good way to record down Daily Scrum meeting minutes in the added page "Daily Scrum". Thanks! Chunyi |
We use a minutes work item type (easy to create) to capture daily scrum
minutes and other meeting minutes. The iteration plan can point to these minutes work items. This may be a good candidate for a blog entry or tech note. |
The document is excellent. Thanks for that.
Do you have idea, how can we create similar work item named Defect (not the one which is by default available) with custom attributes like, root cause, associated to task id, test case info etc? Or any other way to track this information? Comments
Richard Knaster
commented Oct 12 '12, 9:16 a.m.
Hi Virendrasingh:
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.