Practicing agile theory

Here I discuss the curious case of mixing story points and person days and using them synonymously, not understanding what a monumental difference it is, in terms of arriving at a schedule using the two. While the team is using T-Shirt sizing (or planning poker) to come up with a backlog size in Story Points, they are using the words "Story Points" and "Person Days" interchangeably. As a prologue to my previous post https://practicing-agile.blogspot.com/2019/08/when-you-equate-story-points-with-time.html - the objective in this one is to find the answer to the question -  "How does a backlog estimate in terms of Story Points translate to how long will it take for the team to deliver the backlog, given that requirements, technology and a lot of various other factors influencing estimates are bound to change?" In other words, if the backlog size is 120 Story Points, its equivalent to saying that the backlog is worth 120 PDs of work! A derivatio...

An analogy - Ever thought of how Agile scrum could very closely be compared with a "road trip" that almost everyone must've taken sometime in their lifetime? In arriving at the destination ( Product ), there's a lot that goes into the journey -  the Scrum Team must have visibility ( Vision, Roadmap ) to start with, along with an awareness of the road conditions ( Project Transparency ).  That said, the team must have an understanding of traffic/driving rules ( Scrum Processes ) and the vehicle chosen for the trip, should be in a good working condition ( Dev Environment ). With those as prerequisites to begin - The driver must have the knowledge of the route/directions to get to the destination ( Knowledge/Expertise/Competence of developers ). In addition, the driver must have enough fuel ( Motivation ) to get the journey started & keep it going until the team has arrived at the destination ( Product ). While the above sounds simple, during the j...