Skip to main content
Estimating tag added, and split to paragraphs.
Source Link
Sarov
  • 14.8k
  • 5
  • 34
  • 64

We are combining all of our projects into one Kanban board. Since we are only ever one team, it seems to make the most sense to combine everything to one board and prioritize as we can all only work on one thing at a time.

Is there a good tool or method to calculate the completion date of a given story based purely on estimated time to complete, assigned user, given number of workable hours in a day, and known blocking items? I understand that this is always going to be an estimate and we need to be ready for change, but that's exactly why I'd like to do it. So the team can easily see that changing priority or adding other items causes certain completion dates of stories to be pushed back.

I would think that there is some way for a system to know, when an item will be completed. If, for example, it knows, that there is a backlog of 120 hrshours for a given user, and that our team only works on items from the board for 4 hours in a day. Of course, the final piece would be recognizing linked issues, that are blockers,blockers; so that for some items, it knows that other pieces must have beenbe completed first.

If it helps (or hurts, lol), we are using JIRA.

We are combining all of our projects into one Kanban board. Since we are only ever one team, it seems to make the most sense to combine everything to one board and prioritize as we can all only work on one thing at a time.

Is there a good tool or method to calculate the completion date of a given story based purely on estimated time to complete, assigned user, given number of workable hours in a day, and known blocking items? I understand that this is always going to be an estimate and we need to be ready for change, but that's exactly why I'd like to do it. So the team can easily see that changing priority or adding other items causes certain completion dates of stories to be pushed back.

I would think that there is some way for a system to know, when an item will be completed. If for example it knows, that there is a backlog of 120 hrs for a given user, and that our team only works on items from the board for 4 hours in a day. Of course, the final piece would be recognizing linked issues, that are blockers, so that for some items, it knows that other pieces must have been completed first.

If it helps (or hurts, lol), we are using JIRA.

We are combining all of our projects into one Kanban board. Since we are only ever one team, it seems to make the most sense to combine everything to one board and prioritize as we can all only work on one thing at a time.

Is there a good tool or method to calculate the completion date of a given story based purely on estimated time to complete, assigned user, given number of workable hours in a day and known blocking items? I understand that this is always going to be an estimate and we need to be ready for change, but that's exactly why I'd like to do it. So the team can easily see that changing priority or adding other items causes certain completion dates of stories to be pushed back.

I would think that there is some way for a system to know when an item will be completed. If, for example, it knows that there is a backlog of 120 hours for a given user and that our team only works on items from the board for 4 hours in a day. Of course, the final piece would be recognizing linked issues, that are blockers; so that for some items, it knows that other pieces must be completed first.

If it helps (or hurts, lol), we are using JIRA.

We are combining all of our projects into one Kanban board. Since we are only ever one team, it seems to make the most sense to combine everything to one board and prioritize as we can all only work on one thing at a time. Is

Is there a good tool or method to calculate the completion date of a given story based purely on estimated time to complete, assigned user, given number of workable hours in a day, and known blocking items? I understand that this is always going to be an estimate and we need to be ready for change, but that's exactly why I'd like to do it. So the team can easily see that changing priority or adding other items causes certain completion dates of stories to be pushed back. I

I would think that there is some way for a system to know, when an item will be completed if. If for example it knows, that there is a backlog of 120hours120 hrs for a given user, and that our team only works on items from the board for 4 hours in a day. Of course, the final piece would be recognizing linked issues, that are blockers, so that for some items, it knows that other pieces must have been completed first.

If it helps (or hurts, lol), we are using JIRA.

We are combining all of our projects into one Kanban board. Since we are only ever one team, it seems to make the most sense to combine everything to one board and prioritize as we can all only work on one thing at a time. Is there a good tool or method to calculate the completion date of a given story based purely on estimated time to complete, assigned user, given number of workable hours in a day, and known blocking items? I understand that this is always going to be an estimate and we need to be ready for change, but that's exactly why I'd like to do it. So the team can easily see that changing priority or adding other items causes certain completion dates of stories to be pushed back. I would think that there is some way for a system to know when an item will be completed if for example it knows that there is a backlog of 120hours for a given user and that our team only works on items from the board for 4 hours in a day. Of course the final piece would be recognizing linked issues that are blockers so that for some items, it knows that other pieces must have been completed first.

If it helps (or hurts, lol), we are using JIRA.

We are combining all of our projects into one Kanban board. Since we are only ever one team, it seems to make the most sense to combine everything to one board and prioritize as we can all only work on one thing at a time.

Is there a good tool or method to calculate the completion date of a given story based purely on estimated time to complete, assigned user, given number of workable hours in a day, and known blocking items? I understand that this is always going to be an estimate and we need to be ready for change, but that's exactly why I'd like to do it. So the team can easily see that changing priority or adding other items causes certain completion dates of stories to be pushed back.

I would think that there is some way for a system to know, when an item will be completed. If for example it knows, that there is a backlog of 120 hrs for a given user, and that our team only works on items from the board for 4 hours in a day. Of course, the final piece would be recognizing linked issues, that are blockers, so that for some items, it knows that other pieces must have been completed first.

If it helps (or hurts, lol), we are using JIRA.

Tweeted twitter.com/StackProjects/status/834164869494665217
Source Link

Estimate Item Delivery from Throughput plus blockers

We are combining all of our projects into one Kanban board. Since we are only ever one team, it seems to make the most sense to combine everything to one board and prioritize as we can all only work on one thing at a time. Is there a good tool or method to calculate the completion date of a given story based purely on estimated time to complete, assigned user, given number of workable hours in a day, and known blocking items? I understand that this is always going to be an estimate and we need to be ready for change, but that's exactly why I'd like to do it. So the team can easily see that changing priority or adding other items causes certain completion dates of stories to be pushed back. I would think that there is some way for a system to know when an item will be completed if for example it knows that there is a backlog of 120hours for a given user and that our team only works on items from the board for 4 hours in a day. Of course the final piece would be recognizing linked issues that are blockers so that for some items, it knows that other pieces must have been completed first.

If it helps (or hurts, lol), we are using JIRA.