Scrum

What is Scrum?

It is an framework within which individuals can address complex problems, by continuous products and service being delivered maintaining highest possible value, being productive and creative while defining the solutions.

Scrum is

• Simple to Understand
• Difficult to Master
• Lightweight

Scrum is a process framework, that is being used to manage work on comples products since early 1990s. Scrum is not a proces, technique or definitive method, rather than a framework within which once can employ their own various processes, and technique based on their business needs. This framwork makes clear the relative efficacy of product management, and work techniques so that their is an continuous, never ending improvements to the teams, products, and the working place.

Why Scrum should be use?

Scrum has proven itself in industry since long, as it has helped

1. Develop Products and Enhancements
2. Release Products and Enhancements as freqeuntly as possible (per day release)
3. Sustain and Renew Products

Scrum is proved very effective in iterative and incremental transfer. Scrum is nowwidely used for not only just products but also services, and the management of the parent organization.

Essence of Scrum is a small team of highly flexible and adaptive individuals. These strengths continue operating in single, several, many, and networks if teams that develo, release, operate and sustain the work and work products of thousands of people. They collaborate and interoperate through sophisticated development architecture and target release environments.

Pillars of Scrum

Scrum employs an iterative, incremental approach to optimize predictability and control risk. Important pillars of an scrum are as follows

1. Transparency
2. Inspection
3. Adaption

Transparency

Significant aspects of the process must be visible to those responsible for the outcome. Transparency requires those aspects by defined by a common standard so observers share a common understanding of what is being seen.

In simple words - A common language referring to the process must be shared by all participants and those performing the work and those inspecting the resulting increement must share a common definition of "Done"

Inspection

Scrum users must frequently inspect Scrum artifacts and progress towards a Sprint Goal to detect undesirable variances. Their inspection should not be so frequent that inspection gets in the way of work. Inspections are always beneficial when diligently performed by skilled inspectors at the point of work.

Adaption

If an inspector determines that one or more aspects of a process deviate outside acceptable limits, and that the resulting product will be unacceptable, the process or the material being processed must be adjusted. An adjustment must be made as soon as possible to minimize further deviation.

Main events involved here in progress

1. Sprint Planning
2. Daily Scrum
3. Sprint Review
4. Sprint Retrospective

Scrum Values

1. Respect - treat people with respect so that team cultivate an engaged productive and humane environment for all.
2. Commitment - Team is empowered to make realistic commitment, we are fully invested in outcome.
3. Focus - Team focus on only few things at a time, we deliver the most value in short time.
4. Openness - Team individuals are open for their work, their progress, and the things coming up next, also around the ideas of others, so that all are involved in the decision making, which results in Best Decision coming out from the open ideas.
5. Courage - Everyone in team must support each other in doing the right thing na din taking informed risk so that we learn and improve on our delivery.

When the values of commitment, courage, openness, focus, and respect are embodied and lived by the Scrum team, the pillars of Scrum - Transparency, Inspection, and Adaption come to life and build trust for everyone. The Scrum Team members learn and explore those values as they work with the Scrum events, roles and artifacts.

** Above article help anyone to just get the basic understanding of Scrum and process. Details around the Scrum Teams, Events, and Pillars will be continued in my next articles.