In Software industry, we are always confused as to where do we look for resources, when reading up on any given topic. I have been reading and discussing SCRUM with many people, and this is the most closest, and precise information I have read. Sharing it over here for my readers.
Introduction to Scrum
Scrum is an agile project management methodology or framework used primarily for software development projects with the goal of delivering new software capability every 2-4 weeks. It is one of the approaches that influenced the Agile Manifesto, which articulates a set of values and principles to guide decisions on how to develop higher-quality software faster.
Who Uses Scrum Methodology?
Scrum is widely used by software development teams. In fact it’s the most popular agile methodology. According to the 2013 State of Agile™ report, 73% of software teams use Scrum or a Scrum hybrid. However, Scrum has spread to other business functions including IT and marketing where there are projects that must move forward in the presence of complexity and ambiguity. Leadership teams are also basing their agile management practices on Scrum, often combining it with lean and Kanban practices (subgroups of agile project management).
Are Scrum and Agile the Same Thing?
No. Scrum is a sub-group of agile:
- Agile is a set of values and principles that describe a group’s day-to-day interactions and activities. Agile itself is not prescriptive or specific.
- Scrum follows the values and principles of agile, but includes further definitions and specifications, especially regarding certain software development practices.
Although developed for agile software development, agile Scrum became the preferred framework for agile project management in general and is sometimes simply referred to as Scrum project management or Scrum development.
Benefits Received from Scrum
Organizations that have adopted agile Scrum have experienced:
- Higher productivity
- Better-quality products
- Reduced time to market
- Improved stakeholder satisfaction
- Better team dynamics
- Happier employees
What Makes the Scrum Methodology Special?
Scrum addresses complexity in work by making information transparent, so that people can inspect and adapt based on current conditions, rather than predicted conditions. This allows teams to address the common pitfalls of a waterfall development process: chaos resulting from constantly changing requirements; underestimation of time, resources and cost; compromises on software quality; and inaccurate progress reporting. Transparency of common terms and standards is required in Scrum development to ensure that what is being delivered is what was expected. Frequent inspection ensures progress and detects variances early on so that adjustments can be made quickly. The most common Scrum events for inspection and adaptation are: Sprint Planning, Daily Scrum or “Stand Up”, Sprint Review, and Sprint Retrospective (see Scrum Events below).
Challenges of Scrum and Other Agile Methodologies
Most enterprises first transition individual teams to agile before they “scale” to the rest of the organization. Scaling agile is not easy, which has recently prompted new frameworks to emerge, such as the Scaled Agile Framework® and Disciplined Agile Delivery (DAD) This popularity has made Scrum a significant piece of many agile application lifecycle management (agile ALM) initiatives.
Components of Agile Scrum
The Scrum methodology is defined by team roles, events (ceremonies), artifacts, and rules.
The Scrum Team
Scrum teams are typically composed of 7 +/- 2 members and have no team leader to delegate tasks or decide how a problem is solved. The team as a unit decides how to address issues and solve problems. Each member of the Scrum team is an integral part of the solution and is expected to carry a product from inception to completion.
There are three key roles in a Scrum team:
The Product Owner
The Product Owner is the project’s key stakeholder – usually an internal or external customer, or a spokesperson for the customer. There is only one Product Owner who conveys the overall mission and vision of the product which the team is building. The Product Owner is ultimately accountable for managing the product backlog and accepting completed increments of work.
The ScrumMaster is the servant leader to the Product Owner, Development Team and Organization. With no hierarchial authority over the team but rather more of a facilitator, the ScrumMaster ensures that the team adheres to Scrum theory, practices, and rules. The ScrumMaster protects the team by doing anything possible to help the team perform at the highest level. This may include removing impediments, facilitating meetings, and helping the Product Owner groom the backlog.
The Development Team
The Development Team is a self-organizing, cross-functional group armed with all of the skills to deliver shippable increments at the completion of each sprint. Scrum broadens the definition of the term “developer” beyond programmers to include anyone who participates in the creation of the delivered increment. There are no titles in the Development Team and no one, including the ScrumMaster, tells the Development Team how to turn product backlog items into potentially shippable increments
Scrum Events (Ceremonies)
A sprint is a time-boxed period during which specific work is completed and made ready for review. Sprints are usually 2-4 weeks long but can be as short as one week.
Sprint Planning team meetings are time-boxed events that determine which product backlog items will be delivered and how the work will be achieved.
The Daily Stand-up
The Daily Stand-up is a short communication meeting (no more than 15 minutes) in which each team member quickly and transparently covers progress since the last stand-up, planned work before the next meeting, and any impediments that may be blocking his or her progress.
The Sprint Review
The Sprint Review is the “show-and-tell” or demonstration event for the team to present the work completed during the sprint. The Product Owner checks the work against pre-defined acceptance criteria and either accepts or rejects the work. The stakeholders or clients give feedback to ensure that the delivered increment met the business need.
The Retrospective, or Retro, is the final team meeting in the Sprint to determine what went well, what didn’t go well, and how the team can improve in the next Sprint. Attended by the team and the ScrumMaster, the Retrospective is an important opportunity for the team to focus on its overall performance and identify strategies for continuous improvement on its processes.
The product backlog is the single most important document that outlines every requirement for a system, project or product. The product backlog can be thought of as a to-do list consisting of work items, each of which produces a deliverable with business value. Backlog items are ordered in terms of business value by the Product Owner.
A sprint backlog is the specific list of items taken from the product backlog which are to be completed in a sprint.
An Increment is the sum of all product backlog items that have been completed since the last software release. While it is up to the Product Owner to decide on when an increment is released, it is the team’s responsibility to make sure everything that is included in an increment is ready to be released. This is also referred to as the Potentially Shippable Increment (PSI).
The rules of agile Scrum should be completely up to the team and governed by what works best for their processes. The best agile coaches will tell teams to start with the basic scrum events listed above and then inspect and adapt based on your team’s unique needs so there is continuous improvement in the way teams work together.
To get started with agile Scrum, it is not uncommon for an individual Scrum team to use simple Scrum tools like a whiteboard, sticky notes, or a spreadsheet to manage the product backlog and the progress of the sprint backlog items in each sprint.
Scaling agile practices to the rest of the organization is undoubtedly more complicated: The more teams use Scrum within an organization or are geographically dispersed, the more cumbersome simple tools like whiteboards, sticky notes, and spreadsheets become.
Taking Agile to the Next Level
VersionOne addresses the challenge of scaling agile practices like Scrum by providing an all-in-one agile project management platform that can be used not only by individual teams, but also by distributed enterprises who have adopted a scaled agile framework. The VersionOne agile ALM platform is a centralized environment for stakeholders at the team, program and portfolio levels to plan, track and report on software delivery regardless of location.