Scrum in a very brief nutshell – a set of points along with a brief description

I have written several articles about Scrum, none of them very long or like an essay, but this article will probably be the shortest, since it is more like a slide with a few points (and optional explanation) next to the slide points. Here goes:
- Have a prioritized list of requirements: This is essentially about putting all your requirements down in point form (and not trying to detail out all the requirements right now), and then prioritizing them so that everyone knows which are the most important points
- Plan a time for when to show your work: In essence, this is a demo. A demo of your work set for certain dates (these dates being at specific intervals), to show to your stakeholders and as a form of demonstration of completion by the team
- Invite people for this showing of the work: Showing off the work is not complete till you are sure that all the stakeholders are invited and can come and see. These stakeholders include the product owner (representative of the product management), senior management, and of course, the team members
- Agree to deliver a set of requirements: This is the hard part, since it includes the whole set of processes to take the overall set of requirements, get the team to understand them, break down those requirements into a set of features, do planning poker to help in estimation of those features and prepare a Sprint backlog for getting the list of features for the current Sprint
- Actually do the work required to complete these requirements: This is one of the most time taking part of the Scrum cycle, since this is the time when the team actually develops and tests the requirements, with monitoring of the work done through the breakdown charts, and also work through the progress through the use of the Daily Scrum
- Do the actual showing of the work: This is the actual summary of the work done, and includes getting the team together for the introspection / post-mortem, and having the demo to the stakeholders at the end of the cycle, so that people can comment as to whether the work is happening in the desired direction
- Repeat: All the above (except for the first point) is part of one of the cycles of Scrum, and you need to do these cycles through the project development cycle (with the length of each cycle varying between 1 week to 2 months or so).

Ad: