Loading Profile...
Twitter,
Facebook, or email.
EMPLOYEE
Can I copy & and paste tasks in ScrumWorks Pro?
Official
Response
-
Yes:
1. Select the tasks you wish to copy,
2. Right click and select copy or press CTRL C
3. Right click the target backlog item,
4. Select Paste or press CTRL V
-
Yes:
1. Select the tasks you wish to copy,
2. Right click and select copy or press CTRL C
3. Right click the target backlog item,
4. Select Paste or press CTRL VComment -
-
What is actually preferred way with ScrumWorks to move not finished user stories / tasks from ended sprint to new one?
1) Just dragging them from ended sprint to new one?
- will then ended sprint's data be wrong? E.g. later when checking ended sprints velocity it doesn't contain anymore task / user story that was worked during the sprint, not finished, and finally dragged to new sprint for continuing the work
2) Copy-paste tasks / user stories?-
Currently option 1), or with the slight detour of moving the PBI back into the backlog before deciding to move it into the next sprint during that planning meeting is the suggested course of action.
Option 2) is possible, and I have seen it used, the key thing to remember about it is to duplicate the PBI Estimate History on the PBI you are moving into your new sprint, while leaving the old tasks in your old sprint. It is just a little bit of work, but can be done.
I believe we currently have a PBI in our backlog about this. You may want to weigh in on this idea as it pertains to this too: http://community.danube.com/danube/to... -
-
-
-
-
I want to weigh in on Zotte's question:
ScrumWorks Pro currently supports the "No Partial Credit" approach to sprint review and PBI evaluation.
That is, if the "acceptance criteria" of a backlog item is not 100% done, even if the *tasks* are all done, the item itself is not done. The suggested course in most Scrum lit is to move the item back to the backlog.
This doesn't affect velocity negatively since velocity equals the sum of story points "done" in a sprint. Moving an undone item back to the backlog doesn't affect this count.
I do see the value of somehow seeing what was committed to vs delivered in a sprint for historical tracking purposes. Thus the feature request Caleb pointed out.
http://community.danube.com/danube/to...
If this feature is important to you or others, please vote it up! -
-
Ok, I understand your point with PBIs but how about with tasks?
Is the best solution from tool perspective:
detour PBI's from backlog to new sprint and then copy-paste remaining tasks from ended sprint to new one? Or do you need to create manually tasks again? -
-
It depends on what you need to track. For example one customer I worked with just made a copy of the tasks and moved those to the new Sprint.
This preserved the history of the old tasks within the sprint, but also allowed the team to continue working on the tasks where they had left off. -
-
The Copy and Paste suggestion doesn't work in our installation of ScrumWorks Basic. Is this ScrumWorks Pro feature only?
-
Yes, this is a feature only found in ScrumWorks Pro.
-
-
-
-
EMPLOYEE
EMPLOYEE
