Scrum : The Actual Agile Methodology Manifesto

source: http://cdn.exploringscrum.com/wp-content/uploads/2011/08/scrum-glossary-agile-terms-300x160.png

What is Scrum?

Scrum emphasizes more on “empirical process control” which is real world progress of project than best guess or forecast progress of the project for future releases. . In Scrum, projects are divided into crisp work shots, known as sprints, which are typically one week, two weeks, or three weeks in duration. At the finish of every sprint, stakeholders and team members meet to assess the progress of a project and plan next steps. This helps a project’s direction to be adjusted or reoriented based on completed work and its scope(necessity) , not on speculations.

The USP of SCRUM amongst managers and developers is ongoing assessment of completed work .SCRUM became more popular as it comes with a simple set of roles, responsibilities, and meetings that never change. If Scrum’s capacity for adaption and flexibility makes it an appealing option, the stability of its practices give teams something to lean on when development gets chaotic.

The Roles of Scrum

Scrum has three roles:  Product owner, Scrum master, and team member.

• Product Owner: He/She is responsible for communicating the vision of the product from customer's interests to the development team. Because the Product Owner has the most authority of the three roles and also also the role with the most responsibility. With growing responsibility and higher authority Product owner must strike with balanced involvement as he/she shouldn't micro manage at the same time should always be on their toes to answer any questions from the team.

• ScrumMaster: The ScrumMaster acts as a facilitator for the Product Owner and the team but nowhere involved in management of team.  Instead, he or she works to remove any impediments that are obstructing the team from achieving its sprint goals. In short, this role helps the team remain creative and productive, while making sure its successes are visible to the Product Owner. The ScrumMaster also works as an adviser to the Product owner about how to maximize productivity from the team.
• Team Member: This team is responsible for executing the work. Ideally, teams consist of seven cross-functional members, plus or minus two individuals. For software projects, a typical team includes a mix of software engineers, architects, programmers, analysts, QA experts, testers, and UI designers. Each sprint, the team is responsible for determining how it will accomplish the work to be completed. This grants teams a great deal of independence, but, similar to the Product Owner’s situation, that freedom is accompanied by a responsibility to meet the goals of the sprint.

This is my experience and insight on SCRUM : An Agile Methodology ! Happy SCRUM.