Is there a way to change the Rally backlog to show a list of stories with sub-stories as a hierarchy? Right now our backlog makes more sense to just show epic level stories, but it is littered with very granular stories, so it is hard to prioritize at the epic level. Anyone else have this problem/solution?
Rally's backlog is primarily intended as an area to:
Prioritize
and then Schedule
Sprint-sized work products into Iterations. Because Epics aren't schedule-able, they don't show up in the backlog.
You may wish to consider stack-ranking epics from the Plan-User stories page. Or, alternatively, linking your epics to Features in Portfolio Manager, and relative-rank the Feature-linked Epics within the Feature's Story detail screen.
Related
I am analyzing Milk teas management website, that is a web online to help user buys via online and seller can manage their products, orders
I have to do Non-functional requirements and functional requirements for this website like this
FUNCTIONAL REQUIREMENTS
Register
Login
Add products to card
Submit order
Cancel order
NON - FUNCTIONAL REQUIREMENTS
Number of milk tea can be added to the cart
I am right for that? Can you give me some idea for this to let me improve better, I am new for this section, thank you so much
Functional Requirements
Good functional requirements should clearly describe the behavior of the system. Here are some examples:
"If the user enters the wrong password 3 times when signing in, the account shall be locked for 24h."
"When an electronics product is added to the cart, the user shall be presented with an option to purchase a warranty."
"If a user attempts to cancel an order after it has been processed, the user must specify the reason for the cancellation, which must be approved before a refund is issued"
If you want to add more functionality, create more requirements, don't pile them all into one. For example, the last requirement in the above list can be split into 2: (1) require cancellation reason, (2) approval before refund. It also helps to organize requirements by feature in spreadsheets (one row per requirement) or JIRA Stories, for example.
Make sure you read many examples of well-written requirements, and practice. Follow a checklist, and have a co-worker review your work. Always ask yourselves how you would test each requirement. If you can't figure out how to write a test for the requirement, how can you ever prove the product works as intended?
Non-Functional Requirements
Non-functional requirements are also known as "quality attributes" or "constraints" of the system. The range of possible items that can be added to a cart (0..max) seems like a constraint on that field, so I can see how some would consider this a NFR. But how would you test it?
Instead, you can express this like a functional requirement: "When the user enters a value that is greater than the maximum, display an error message". A NFR might describe the color, size and location of the error message. NFRs can also specify which UI kit to use and style guidelines to follow. For example, "Must follow Google Material Design" (https://material.io).
You should also be familiar with NFR categories (also known as the "ilities"):
Performance
Stability
Reliability
Scalability
Flexibility
Usability
Testability
Traceability/Auditability
Security
Compliance/Certification
Much More: https://en.wikipedia.org/wiki/Non-functional_requirement#Examples
Here are some examples of NFRs for a website:
Performance: "A new user account shall be created in less than 2000 ms"
Reliability: "The system shall have at least 99.9% availability"
Capacity: "The system shall service up to 1000 simultaneous users"
Scalability: "The system shall be horizontally scalable to increase the number of simultaneous users"
Usability: "Users should be able to navigate to any page in the site within 3 clicks"
References
Read these guidelines by the System Engineering Body of Knowledge (SEBoK). Follow them closely, share with your team:
https://www.sebokwiki.org/wiki/System_Requirements#Presentation_and_Quality_of_Requirements
This is an excellent book on large-scale agile requirements if you want to go deeper:
https://www.oreilly.com/library/view/agile-software-requirements/9780321685438/
Foreword: I've searched around on this question a fair bit and found answers which are close to a solution, but not what I'm looking for. So here I am, and I hope someone can help me. I'm relatively new to VSTS, so be gentle (or at least constructive) ;P
The Question: I'm looking for a way to restrict access to specific tickets (NOT by ticket type) that contain NDA protected data, whilst keeping them in the same backlog and iterations as the rest of the tickets related to a project.
We have many different NDA protected customers, so whilst creating a new ticket type per NDA, and restricting access to this, could work, it's not the solution I'm looking for.
Alternatively, I'm barking up the wrong tree, and there is an entirely different and "better way" to support this use-case?
Edit 1 - More info: Let's say I have 1 backlog for a product. It contains only 2 work items. It's important there is only 1 backlog for planning and overview by a product owner.
One of the two work items contains sensitive information only half the development team should have visibility to. How do I keep both tickets in the same backlog and iterations, but hide the sensitive one from some team members?
Thanks in advance for your time!
Regarding permission of work items in a team project, you can set the permission in area and iteration scope, but can’t for specific work items.
So, you need to put these work items in different area and manage permission for this area. Simple steps:
Go to team project admin page
Work=>Areas
Click New/New child, to create a new area.
Click …=>Security, set the permission for the group(s) or user(s)
Click the default team’s settings => Areas
Click + Select areas to add that area in order to show related work items (in that area)
Is there any way to set up a public view (View Only) of the Product Backlog Board for the customer see what we are working on and so?
It would be awesome too, if the customer could vote for backlog item that we haven't start working on it.
Trying to get the same concept of https://trello.com/ in TFS
The first thing (View Only) of the Product Backlog Board for the customer is easy to achieve. You just need to set related permissions for your customer or customer group.
Such as assign the user stakeholder access which have permission to view backlogs.
Assign Stakeholder access to those users who need to enter bugs, view
backlogs, boards, charts, and dashboards, but who don't have a TFS
CAL. Stakeholder access is free. Stakeholders can also view releases
and manage release approvals. See Stakeholder access for details of
features available to stakeholders.
Source Link: Change access levels
Then you need to deny some permissions which you don't want custom to have.
As for the second thing, there is no this kind of feature in TFS for now. Even though you have ability to prioritise Backlog items by dragging and dropping the item. If you need this feature, you can sumbit a feature requst in uservoice stie, TFS Admin and PM will kindly reveiw your suggestion.
In TFS 2015 using the Agile process template, the board for the "Stories" backlog shows only stories, and the board for the current iteration shows all tasks under stories. This makes sense for most teams.
We are breaking down our work into smaller than usual stories and thus avoiding task breakdown, so very few of our stories have tasks. Is there a way to show stories on the current iteration board instead of tasks, so that it looks similar to the higher-level stories board but with only the stories in the iteration?
In the end, I want to avoid a useless board like this:
Have you considered just using the Kanban/Backlog board?
My team don't use tasks at all, all our work is tracked on the Kanban board, we never use the Sprint Board.
Some teams add a "Sprint Backlog" column to show what is planned for the current sprint. Then you can collapse the "New" column until the next planning session.
Very fond of the release burn down chart, but as we have features from different areas in a single release I am looking to get a Burn Down Chart scoped to a specific top level story. In this case the only stories to be considered would be its leaf stories that are scheduled for the release in question.
Does anyone have an idea if this is possible or where to start? I found the code here: https://github.com/RallyApps/app-catalog/tree/master/src/apps/charts/burndown but couldn't see how to restrict the scope of the work products being considered.
Other ways I tried to get this view:
- I tried a custom view on the main user-stories view filtered to a release, but the summary rows give you a summary for all the stories in that tree, not just those which it filtered to
- Track work product status view only does story count whereas I need the total story points from the stories (not tasks) to be reported on
If anyone knows anywhere else I can get a nice view of a story hierarchy progress, scoped to a release that would also be helpful.
As a starting point, the app accesses historical data via Lookback API. Documentation for it is available here.
The example below is from "Work item hierarchy" section of that document:
To retrieve all Stories that descend from Story 333 (includes 333,
444, 555, 666, 888, and 999 but not Defect 777), you would include
this clause in your query:
{
_ItemHierarchy: 333,
_TypeHierarchy: “HierarchicalRequirement”
}
BurnDownChart.js from the repo has a store of type "Rally.data.lookback.SnapshotStore", which you may filter using work item hierarchy.
AppSDK2 SnapshotStore accesses data from Lookback API.