What is scrum? It's a special approach to software development. Instead of a full process, people who use this process work within a framework. So there is a much less formal approach to things in the sense that a very specific plan is excluded in favor of leaving things up to the software development team. And the reason why this is done is because the team will have a better idea of what sort of options are best used for solving a particular type of problem.
This sort of process is in contrast to sprint planning, which is a type of approach that is based around the goal of reaching a specific desired outcome. Instead, the scrum system works through a self-organizing, cross-functional team, which means that the goal is greatly influenced by the team and not necessarily by any specific goal. It also involves putting together feasible ideas and then implementing them. To carry out this process, the entire team will need to assign two positions: a ScrumMaster and a product owner. Although the approach tends to be somewhat less rigid, it still requires a certain level of control and organization.
The ScrumMaster's purpose is to act as a coach, essentially helping each member of the team figure out how they can best contribute to the framework. On the other hand, the product owner represents the target consumer and basically guides the team into creating a product which fits well with the demands of the business as well as its target consumers.
Also, scrum projects do not define progress in terms of a straight line but instead as a series of sprints which are timeboxed iterations for a given period of time, typically a month or a few weeks. At the start of each period, team members will divide the tasks among themselves. The goal is to deliver a particular number of features within a given period of time. Once they have carried out the necessary tasks, the features submitted by each member of the team will then be coded and tested. After that, the team members will then coordinate on how to best integrate these various features onto the system.
After the initial tests and evaluations, the new features are then reviewed by the team, the ScrumMaster and product owner. This is done at the end of the scrum process, and it also includes demonstrations of what the new features can do for the product owner or any other person who is interested in the project.
