Recent activity
Subscribe to this feed
A comment on the question "How to properly remove a requirement/user story/task from a running sprint?" in agile42:
I guess that's a workaround that could possibly work. One way Agilo could take care of this, is to offer the user an action to "remove" a user story / task from a sprint, but instead of just removing it, it would create a 'shadow ticket' in its place, status of which would be closed, and it's resolution: removed. The shadow ticket would of course include proper links to the original story. – Primož Verdnik, on June 29, 2009 05:06
A comment on the question "How to properly remove a requirement/user story/task from a running sprint?" in agile42:
Thanks for your reply. I'm really glad you guys opened your Agilo (https://dev.agile42.com/) for the public to see, and I hope to find this feature in the backlog soon ;)
Cheers – Primož Verdnik, on June 18, 2009 14:25
Primož Verdnik marked one of Felix Schwarz's replies in agile42 as useful. Felix Schwarz replied to the question "How to properly remove a requirement/user story/task from a running sprint?".
Primož Verdnik asked a question in agile42 on June 17, 2009 08:40:
How to properly remove a requirement/user story/task from a running sprint?How to properly remove a requirement/user story/task from a running sprint?
Half way through the sprint we realized that we won't be able to achieve the sprint goal, so the product owner decided, that one of the bigger features will be taken out of the running sprint.
This is how agilo renders the burndown chart, when we remove the sprint property value from the user story.
Before the user story has been taken out:
After the story has been taken out:
The problem I see with this is: The interpretation of the burndown chart now doesn't reflect the fact, that a user story was taken out from the sprint. In fact, now it looks like the task was never there in the first place. What we want to see there is a sharp vertical decline that would correctly reflect the removal of the user story.
Is there another option of removing user stories? Are we doing something wrong?
Thanks for the answer, and thanks for making Agilo. It's helping us immensely.
Primož Verdnik replied on December 24, 2008 09:40 to the question "Soocial did not dedupe or merge my contacts, now I have duplicates everywhere" in Soocial:
I have many cases where I have two or up to five instances of contacts, which are the same person. First name and last name are exactly the same in the dupes. In fact, the rule "same name same person" would probably work for me for every dupe i have.
I hope that either you guys or Google provide a working and usable merging solution.
Keep up the good work, you still rock ;)
drye replied on December 23, 2008 15:28 to the question "Soocial did not dedupe or merge my contacts, now I have duplicates everywhere" in Soocial:
Loading Profile...

