[dirklectisch]

Author of the article here.

I normally recommend when starting out to take a small segment of your process first and then widen it as you get more experience.

For the start point I usually try to think of these aspects:

- Can work still be cancelled at this part of the process. If so it's probably not the right spot to measure the start date.

- Can work still be reprioritized at this point in the process? If so that will significantly widen the precision of the predictions that the forecast will make.

Also note that setting a the start date at the moment of commitment still gives you valuable insights in how much work you will be a able to next.

For setting the end date I think when the software is released is the most interesting point to measure. As always it depends on context. If you do a yearly release this doesn't make any sense because the granularity of all your predictions will be a year.