As LevelTen has been transitioning from a waterfall model to Agile Methodology, we’ve not only learned a whole different viewpoint on process, but a new vocabulary to go along with it. The terms "daily scrum" and "sprint" are thrown around so much in the office, that we end up using these new terms around our clients and friends who then look at us like we are speaking a foreign language. I'd like to share a few of these concepts, but first, a short overview.

In the Scrum process, the Sprint Retrospective Meeting follows the Sprint review meeting. At this time-boxed 3 hour meeting, the ScrumMaster encourages the Team to revise, within the Scrum process framework and practices, its development processes to make it more effective and enjoyable for the next Sprint.

Further Reading

In the Scrum process, the Sprint Review Meeting is held at the end of each Sprint cycle. It is a 4-hour time boxed meeting at which the Team presents what was developed during the Sprint to the Product Owner and any other stakeholders who want to attend. This informal meeting at which the functionality is presented is intended to bring people together and help them collaboratively determine what the Team should do next.

Further Reading

In the Scrum process, the Sprint Backlog defines the work, or tasks, that a Team defines for turning the Product Backlog into an increment of potentially shippable product functionality.

Tasks should be divided so that each takes roughly 4 to 16 hours to finish. Tasks longer then 4 to 16 hours are merely placeholders for tasks that haven't yet been appropriately defined. Only the Team can change the Sprint Backlog.

Further Reading

In the Scrum process, the Sprint is the name for the process where work is accomplished. A Sprint is a 30-day iteration in which the Team works to complete new functionality from the Product Backlog. Each Sprint is initiated with a Sprint Planning Meeting and ends with a Sprint Review Meeting.

Further Reading

In the Scrum process, the Sprint Planning Meeting initiates each Sprint cycle. Sprint planning meetings cannot last more then 8 hours, and are broken up into two 4 hour sessions. The first 4 hours are spent with the Product Owner who presents the highest priority product backlog to the Team. During the second 4 hours, the Team plans out the next Sprint. When the second 4 hour meeting commences, time begins to advance for the current Sprint session.

Further Reading