Scrum Methodology

Scrum is an agile method for project management developed by Ken Schwaber. Its goal is to dramatically improve productivity in teams previously paralysed by heavier, process-laden methodologies. Its intended use is for management of software development projects as well as a wrapper to other software development methodologies such as Extreme Programming.

Scrum is characterised by:

A living backlog of prioritised work to be done.
Completion of a largely fixed set of backlog items in a series of short iterations or sprints.
A brief daily meeting (called a scrum), at which progress is explained, upcoming work is described, and obstacles are raised.
A brief planning session in which the backlog items for the sprint will be defined.
A brief heartbeat retrospective, at which all team members reflect about the past sprint.

Scrum is facilitated by a scrum master, whose primary job is to remove impediments to the ability of the team to deliver the sprint goal. The scrum master is not the leader of the team (as they are self-organising) but acts as a productivity buffer between the team and any destabilising influences.

Scrum enables the creation of self-organizing teams by encouraging verbal communication across all team members and across all disciplines that are involved in the project. A key principle of scrum is its recognition that fundamentally empirical challenges cannot be addressed successfully in a traditional "process control" manner. As such, scrum adopts an empirical approach - accepting that the problem cannot be fully understood or defined, focusing instead on maximising the team's ability to respond in an agile manner to emerging challenges.

My name is David Kent and I am a project manager with extensive experience (see my project manager resume) solving business problems through the use of effective design practices, on-time development cycles, and seamless deployment of custom-built web initiatives.

Scrum Methodology

Methodologies