3

TL;DR A research spike is intended to reduce the cone of uncertainty for future work. It is not intended to deliver shippable increments of anything. Treating the output of a spike as anything other than input to story planning/refinement is a Scrum implementation smell. Time-Box Your Spikes As an empirical control framework, Scrum is heavily reliant on ...


3

There are a few things to consider. Regarding "constant pace", the Manifest for Agile Software Development says: Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. This does not say anything about the complexity of work increasing or decreasing over time. It also ...


2

TL;DR I'm not going to address your math directly, because it's a solution for Y in an X/Y problem. Specifically, how long it takes to complete your current backlog should be a function of your current lead and cycle times, not an invitation to resize your queues or attempt to crash the project by adding additional resources. What you really ought to do is ...


1

I know of at least two "Empirical assessment of machine learning models for agile software development effort estimation using story points". Available online at https://link.springer.com/article/10.1007/s11334-017-0288-z "Empirical Validation of Neural Network Models for Agile Software Effort Estimation based on Story Points". Available online at https://...


1

Each person in a team may have his personal understanding of the correlation between an effort and Story Points. Initially, in a new team, that may be true. That is why an estimation based on Story Points is more than each team member just giving a number and then taking the lowest/highest/average/whatever as the final estimate. When doing a Story Point ...


1

Story points are a relative measure of effort rather than an absolute one. However, each member of the team should have the same understanding of the size of a points estimate. A common understanding is achieved when the team estimates repeatedly together and when they agree common baseline stories against which to measure. This is really no different to ...


1

Mike Cohn has a great article on Story Points. Some of the highlights are Story points are a unit of measure for expressing an estimate of the overall effort that will be required to fully implement a product backlog item or any other piece of work. ... Because story points represent the effort to develop a story, a team’s estimate must ...


1

The purpose of the limited timebox is to force the team to break down larger items into smaller ones. 2 weeks is a long time for research. I usually look for research tasks to be measured in hours, not days, let alone weeks. You may need to consider exactly what it is you are researching. Some common ways to approach this include: In pure research, what ...


Only top voted, non community-wiki answers of a minimum length are eligible