This question is locked. New answers and comments are not allowed.
Hello!
Before creating a new request I would like to comment about this problem we have in our team, to see if other people have this problem, how they solve it, if there is any workaround within TeamPulse, or if we are just doing something wrong :)
We have now 3 projects at TeamPulse, 2 are for internal tools, and 1 for the app we sell, and there are some requirements that we want to reuse.
For example, we have a feature for logging errors.
"As a Support Technician I want that all the details of the application errors are recorded so that I can know what is going wrong with the application and to get some clues to solve the problem" (Something like this, and some other related requirements, acceptance criteria, etc.)
And there are lots of basic requirements like this that apply to more than 1 project.
So you could say "just copy them" but we don't want a copy, because if we change it, we probably want to improve the functionality across all the projects, so we would have to duplicate those requirements, and make every change for each copy (and maybe some code behind the functionality is also the same, so it's easy to change it everywhere). And duplication always causes problems.
At the other hand, I'm not sure that having exactly the same requirement record shared across all the projects would work, because the status of the requirement may not be the same, it needs some implementation and tests for each project, for example, at one project the requirement status can be "New" because we have just started the project and at another project can be "Completed".
I have seen some requests that could be related to this problem...
http://feedback.telerik.com/Project/8/Feedback/Details/329
http://feedback.telerik.com/Project/8/Feedback/Details/297
http://feedback.telerik.com/Project/8/Feedback/Details/223
Before creating a new request I would like to comment about this problem we have in our team, to see if other people have this problem, how they solve it, if there is any workaround within TeamPulse, or if we are just doing something wrong :)
We have now 3 projects at TeamPulse, 2 are for internal tools, and 1 for the app we sell, and there are some requirements that we want to reuse.
For example, we have a feature for logging errors.
"As a Support Technician I want that all the details of the application errors are recorded so that I can know what is going wrong with the application and to get some clues to solve the problem" (Something like this, and some other related requirements, acceptance criteria, etc.)
And there are lots of basic requirements like this that apply to more than 1 project.
So you could say "just copy them" but we don't want a copy, because if we change it, we probably want to improve the functionality across all the projects, so we would have to duplicate those requirements, and make every change for each copy (and maybe some code behind the functionality is also the same, so it's easy to change it everywhere). And duplication always causes problems.
At the other hand, I'm not sure that having exactly the same requirement record shared across all the projects would work, because the status of the requirement may not be the same, it needs some implementation and tests for each project, for example, at one project the requirement status can be "New" because we have just started the project and at another project can be "Completed".
I have seen some requests that could be related to this problem...
http://feedback.telerik.com/Project/8/Feedback/Details/329
http://feedback.telerik.com/Project/8/Feedback/Details/297
http://feedback.telerik.com/Project/8/Feedback/Details/223
3 Answers, 1 is accepted
0
Hi Raquel,
That is an interesting issue you have there, but not that uncommon.
Unfortunately, in TeamPulse, we don't have a very elegant way to handle it.
The best I could recommend is to create a separate TeamPulse project to hold just the common stories and then in the 3 working projects where they are implemented, create a copy of the story that captures your implementation of the common story and in that copy, place a hyperlink back to the common (or parent) story. These have to be hyperlinks and not story links since we don't support cross project story links yet.
As the parent story changes, I'd create new stories in the common stories project that capture the improvements. Don't just update the story that's already there since that story really should be Done. These new improvement stories would have a story link to the parent so you have some traceability and then as you implement these improvements in the other working projects, you'd create new stories in the 3 working projects with hyperlinks back to the parent, much like you did with the original work.
The key is not to have a single story that you continue to expand upon, but to have a series of stories that individually track improvements. That way you can track the progress of each improvement as it is implemented.
Hope this helps.
All the best,
Steve
TeamPulse Product Owner
Visit our Ideas & Feedback portal to submit a feature request, vote on existing requests or submit general feedback.
That is an interesting issue you have there, but not that uncommon.
Unfortunately, in TeamPulse, we don't have a very elegant way to handle it.
The best I could recommend is to create a separate TeamPulse project to hold just the common stories and then in the 3 working projects where they are implemented, create a copy of the story that captures your implementation of the common story and in that copy, place a hyperlink back to the common (or parent) story. These have to be hyperlinks and not story links since we don't support cross project story links yet.
As the parent story changes, I'd create new stories in the common stories project that capture the improvements. Don't just update the story that's already there since that story really should be Done. These new improvement stories would have a story link to the parent so you have some traceability and then as you implement these improvements in the other working projects, you'd create new stories in the 3 working projects with hyperlinks back to the parent, much like you did with the original work.
The key is not to have a single story that you continue to expand upon, but to have a series of stories that individually track improvements. That way you can track the progress of each improvement as it is implemented.
Hope this helps.
All the best,
Steve
TeamPulse Product Owner
Visit our Ideas & Feedback portal to submit a feature request, vote on existing requests or submit general feedback.
0
Rach
Top achievements
Rank 1
Rank 1
answered on 19 Apr 2012, 09:50 AM
Thanks for your answer.
Is not a bad idea, but as far as I know there is no way to automatically copy requirements from one project to another, so it's going to be a lot of work to do this manually.
I will give some votes to the related requests...
Is not a bad idea, but as far as I know there is no way to automatically copy requirements from one project to another, so it's going to be a lot of work to do this manually.
I will give some votes to the related requests...
0
Hi Raquel,
You're right that currently they is no way to copy a story and paste it into another project. The best you can do at the moment use the Export feature available above almost any grid that displays stories and then use the Import Stories page to bring them in to another project.
Regards,
Joel
the Telerik team
Visit our Ideas & Feedback portal to submit a feature request, vote on existing requests or submit general feedback.
You're right that currently they is no way to copy a story and paste it into another project. The best you can do at the moment use the Export feature available above almost any grid that displays stories and then use the Import Stories page to bring them in to another project.
Regards,
Joel
the Telerik team
Visit our Ideas & Feedback portal to submit a feature request, vote on existing requests or submit general feedback.