I have stories with subtasks (we make heavy use of them) I would like
1) That when all sub-tasks of a story are done, the story moves alone to done
2) That when a story is moved (for instance) from "Idea" to "Backlog", or from "Backlog" to "Ready", all its sub-tasks move with him. So in coders language, that when a Story is moved by dragging the story, all related sub-tasks status get's overridden by the new story status.
The boards structure guarantees no problems since the PO has only one colum for all development status (dev, review, etc) and development scrum board has only status those dev, review, etc colums so .. Everything should be Ok
Furthermore the PO board is only viewing stories and using Epics as swimlanes so he cannot see the sub-tasks moving. And the developers board is only showing sub-tasks using stories as swimlines.
So developers cannot move the stories to Done.. only the sub-tasks.
Can do all this through validators on workflow transitions
Related
On my Kanban board project I have the option to add swimlanes on the Features where all the product backlog items are and another option on the Stories side.
Which would be the approach of each of them and why should be their separate use.
For example, I have on my Feature option an Expedited lane, does it make sense to leave it there or that options is more a swimlane that belongs to the Stories option?
As you can see I can set as many swimlanes I need, I found useful to have for example one swimlane per project on the Features option if I suppose to work with more than one at the same time, but in the other hand it gets me confused because I have the same option on Stories
Usually we use Product Backlog items(PBIs) to represent the work you want to develop and ship. You track bugs, tasks, and blocking issues using the bug, task, and issue WITs. To support portfolio management, teams create features and epics to view a roll up of user stories within or across teams. We usually map some PBIs under feature. The Feature could be the Parent of PBIs.
The Expedited Swinlanes could be used to both at Feature board or Stories Board to track those workitems which are urgent. For more details, you could read this document: https://www.visualstudio.com/en-us/docs/work/kanban/expedite-work#types-of-swimlanes
You create Swimlanes for each project also makes sense. In the Stories board, you could also create swimlanes the same like the Feature board to divided those workitems. But I suggest that you could create a team for each project, move those corresponding workitems to each team. Or you could create Areas for each project, using Area to distinguish them
We're still fine-tuning our ALM process using TFS 2015 Update 1 On-Prem. We are using the standard SCRUM template and we display bugs on the backlog, along with requirements. Bugs are reported by the business and go through the same level of analysis as PBIs in that they will contain child tasks:
Now for PBIs, when a tester is testing the PBI and discovers a bug with it (which needs to be fixed as part of this sprint), they will create a bug as a child to the PBI. This keeps them together on the task board. 1 PBI may have many bugs and these may be worked on by different people. These child bugs will have child tasks.
The process mostly works but on the Kanban board, the child bugs are shown, the parent PBIs are not. Why not? and how can I work-around this? I can link them differently but we want them to stay together on the boards.
Thanks
It feels like you're really mixing and matching the two supported scenarios here.
Personally I prefer not to create Bugs as part of the sprint (to me they're not really bugs if they haven't made it out of the iteration) and often it's used as a communication mechanism instead of dev & test working closely together.
If you want something on the board under the PBI/Bug, you could use a Task Work Item (or a custom type) and then use the funky card colouring on the board to look for a tag to signify that it's an in-sprint bug/issue.
Highlight work items based on custom criteria
I have two project setup, both using the Scrum template. In one of them the sprint backlog board shows swim lanes/columns as I would expect:
To Do
In Progress
Done
In my other project (the one that matters, of course), it looks as if the columns from the Backlog Items have been merged with those of the Sprint Backlog items and displays with all of these columns:
To Do
New
Approved
In Progress
Committed
Done
The extra columns appear to be read-only in the board view and do nothing but make the board cumbersome to use. Have I changed a setting somewhere that affects this?
You probably have one team (or project) configured to have bugs on the backlog as requirements, and another team/project configured to have bugs on the backlog as tasks.
Bugs have a different set of states, so if you treat bugs as tasks, the board will show two sets of states: One for bugs, one for tasks.
This can be configured by going to your team's settings (click on the "gear" icon on the top right in VSO, then Overview tab, then choosing the team and looking at the settings).
Daniel's answer pointed me in the right direction, but it still wasn't clear exactly what steps to go through to fix the issue. Here are step-by-step instructions on how to set the number of columns on your sprint board based on how your team works with bugs.
Note that this is a modification from my original answer. The way to fix this has become dramatically easier after the latest update to VSO.
Click the gear to edit settings on the sprint board:
Click Working with bugs under the general heading in the left column.
The option you select here determines how many columns appear on your sprint board.
To manage the scrum development process of a big community website, we decided to move to JIRA/Greenhopper/Bonfire.
I have created elaborate Epic, Stories and Tasks, all well linked to each other.
I would like to develop the "Product Story" in more detail all the time by adding new Epics, new Stories to (new or existing) Epics, etc.
To be able to do this properly, I want to have a hierarchical overview of all issues: Epics, Stories, Tasks, etc.
Question: How do we set this up in JIRA?
Why?
=> My approach is from the point of view of project management: getting everybody aligned around the same vision. However, I think it is part for everyone in the team -especially for the ones who are actually building the product- to have a quick view of how their current or planned work fits into the big picture.
Stories have sub-tasks, which will be shown hierarchically in the Sprint, but all sub-tasks have to be completed in the sprint of the user story. I also think when you create a story you can specify an epic, which will create a hard-link ( the same as story -> sub-task). Is there a reason you want to use a Jira task? To me it looks that in a SCRUM environment you only need Epics, stories and sub-tasks. Maybe some spikes and support tickets from time to time.
Coming from a tool like Rally, I can appreciate you wanting to see the big picture. We transitioned from Rally to Greenhopper over a year ago mainly because of costs. Lets just say you get what your pay for. I haven't found the feature you're looking for in Greenhopper, it only has a single threaded view for things like Epics to Stories (on the planning page) or Stories to tasks on the (on the work page)
In a SCRUM Agile project we use TFS 2010/VS2010.
In the period before starting this project, the customer has already written out 80% of all the use cases. The issue is that most of these UCs are so large, that I want to split them up in user stories. The user stories can be compared to scenarios for the use cases.
My plan is now use the Agile process template and start creating top level user stories as use cases. Each top level use case will have 1 or more user stories as child beneath the parent user story. Then below the 2nd level user story I add one or more tasks where developers can do their checkin against.
Is this the right approach ?
Yes it is, the proof is that when you create a child work item from a User Story only two types are available: Task and User Story.
This is made to split big User Stories into a subset of smaller ones.