How to keep history of the scrum mettings?
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
I wrote a detailed article about a Meeting Work Item Type. Not Scrum oriented but it could be easily adapt .
Have a look on work item 58272 (Word Document attached): 58752: Article "Work Items customization : Meeting type example"
7 other answers
- 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.
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.
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
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
Hi Virendrasingh:
Yes you can. Your choices are:
1. Modify the existing Defect work item (recommended)
2. Create a new work item and delete the old one
The following article on Jazz.net will help you customize the work item.
Below is an example Defect with the fields you mention. You can now easily do the customizations in the web client. There may be a few things that you will need to use the eclipse client, but the majority of heavy lifting can be done in the web.
Customizing work items: https://jazz.net/library/article/565/
