The scrum framework is in actual fact quite simple.

There are only 4 meetings and 6 artifacts, although I add an extra one as I think it is vital to helping the team work. If you are not doing these meetings or maintaining these artifacts then you are not doing Scrum. Missing artifacts and meetings will cause the loss of all benefits that would otherwise be gained. Scrum is built upon delivering working software within a 2-4 week time frame. Scrum meetings

Sprint Planning Takes place at the start of each sprint. The team meets with the product owner and discusses the next set of highest priority items from the product backlog. The result of this meeting is a sprint backlog which contains the stories broken down into tasks with estimates for each task. The team also agrees with the product owner the commitment for the sprint and a sprint goal. This commitment is generally based on the teams known velocity. Daily scrum The team meet for a maximum of 15 minutes per day with the scrum master around the team task board. Team members update the task board, align with each other on tasks and answer 3 questions. What have you done in the last 24 hours, what will you do in the next 24 hours and what is getting in your way. Sprint Review or demo Takes place at the end of each sprint. The team meets with the product owner and demonstrates the working software produced during that sprint. This allows the team and product owner to inspect and adapt the product. Retrospective Occurs at the end of each sprint. The team meets with the scrum master and looks at want went well and what can be improved. Individual actions are taken to improve the process. This allows the team and scrum master to inspect and adapt the process.

Lets take a look at the scrum artifacts:

Vision Statement Every project should have a vision. It is vital for the team and any one else involved to know what they are aiming for. It should be simple and straight to the point providing a description of the product to be built. Product Backlog This is the list of all the requirements known about for the system whether they be functional or non-functional. This list must be prioritized and it describes the what of the system. Requirements are often described using a technique called user stories. The product back log is always in flux and can be changed and re-prioritized as the project needs. Sprint Goal The Vision for the current sprint. This is an agreement between the team and the product owner and helps the team to meet the objectives for the sprint. Sprint Backlog The team break the product backlog items down into the tasks they need to do to complete the backlog item. This is the how of the system.

Impediments All things that are slowing down or stopping the development process are identified and prioritized. This can be at daily scrums or in team retrospectives. These impediments can be team or organizational. Sprint Burndown A visual representation of the teams progress for the sprint. This allows the team, scrum master and other interested parties to see the current progress. Task Board Not technically a scrum artifact but I believe that it is vital. It allows the team to be transparent with its progress. It creates a focal point for the team; daily scrums can be held around it and it aides and focuses communication. You can also expand it with your impediments and sprint burndown charts.

The diagram below puts into context the scrum flow