Hi,
We started adopting agile method for our development. previously we used to categorize our requirement based on the business function - eg: postpaid account maintenance functions - 2 or more requirement would fall under this category and will be tracked.
is there a way in rally where i can categorize all the user stories based on the functional area or Business flow
Comments
Packages provide the ability to group collections of Work Products into meaningful categories to help you organize your Work Products. User Stories, Defects, and Test Cases can be assigned to a Package.
Once the Package is created and populated, you can find a Package and all its elements by clicking the Searchtab, entering your Package search criteria, and selecting your Package in the resulting dialog. You can also filter and sort a package on each Work Product Summary page(User Story, Defect, and Test Case pages)
To create/update your package field follow these steps
1. Select Setup >> Workspaces & Projects
2. Click on the name of the workspace you want to edit.
3. Click on the Work Products & Fields link.
4. On this screen you will be able to select and create/edit the package field.
To create a value put a value a in the text box and click the Add Value button.
Edit an existing list item by highlighting it from the list of existing values. The list item appears in the text box below the list. Edit the value and click the icon to save the change. The value is updated and reflected in the list.
Remove an existing value by highlighting it from the list of existing values. The value appears in the Current Value text box below the list. Click the Remove button and the value is removed from the displayed list.
Re-order the list by highlighting a value and clicking the up or down arrows.
Reply to this Comment
I find the Packages concept to be somewhat lacking. If I define packages for one project, the packages dropdown will appear for all projects in my workspace. Is there another way to categorization (besides creating a bunch of parent-child relationships)?
Reply to this Comment
Unfortunately, you cannot define fields (custom or standard) on a per-project basis; rather, fields exist at the workspace level. This is why you are seeing the Package values for all of the projects within your workspace.
You could have a free-text field, though the downside to that is the reliance on users to enter information correctly.
You could prefix the story name with the business function. Similar downside to above, though.
Could you use either of those approaches?
Reply to this Comment
Is this only available in the Enterprise Edition? I don't see any Work Products & Fields link on the community edition.
Reply to this Comment
Steve,
Community Edition DOES include the ability to edit fields.
From Setup mode, click on your workspace name on the "Workspaces & Projects" tab, and select the "Work Products & Fields" hyperlink on the lefthand side.
Please let me know if you're not seeing that.
Thanks,
Reply to this Comment
My team has been using Packages effectively, as essentially to mean a "Theme" or Functional Area. Once all the stories are given a package value, it is easy to use in views for filtering, or for exporting to Excel for further grouping / total effort analysis by business component.
Reply to this Comment
Hi Dan,
The workarounds you propose can help....and we're doing them now. But I was surprised to see that Packages were configured at a Workspace level. This seems to be inflexible and makes me question the value of the workspaces concept (I'm starting to see many shortcomings with workspace vs. project config). I guess I will now set up Workspaces for each project because of this inflexibility.
Thanks,
Darrell
Reply to this Comment
Darrell, we do have a couple of existing feature requests that seem to fall into line with what you are looking for. If you get a chance, please head over and vote up these posts:
Project level custom fields
Project configuration
Reply to this Comment