Scrum focuses on defining and executing time-boxed "Sprints" in a specific interval of time, structured to create iterative pieces or features of the finished software product. The entire software development lifecycle is accomplished within each sprint to include requirements analysis, design, coding, implementation, testing, integration, and often, deployment.
The iterations/features are defined and stored in a product backlog. The product backlog is a prioritized queue of business and technical requirements that need to be implemented to create the system or product. The backlog evolves as features are completed, identified, and prioritized. Software iterations are planned, tracked, and executed throughout each sprint using prioritized items from the product backlog. Time-boxed Daily Stand-up meetings, Sprint Reviews, Sprint Retrospectives, and Sprint Planning sessions bridge communications and create transparency between the team and the client.
Daily Standup - A Daily Standup is a meeting time-boxed to a maximum of fifteen minutes and is designed for team members to identify what they completed the previous day, what they are planning for the current day, and any impediments preventing them from accomplishing their tasks.
Sprint Review - A Sprint Review meeting is held at the conclusion of each sprint with the purpose of reviewing the work accomplished in the sprint and, where appropriate, demonstrate the completed piece of software. The entire team, Product Owner, user community, and client staff attend this review with the contractor Project Manager and Scrum Master as moderators.
Sprint Retrospective - A Sprint Retrospective session is also held at the Sprint Review to identify areas for improvement and develop action plans or process changes based on issues encountered during the sprint. This typically includes items that the team should start doing, stop doing, and continue doing from a process perspective. This will provide continuous process improvement for the team and the client.
Sprint Planning - A Sprint Planning session occurs prior to the start of a sprint with the entire team and the Product Owner in attendance. The Product Owner reviews the prioritized items in the Product Backlog and presents each requirement identified for the sprint. The team discusses the approach for splitting apart the requirements into user stories and creates a Sprint Backlog. Each user story will be dissected in detail to identify the specific tasks/features necessary for completing the requirement and establishes the Definition of Done. The outcome of this planning discussion will be moderated by the Product Owner and the Scrum Master and documented by the Scrum Master.