These tutorial videos are a great way to learn about Kerika. What we WANT to do is move to a true 2-week sprint model in which all development and QA happens within the 2-week timebox. For us it's mostly about quality and working towards continuous integration (we would release every 2 weeks instead of every 3 weeks). Again, many reasons to do this which I won't get into here. Some go as short as a week. Each Sprint is 2 weeks long: that that works well for us; other folks might find that 3 weeks or 4 weeks i better. Pick what works for you. Week 7. Model for 2-week Sprints (Agile Scrum) TIP. The new sprint then suffers. The important thing is to make sure that the Product Backlog is refined in a timely manner so that Sprint Planning can occur without impediment. Back to videos. As an information radiator, I print it out and hang it on the wall (usually in multiple places) You can see the 2-week sprint schedule above and the 3-week schedule is below. As a visual reminder to stakeholders of the upcoming sprint and a reminder of when the next backlog refinement and sprint review will take place. Use Sprint 3's output to do Sprint 4. During the Sprint. Thanks, I am done. So, a one-week Sprint will have two hours of Sprint Planning; a two-week Sprint will have four hours, and so on. The sprint begins with Planning and ends with Review & Retrospective. TIP. Kerika’s model for 2-week Sprints. Navigate on the page. Week 8. A Typical Sprint, Play-By-Play Ian Mitchell Ian ... For most teams, half an hour a day may be adequate although some may prefer to spend an hour or two a couple of times a week. However, Sprint meetings should scale linearly with the length of a Sprint. While the first Scrum team used a month long Sprint, most teams now work in one or two-week cycles. The Sprint contains all the elements of Scrum. People say that Sprint meetings are too much overhead for a one-week Sprint. Today, most Teams new to Scrum pick two-week Sprints. It is a contiguous process with one iteration immediately following the next without pause. ... Use Sprint 2's output to do Sprint 3. Don't show this again. Each Sprint begins with Sprint Planning, where the Scrum Team gets together with the Product Owner to decide which cards will be pull from our main Product Backlog into the Sprint Backlog.