I find it helpful to keep in mind that the traditional statistical significance test is a statement about a conditional probability. i.e. it's the probability of the data given the hypothesis (the null hypothesis). But…
agree.. technically the velocity should be constant and more or less is.. but the story estimates still establish the building blocks for this.. a story seems to need tasks and task estimates to make the overall story…
We've been using Pivotal, but are about to switch over to Jira completely. Tried Trello. At end of day Trello and Pivotal are lacking 2 key features we need for better predictability in scrum, particularly on enterprise…
I find it helpful to keep in mind that the traditional statistical significance test is a statement about a conditional probability. i.e. it's the probability of the data given the hypothesis (the null hypothesis). But…
agree.. technically the velocity should be constant and more or less is.. but the story estimates still establish the building blocks for this.. a story seems to need tasks and task estimates to make the overall story…
We've been using Pivotal, but are about to switch over to Jira completely. Tried Trello. At end of day Trello and Pivotal are lacking 2 key features we need for better predictability in scrum, particularly on enterprise…