Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Requirements in V1
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  7 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
praveen...@mcafee.com  
View profile   Translate to Translated (View Original)
 More options Jul 15 2012, 12:23 pm
From: <Praveen...@McAfee.com>
Date: Sun, 15 Jul 2012 09:23:00 -0700
Subject: Requirements in V1
Hi,
Could you let me know the versionOne feature to keep a repository of the product requirements?

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
john.ainswo...@mitchell1.com  
View profile  
 More options Jul 16 2012, 1:19 pm
From: <John.Ainswo...@mitchell1.com>
Date: Mon, 16 Jul 2012 10:19:43 -0700
Local: Mon, Jul 16 2012 1:19 pm
Subject: RE: Requirements in V1
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 must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
praveen...@mcafee.com  
View profile  
 More options Jul 17 2012, 7:35 am
From: <Praveen...@McAfee.com>
Date: Tue, 17 Jul 2012 04:35:07 -0700
Local: Tues, Jul 17 2012 7:35 am
Subject: RE: Requirements in V1
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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
nathan.ba...@l-3com.com  
View profile  
 More options Jul 17 2012, 10:54 am
From: Nathan.Ba...@l-3com.com
Date: Tue, 17 Jul 2012 09:54:16 -0500
Local: Tues, Jul 17 2012 10:54 am
Subject: RE: Requirements in V1
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


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
john.ainswo...@mitchell1.com  
View profile  
 More options Jul 17 2012, 12:31 pm
From: <John.Ainswo...@mitchell1.com>
Date: Tue, 17 Jul 2012 09:31:10 -0700
Local: Tues, Jul 17 2012 12:31 pm
Subject: RE: Requirements in V1
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.  

Regards, John

Sr. Software Manager
Mitchell1

"Be as great in act, as you have been in thought." -Willliam Shakespeare


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Jeff Cox  
View profile  
 More options Jul 17 2012, 12:00 pm
From: Jeff Cox <jeff....@ericsson.com>
Date: Tue, 17 Jul 2012 12:00:58 -0400
Local: Tues, Jul 17 2012 12:00 pm
Subject: RE: Requirements in V1
All

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

Jeff


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
nathan.ba...@l-3com.com  
View profile  
 More options Jul 18 2012, 10:43 am
From: Nathan.Ba...@l-3com.com
Date: Wed, 18 Jul 2012 09:43:07 -0500
Local: Wed, Jul 18 2012 10:43 am
Subject: RE: Requirements in V1
Yes, I agree epics would work, and some of the new functions for
managing them make them even better.

-Nathan


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »