{"id":471,"date":"2011-05-07T15:10:33","date_gmt":"2011-05-07T15:10:33","guid":{"rendered":"http:\/\/mikekuphal.azurewebsites.net\/?p=471"},"modified":"2011-05-07T15:10:33","modified_gmt":"2011-05-07T15:10:33","slug":"agile-planning-planestimate-as-a-group-really","status":"publish","type":"post","link":"https:\/\/mikekuphal.com\/?p=471","title":{"rendered":"Agile Planning: Plan\/Estimate As A Group, Really?"},"content":{"rendered":"

\"Office<\/a>So you decided to go \u2018Agile\u2019 with your team?\u00a0 Maybe you have read a book or two on Scrum, XP, or something similar.\u00a0 Many of the base ideals of Agile development make intuitive sense, but this idea of \u201cGroup Planning\/Estimating\u201d\u2026\u00a0 Really?\u00a0 Surely that isn\u2019t going to work with \u2018my\u2019 team.<\/p>\n

I know this is where I was several months ago.\u00a0 The team I work with has been using a number of Agile concepts for years to get projects done, and doing it quite successfully I might add.\u00a0 I was reading up on Scrum, and intrigued by its simplicity yet didn\u2019t really get the idea of how important group collaboration is to its success right away.\u00a0 I had originally balked at the idea of having Daily Standups (after having them for months now, I realize how wrong I was on this), so the idea of having the whole team get into a room for several hours to \u201cplan\u201d (which includes some estimating) every two weeks (our chosen sprint length) just sounded so inefficient.\u00a0 I mean\u2026 isn\u2019t planning\/estimating the PM\u2019s job?\u00a0 Including all those people and taking them away from \u201cdevelopment time\u201d to plan?<\/p>\n

Well, I am here to say that a transition to group planning can be difficult, but once you work through the growing pains, it\u2019s well worth the effort.\u00a0 Don\u2019t short-change yourself by going 1\/2 way either.\u00a0 If you are planning for a 2 weeks sprint, and it\u2019s only taking 1\/2 hour to complete, you probably aren\u2019t planning as a group, but more just planning individually and meeting for a short time to pick tasks individually for the sprint.\u00a0 Most people I have spoken with or read online say it should take around 2 hours per week in the sprint to complete the planning processes.\u00a0 (4 hours for a two week sprint)\u00a0 This is dependent on the size of the team, complexity of the project, etc\u2026 but it\u2019s a good rule of thumb, and one that I have found to be about right given the number of sprints I have been involved with.<\/p>\n

There certainly is work that needs to be done prior to the planning meeting, especially by the ScrumMaster and Product Owner, to groom the project backlog as well as ensure the User Stories are in a state ready to be handed to the team.\u00a0 But the process of taking a feature and decomposing it into development tasks (unless most of the features you are building are trivial in nature), should be done by the team as who knows better than the ones who will be doing the work?\u00a0 Picking the tasks as a team, golden.\u00a0 Estimating the work as a team, what better way to ensure all team members have at least a semi-good understanding of the work being committed to? Having a say in this process also breeds ownership by the team and it\u2019s members.\u00a0 They have some \u2018skin in the game\u2019 from the planning stages, and that helps set them up for success to meet the goals of the sprint which is great for all involved.<\/p>\n

I highly recommend reading Agile Estimating and Planning<\/a> by Mike Cohn<\/a> as his book will help you work through the transition to group planning very well.<\/p>\n

My next post <\/a>will cover the \u2018Ideal Day\u2019 metric, and how I have found it helps the team size User Stories (features).<\/p>\n","protected":false},"excerpt":{"rendered":"

So you decided to go \u2018Agile\u2019 with your team?\u00a0 Maybe you have read a book or two on Scrum, XP, or something similar.\u00a0 Many of the base ideals of Agile development make intuitive sense, but this idea of \u201cGroup Planning\/Estimating\u201d\u2026\u00a0 Really?\u00a0 Surely that isn\u2019t going to work with \u2018my\u2019 team. I know this is where … Continue reading “Agile Planning: Plan\/Estimate As A Group, Really?”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2,5],"tags":[],"class_list":["post-471","post","type-post","status-publish","format-standard","hentry","category-agile","category-scrum"],"_links":{"self":[{"href":"https:\/\/mikekuphal.com\/index.php?rest_route=\/wp\/v2\/posts\/471","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mikekuphal.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mikekuphal.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mikekuphal.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mikekuphal.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=471"}],"version-history":[{"count":0,"href":"https:\/\/mikekuphal.com\/index.php?rest_route=\/wp\/v2\/posts\/471\/revisions"}],"wp:attachment":[{"href":"https:\/\/mikekuphal.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=471"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mikekuphal.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=471"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mikekuphal.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=471"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}