tag:blogger.com,1999:blog-7464205514452705951.post5766687195363613008..comments2023-11-02T11:42:34.387-04:00Comments on Juan Banda: Agile Estimation and Planning: Demystifying the Black ArtJuan Bandahttp://www.blogger.com/profile/12213871052044813213noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-7464205514452705951.post-11875732645742622512013-04-10T10:43:35.500-04:002013-04-10T10:43:35.500-04:00Regarding the value of the planning, not just the ...Regarding the value of the planning, not just the extent, this seems to be in question in many environments. I've tried to summarize some of the reasons to perform task-level estimation, along with some techniques: http://chrissteeleagile.com/task-estimation/Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-7464205514452705951.post-71193437173336939922010-07-21T17:50:36.978-04:002010-07-21T17:50:36.978-04:00"The team wants to split and re-size which of..."The team wants to split and re-size which often results in a larger point total. I believe this is normal but it is difficult to convince one very point-oriented PO of this. Have you seen this on your team(s)? "<br /><br />Well this is a common situation in Agile projects, there´re several dynamics occurring that triggers the need for re estimating. More often than not, re estimation implies adding points to the original estimates which is normal considering the degree of expertise that the team is acquiring as it progresses. <br /><br />What it worked fine for me was presenting these facts to POs like a more refined version of reality, without making-up things or trying to hold on unrealistic estimations. Usually POs have shock reactions but this is mitigated because the earlier that they know the better they can accommodate. <br /><br />Again, the principle is very simple: provide as much transparency as you can, even if you have to say that you´re estimations were completely offset. This transparency is what will allow the team and the PO to react in time.Juan Bandahttps://www.blogger.com/profile/12213871052044813213noreply@blogger.comtag:blogger.com,1999:blog-7464205514452705951.post-2370784112738005842010-07-04T02:59:23.884-04:002010-07-04T02:59:23.884-04:00Hi there, awesome site. I thought the topics you p...Hi there, awesome site. I thought the topics you posted on were very interesting. I tried to add your RSS to my feed reader and it a few. take a look at it, hopefully I can add you and follow.Scrum Processhttp://learnsoftwareprocesses.comnoreply@blogger.comtag:blogger.com,1999:blog-7464205514452705951.post-60285933700935363402010-06-20T13:53:27.071-04:002010-06-20T13:53:27.071-04:00Hi Juan, I like your commentary on re-estimating. ...Hi Juan, I like your commentary on re-estimating. I find that my product owners (I am a UPO with 3 POs) are sometimes surprised when they take a set of stories that were roughly sized a few months ago and try to add them to a sprint. The team wants to split and re-size which often results in a larger point total. I believe this is normal but it is difficult to convince one very point-oriented PO of this. Have you seen this on your team(s)?Anonymousnoreply@blogger.com