Thoughts on using RTM for Scrum development
earok says:
Hi all,
I am starting to use RTM as a minimalist scrum development tool. See http://en.wikipedia.org/wiki/Scrum_(development)
This is the methodology I am currently using, but definitely very keen to get feedback on improvements.
The set up is that the Project leader has these lists in his or her own RTM account:
- Backlog, a regular list that just contains the tasks not currently being worked on.
- Task Lists, a regular list for each collaborator that contains the tasks being worked on during the current sprint, and this is shared with the collaborator's RTM account.
- Sprint, a smart list that is a view of all of the Task Lists. For instance, list:"Tom" or list:"Harry"
At the start of each sprint, any remaining tasks from the previous sprint are moved back into the backlog (Just by selecting all in the Sprint list, move to Backlog). The team then decides on any adjustments to priorities, estimated times etc, before picking tasks for the new sprint and moving them to each of the appropriate user's task lists.
A burn down chart can also be managed by making note of the estimated time on the Sprint and Backlog lists daily.
I am starting to use RTM as a minimalist scrum development tool. See http://en.wikipedia.org/wiki/Scrum_(development)
This is the methodology I am currently using, but definitely very keen to get feedback on improvements.
The set up is that the Project leader has these lists in his or her own RTM account:
- Backlog, a regular list that just contains the tasks not currently being worked on.
- Task Lists, a regular list for each collaborator that contains the tasks being worked on during the current sprint, and this is shared with the collaborator's RTM account.
- Sprint, a smart list that is a view of all of the Task Lists. For instance, list:"Tom" or list:"Harry"
At the start of each sprint, any remaining tasks from the previous sprint are moved back into the backlog (Just by selecting all in the Sprint list, move to Backlog). The team then decides on any adjustments to priorities, estimated times etc, before picking tasks for the new sprint and moving them to each of the appropriate user's task lists.
A burn down chart can also be managed by making note of the estimated time on the Sprint and Backlog lists daily.
(closed account) says:
Hi earok,
I have been a professional project manager for over 14 years. I have both the PMP and CSM certifications. I am just wondering why you would be trying to use a tool like RTM to manage a scrum project. There are many tools available at no to little cost that are specifically designed to manage scrum projects. They specifically help you track items in a sprint, the backlog, story points, burn down charts, burn up charts, etc.
I am a big fan of RTM, but as a professional project manager, RTM is not the appropriate tool to help you successfully lead or manage a project. Below is a link that will give you some ideas about the free tools that are available to manage scrum projects. I hope this information is helpful.
http://open-tube.com/10-free-scrum-project-management-tool/
Amie
I have been a professional project manager for over 14 years. I have both the PMP and CSM certifications. I am just wondering why you would be trying to use a tool like RTM to manage a scrum project. There are many tools available at no to little cost that are specifically designed to manage scrum projects. They specifically help you track items in a sprint, the backlog, story points, burn down charts, burn up charts, etc.
I am a big fan of RTM, but as a professional project manager, RTM is not the appropriate tool to help you successfully lead or manage a project. Below is a link that will give you some ideas about the free tools that are available to manage scrum projects. I hope this information is helpful.
http://open-tube.com/10-free-scrum-project-management-tool/
Amie
Log in
to post a reply.