Core Roles in Scrum

An important feature of SCRUM is little number of roles. These Roles have direct influence on the realization of a project. The SCRUM core roles are believed to be accountable for the production of deliverables which meet the acceptance criteria in every sprint which in turn ensures success of the entire project.
The following are the three principal roles in Scrum:

1. The Product Owner- is the voice of the business,
2. The Development Team- that converts ideas into functionality
3. The Scrum Master -who enables the team and process

The Product Owner 
The product owner is regarded to be the one who has far-sightedness of the project and is accountable for accumulating the requirements and needs to understand the value of the project.
The product owner is also responsible for dealing and listing the product backlog. He is also involved in the planning of the release.
A product Owner is typically the project manager or can also be a business analyst who has technical skills. An efficient product owner is expected to have attributes such as ample technical knowledge, needs to have domain expertize and should be easily accessible to the development team.
The Scrum Master
The Scrum Master has his/her focus on the progress of the process and also is known to guide the scrum team.
The Scrum Master is responsible for planning the sprints and prioritizing the sprint backlog. He/she is also involved in managing development process. The Scrum Master also helps in identifying and eliminating the obstacles that is currently hindering the performance of the team
The Scrum Master is responsible for preparing the burn down chart and helps in unblemished communication among one and all in the project. The scrum master enables the group to follow the workflow and ensures that the tasks in the sprints are completed on time. A Scrum Master can either be the team leader or act as the project manager. A scrum master is ideally considered to have a good balance of skills such as technical expertise, problem solver, team player and a problem solver.
The Scrum Team
A Scrum team does not mean the typical development team. A scrum team has its own special capabilities.
Stated below are few features of a Scrum team

1. Cross-functional teams: the team has members from various disciplines in order to help achieve the approved functions. Software engineers, programmers, architects, analysts, system admins, testers etc. could be the members of the teams.
2. Self-organizing teams: the teams take a call on tasks to be done by whom and how to complete the tasks.
3. Business representation:  The business representative is as the voice of the customer, and also the voice of change.
4. Backlog driven: work is done as per the backlog.

The responsibilities of the development team:

• Achieve sprint goals
• To prepare self-made goals
• To organize their time

 To know more click on: http://www.scrumstudy.com/blog/

How will SCRUM benefit me?

Scrum is a hugely beneficial approach to managing software development projects; however, for the team to be successful it must adhere to the core values and principles enshrined in the Agile Manifesto. If Scrum processes are followed properly, then the team will experience the “Enabling Eight.”

1. The team is more likely to produce functional, high-quality software, because the team’s aim is to deliver working software and not just to complete the development activity.
2. An iterative and incremental development approach will enable the team to better cope with the changes that occur when modifications are demanded by stakeholders as the project progresses.
3. Less documentation will enable the team focus more on developing software than on maintaining records.
4. Frequent Sprint reviews as well as practices such as the Product Backlog, Daily Scrum Meetings and Burn-down charts enhance greater visibility and transparency of progress and reduce risks.
5. Regular feedback from the customer will help the development team refine the software by incorporating the suggested changes and delivering high-quality software.
6. Close, face-to-face communication among team members will boost cooperation resulting in better teamwork and in increased productivity.
7. A change-oriented approach will help the team to inspect and adapt the important features, thereby evolving the overall product as the development process proceeds.

Regular Sprint reviews as well as practices such as burn down and velocity will enhance customer satisfaction, which is crucial to any software development activity.

To know more : http://www.scrumstudy.com/blog/how-will-scrum-benefit-me/