Ken Schwaber and Jeff Sutherland have posted an update to the Scrum Guide this year. Here is a link to the summary of the changes. In case you prefer, here is a summary of the changes:
1. The team doing the work is now called the ‘Development Team‘, and all members of the team are called Developers whether their expertise is in programming, testing, UX design, technical writing, etc. This is to emphasize that the team works together to ‘develop’ the software.
2. The team no longer ‘commits‘ to accomplishing the sprint goals, they ‘forecast‘ what they will complete and the expectation is that the plan will adapt as they learn more. The main reason for this is at times stakeholders have engaged in committment bashing, penalizing the team for breaking commitments even when the circumstances were beyond the team’s control. This is an acknowledgement that it’s nearly impossible to predict a 100% accurate plan until the team has enough information – which is usually when they are doing the actual work. We can, however, forecast accurately enough to make a plan with flexibility baked in.
3. Scrum doesn’t require use of a burndown chart specifically, only that the amount of work remaining in a sprint is summed and known daily, and trending towards completion is maintained throughout the sprint.
4. Release planning is valuable but isn’t required; it depends on your circumstances.
5. The Sprint Backlog is the Product Backlog items selected for the sprint plus the plan for delivering those. Here is a diagram from scrum.org which illustrates what is considered the sprint backlog:
6. The product backlog is now ‘ordered‘ instead of ‘prioritized‘; this is to emphasize that there are many factors that go into the order of the backlog including ROI but also logical order, dependencies, gaining knowledge, and other factors unique to the situation.
Edit: Here is a link to the Scrum Guide