A typical 2 week Sprint calendar

When you’re getting started with Scrum, one of the first things you are going to want to do (other than understand the 4 values of the <a href="https://agilemanifesto.org/" rel="noopener ugc nofollow" target="_blank">Agile Manifesto</a>, the <a href="https://agilemanifesto.org/principles.html" rel="noopener ugc nofollow" target="_blank">12 principles behind it</a> and the <a href="https://www.scrum.org/resources/scrum-values-poster" rel="noopener ugc nofollow" target="_blank">5 Scrum core values</a> ) is to set up your Scrum events in your team calendar. So today, let’s explore when you could run them in a typical 2 week Sprint, and the reasons behind that. <h1>Recap of Scrum events</h1> Before we get into when to put the events into a Sprint, here’s a recap of the 4 Scrum events that the Sprint encompasses: <ul> <li>Daily Scrum every day (15 mins max)</li> <li>Sprint Review once per sprint (2 hours max)</li> <li>Sprint Retrospective once per sprint (2 hours max)</li> <li>Sprint Planning once per sprint (4 hours max)</li> </ul> And optionally… <ul> <li>Product Backlog Refinement as a group (1 hour per week)</li> </ul> I find it useful to get some time together as a team to perform group Product Backlog Refinement — but in practice, this is an activity that also happens throughout the Sprint. <a href="https://agilebatman.com/a-typical-2-week-sprint-calendar-60304478651b">Visit Now</a>