title: How do you structure a development sprint?
body: <p>So I have a backlog of features and we are about to get started on a sizable project.  I am working on defining the structure of our sprints and I'm interested in the communities feedback.</p>
  
  <p>What I'm thinking is:</p>
  
  <ul>
  <li>One day sprint planning
  
  <ul>
  <li>Fill the backlog and figure out what each dev will go after this sprint</li>
  </ul></li>
  <li>Three weeks of development
  
  <ul>
  <li>GO! GO! GO!</li>
  </ul></li>
  <li>Daily stand up meeting
  
  <ul>
  <li>Check to see if anyone needs help or feels off track</li>
  </ul></li>
  <li>Two days of sprint review
  
  <ul>
  <li>code reviews happen here, stakeholder presentations</li>
  </ul></li>
  <li>One day sprint retrospective
  
  <ul>
  <li>what did we get done in the last sprint? how can we do better next time?</li>
  </ul></li>
  </ul>
  
  <p>Sprints should always end on a Tuesday (to avoid too much weekend stress).</p>
  
  <p>Anything else?  There is obviously more to agile than this. I want to provide the team with a simple outline of how we are going to operate as we get this project started.</p>