Update Estimations

Added A Fair Way to Get Up to Par with Reference Stories

Estimation.md

@@ -2,6 +2,8 @@
 
 - [12 Common Mistakes Made When Using Story Points](https://medium.com/bynder-tech/12-common-mistakes-made-when-using-story-points-f0bb9212d2f7) - by Maarten Dalmijn. "Being aware of mistakes that can be made when using Story Points helps applying them the right way."
 
+- [A Fair Way to Get Up to Par with Reference Stories](https://ragozzine.github.io/post/2019-04-13-a-fair-way-to-get-up-to-par-with-reference-stories/) - by Alley. "TIn the end, teams should estimate tasks based on the present state of things, with each individual making a judgment call through the criteria of complexity, effort, and risk. Reference stories can help guide team members to suggest a point value that makes sense to them."
+
 - [Accuratizing Software Estimation](https://medium.com/pointer-io/accuratizing-software-estimation-cf81a9e9fd87) - by Chet Haase. "The initial answer given by the engineer was reasonable, given their knowledge of the problem domain at the time. It’s just that engineers are always optimistic, accounting only for how long something might take in the best situation, with the best minds, where nothing goes wrong and management leaves them the hell alone. But this never happens in reality, so we need to apply our knowledge of typical software product schedules to derive a more accurate answer."
 
 - [Agile Estimating and Planning: Planning Poker](https://www.youtube.com/watch?v=MrIZMuvjTws) (Video) - by Mike Cohn. "In this video, Mike explains how to play Planning Poker to collaboratively estimate an agile or Scrum team's product backlog."