Scrum is the most commonly used agile process for projects specifically more prominent for software development. As a product development framework scrum is applicable for any type of projects. Whether it is minimal project requirements at the start of the project or complex requirement which keeps changing throughout the life of the project or even aggressive timelines to build the product with the least time to market strategy, scrum is very effective.
Scrum projects move forward in a series of iterations and the iterations are usually in the length of 1 to 6 weeks. These iterations are also called Sprints. An ideal sprint is usually 4 weeks long.
Typically scrum is a small team consisting of 7 – 10 members and this is when the team is most effective. But is some case the team can be as low as 2 and as high as 12. This does not mean scrum cannot be applied for larger projects. It can be easily scaled up for huge projects scaling into hundreds. Everyone on the project team works together to complete the work accepted in the sprint backlog for the particular sprint.
In the sprint planning meeting the team picks up a piece of work based on the most high valued features determined by the product owner. Everyone in the scrum development team works together to complete the work collectively to completed within the sprint, which they have committed in the sprint planning meeting. The scrum team is self-organised and is not monitored by anyone. The other roles in the scrum team are product owner and scrum master.
Scrum Master is the person responsible for facilitation of all the necessary things within the team. Scrum Master follows what is known as Servant Leadership, he only facilitates scrum within the team and ensures scrum is followed, he is not the manager of the team nor does his pushes work to the team. He is only there to help the team use the scrum process, by removing impediments to the project’s progress and also protects the team from outside interference.
Product owner is the one responsible for the project and is representing the stakeholders and users of the project. He is commonly known as Voice of the Customer. As there is frequent interaction with the stakeholders and the scrum team for outputs at the end of each iteration, the product owner forms the liasion between the stakeholders and the team. Unlike traditional projects, the product owner in scrum is involved throughout the life of the project. And typically spends around 7-10% of his time in grooming the product backlog.
