Requirements in V1

74 views
Skip to first unread message

Prave...@mcafee.com

unread,
Jul 15, 2012, 12:23:00 PM7/15/12
to VersionO...@googlegroups.com
Hi,
Could you let me know the versionOne feature to keep a repository of the product requirements?

John.Ai...@mitchell1.com

unread,
Jul 16, 2012, 1:19:43 PM7/16/12
to versiono...@googlegroups.com
Praveen,
When you create a Project in VersionOne that is a setting up a backlog
for the Stories (user requirements). The Projects are hierarchical so
you can traverse the tree to also get rollups from Child Projects you
have specified.

Within a Project you can use the Product Planning, Release Planning and
Sprint Tracking views to see the backlog items. There are some good
general videos under the Support Center option in VersionOne that will
walk you through this.

Regards, John

Sr. Software Manager
Mitchell1

"Be as great in act, as you have been in thought." -Willliam Shakespeare
--
You received this message because you are subscribed to the Google
Groups "VersionOne-users" group.
To post to this group, send email to versiono...@googlegroups.com.
To unsubscribe from this group, send email to
versionone-use...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/versionone-users?hl=en.

Prave...@mcafee.com

unread,
Jul 17, 2012, 7:35:07 AM7/17/12
to versiono...@googlegroups.com
Hi Mitchell,
Don't you think we should differentiate between a requirement and a story?

The process we follow is to come up with user story against the product requirements and import the stories to VersionOne. We track progress against these stories.
Since multiple stories can be clubbed under a product requirement, I'm looking for a way to keep the requirement in VersionOne for requirement traceability.
I was thinking of using the "Goals" feature in V1, but that is meant for a different purpose. I would appreciate if you could let me know of any way to keep the product requirements in V1.

Thanks,
Praveen RS

Nathan...@l-3com.com

unread,
Jul 17, 2012, 10:54:16 AM7/17/12
to versiono...@googlegroups.com
Praveen,

We use V1 Requests to represent this kind of a requirement on our
project. They can be linked/traced to multiple user stories.

-Nathan

John.Ai...@mitchell1.com

unread,
Jul 17, 2012, 12:31:10 PM7/17/12
to versiono...@googlegroups.com
Praveen,
Look at using the Epic artifact as well. Epics can be decomposed into
multiple Stories (like higher level requirements into lower) and
VersionOne has been improving the planning and tracking of these with
their recent releases.

Jeff Cox

unread,
Jul 17, 2012, 12:00:58 PM7/17/12
to versiono...@googlegroups.com
All

I may be missing something, but don't Epics serve this purpose?



Jeff

Nathan...@l-3com.com

unread,
Jul 18, 2012, 10:43:07 AM7/18/12
to versiono...@googlegroups.com
Yes, I agree epics would work, and some of the new functions for
managing them make them even better.
Reply all
Reply to author
Forward
0 new messages