tag:blogger.com,1999:blog-6007320501812764218.post8404148321324481360..comments2010-02-17T09:38:38.533-06:00Comments on Off The Schneid: Parkinson's Law - A lesson in estimatingNate Schneiderhttp://www.blogger.com/profile/10566971472015747369noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-6007320501812764218.post-49598306380529976252009-01-28T10:29:00.000-06:002009-01-28T10:29:00.000-06:00I can't answer your question. All I can say about...I can't answer your question. All I can say about estimating is from when I was doing hardware development. I don't believe my group ever fell victim to Parkinson's Law because we never ever met our deadlines.Rosshttps://www.blogger.com/profile/18099651314360939371noreply@blogger.comtag:blogger.com,1999:blog-6007320501812764218.post-42729331524874926792009-01-28T09:41:00.000-06:002009-01-28T09:41:00.000-06:00My first thought to counter the question of "did w...My first thought to counter the question of "did we succumb to parkinson's law?" is this: Did you ever exceed your "attempted velocity" for an iteration? The question of whether or not you let your work fill the space is addressed if you ever added a new story to an iteration. <BR/><BR/>Also, I find Chris comment about aggressive vs conservative estimates intersting. I always thought the agile idea of getting a group consensus should eliminate any one person's propensity to pessimistically or optimisically estimate the size of a story or feature.<BR/><BR/>The feeling that some work was fluff might come from a less than stellar product owner; it's basically their job to keep the stories done in line with the vision for the project, keeping the team on track.<BR/><BR/>But to be honest, I'm new to agile concepts myself. Great post, it sounds like you're already doing your post-mortems: reviewing how you're applying agile and changing as you need to. Keep up the good work!Stevehttps://www.blogger.com/profile/10666232579579289254noreply@blogger.com