SCRUM For Wedding Planning – Notes

<p><a href=""><img title="Gregory Heller at Ignite Seattle 12 by Randy Stewart" src="" alt="Gregory Heller at Ignite Seattle 12 by Randy Stewart" hspace="10" align="left" /></a>Yesterday I presented an Ignite Talk at <a href="" target="_blank">Ignite Seattle 12</a> on the topic of using <a href="" target="_self">SCRUM Project Management for wedding planning</a>.  I've heard people liked it, and some people asked me for some more information.  The video will surely be out soon enough, and I posted my slides already.  But slides without audio don't help that much, so until the video comes out, I figured I would post my notes.</p>
<p>This is a bit of an "opening the kimono" moment.  What you will see in the notes below, which I will not edit significantly from what I used to prep yesterday, is that I dropped alot as I worked toward the final genesis of the talk (if you were there, or when you see the video). I prepared my initial notes, which were more of a rough draft of an essay first, then produced my slide deck last week. I didn't finalize the notes until Monday, and polished the presentation on Tuesday. I'd say I spent about an hour per minute preparing which is in sharp contrast to my last <a href="">Ignite Seattle talk in 2009</a> for which I probably spent 3 hours or more per minute of presentation.</p>
<p>A few tips I've learned about slide design: use a black background, and use high contrast fonts in large point sizes. Like 60pt or higher, the large words on my slides are all above 80pt.  The credits are between 18pt and 40pt.  Where I used images, I tried to make them as large as possible (full screen). Using the black background doesn't call attention to where the image ends and empty space on the slide when projected.</p>
<p>So here are my notes:</p>
<p><strong>1. Title Screen</strong></p>
<p>I'm a certified scrum master and I am going to tell you from my recent experience how you can use SCRUM to plan your wedding and stay sane while doing it.</p>
<p>SCRUM is a project management style designed for agile software development</p>
<p>It allows a product/project to respond to changing market demands without throwing out the entire project into jeopardy</p>
<p>Helps to cut down waste and waiting periods</p>
<p>reducing employee stress while simultaneously increasing productivity.</p>
<p><strong>2. Why is it well suited for wedding planning?</strong></p>
<p>Its well suited for Wedding planning because it is all about time boxes, Once you pick a date, your working against the clock. On the wedding day, you are getting married, and what you have gotten done by that day is all that you will get done.</p>
<p><strong>3. CALENDAR</strong></p>
<p>Scrum does not allow a delivery date to be altered! Just like most weddings. if you are behind on your work, you triage – delete items in the Sprint Backlog.</p>
<p><strong>4. BACKLOG</strong></p>
<p>The <strong>product backlog</strong> is a list of all the “features” of your wedding.</p>
<p>The items on the list are really groupings of other tasks, in a software project they would be feature requests like “user can post video”, not “code video upload” “code video player” those would be the tasks on the sprint backlog.</p>
<p>When you think of new “features”, add them to the product backlog where they wait to be placed onto a sprint backlog.</p>
<p><strong>5. The sprint backlog</strong> is a list of all the to-do items you are going to work on in a specific sprint, and they are, necessarily, more detailed than the items you initially put on your product backlog.</p>
<p><strong>6. Sprints</strong></p>
<p>In SCRUM a sprint would typically be 30 days, but depending on how long you have to plan your wedding your “Sprints” could be longer or shorter: 10 to 45 days</p>
<p>Sprints allow you to logically group to do items based on the date they need to be done. In wedding planning there are a few distinct phases, getting the invitations out. Getting the clothing and decorations ordered. Finalizing the menu and other reception details.</p>
<p><strong>7. SCRUM DIAGRAM</strong></p>
<p>Don't bother trying to understand this slide now. Check it out online later at</p>
<p><strong>8. BOUNDARIES</strong></p>
<p>Sprints don't need to run back to back with no breaks in between. The sprints create a boundary between the wedding planning and the rest of your life leaving you time for things like vacations, holidays, time with friends and your job.</p>
<p><strong>9. Shipable</strong></p>
<p>SCRUM emphasizes developing “shipable units” of product, meaning you complete something and it is ready to go. In the context of wedding planning this is important too. If it is not truly done, it's useless. Focus on the things you can finish, finish them completely within a sprint and move on. As soon as something looks like it will not get done, drop it from the sprint and move on.</p>
<p><strong>10. DONE</strong></p>
<p>What does DONE mean? Anyone who's worked on a software team knows that 2 engineers will have 3 opinions. You and your partner need to understand DONE the same way, and you need to write the tasks on your backlogs in such a way that when you mark them DONE, you know that they are ready to go, no more work necessary.</p>
<p><strong>11 Invites</strong></p>
<p>Take for example “Wedding Invitations”</p>
<p>As an item on your backlog it is hopelessly vague. On your sprint backlog it includes: ordering samples, asking a friend to help design them, finding a printer, picking paper, getting envelopes, having them printed, stuffing them, finding a pen that writes best on the metallic paper of the envelops you bought, addressing them, buying the stamps and actually mailing them.</p>
<p><strong>12 Prioritize</strong></p>
<p>It is absolutely important to prioritize the items on your product and sprint backlogs so that you know you are getting the most important things done. As our planning progressed we adjusted the priority of items. Some things were always a priority 1, but as time and other resources got short, there were priority 2 or 3s that got dropped.</p>
<p><strong>13 SCRUM TEAM</strong></p>
<p>A typical SCRUM team team is 5 to 7 people, modified SCRUM for wedding planning has a small SCRUM team: you and the one you are going to marry. There is no SCRUM master, and you are both the Product Owner.</p>
<p><strong>14 CHICKENS AND PIGS</strong></p>
<p>If you've read about SCRUM, you might have seen a reference to Chickens and Pigs. The story goes that a chicken and a pig were hanging out one day when the chicken suggested they open a restaurant, the pig asked what they should call it, to which the chicken replied “Ham and Eggs.” To which the pig replied, “No Thanks, I'd be committed, but you'd only be involved.”</p>
<p><strong>15 Beware the chickens!</strong> Wedding planning is rife with them: parents, siblings, best friends, coworkers.. all can be chickens, even a wedding planner, or venue coordinator. The Product Owner, and the SCRUM team are the Pigs. Totally committed.</p>
<p><strong>16. TIME BOXED DAILY SCRUM</strong></p>
<p>An important part of SCRUM is the daily SCRUM, a 15 minute time boxed meeting. In wedding SCRUM, you don't need to do this every day, maybe 2 or 3 times a week during an active sprint. Its not a working meeting. Its not about the doing.</p>
<p><strong>17. DAILY SCRUM QUESTIONS</strong></p>
<p>It is a reporting meeting during which each member of the team says what they have done since the last meeting, what they plan to do before the next meeting, and any blockers or impediments to the doing.</p>
<p>It is important not to get dragged into the “doing”. Any discussions or decision making happens in followup meetings or working sessions.</p>
<p><strong>18.</strong> <strong>Communication and Transparency</strong></p>
<p>The Daily Scrum is a ritual that fosters communication and transparency which is not only a good thing to develop during wedding planning, but also in marriage.</p>
<p><strong>19. PHOTO</strong></p>
<li>If you follow some of these tips:</li>
<li>Make A List</li>
<li>Prioritize it</li>
<li>Organize it into sprints</li>
<li>Focus on what can be completed within each sprint</li>
<li>communicate regularly with your partner</li>
<p>you too can stay sane while planning your wedding with scrum.</p>
<p>All photos were creative commons licensed, as is this presentation, learn more at</p>
<p><strong>follow me on twitter <a href="" target="_blank">@gregoryheller</a> and <a href="" target="_blank">@hungryseattle</a></strong></p>