Scrum -2

# Scrum Principles

The Scrum framework relies on six basic principles, guidelines that must be followed throughout every project.

Control over the empirical process

Self-organization

Collaboration

Value-based prioritization

Time-boxing

Iterative development

Control over the empirical process#

In Scrum, the empirical process is based on observation of hard evidence and experimentation rather than theory.

There are three main ideas to empirical process control: transparency, inspection, and adaptation.

Self-organization#

As the Scrum process relies on many individuals, self-organization is essential.

Everyone involved is empowered to work independently, and the self-organization principle allows for greater buy-in among all parties, while making it easier to assess individual contributions.

This principle fosters a creative and innovative environment that promotes growth.

Collaboration#

The collaboration principle revolves around three core dimensions: awareness, articulation, and appropriation.

This principle also defines project management as a shared value-creation process that relies on teams working together and interacting to produce the best results.

Value-based prioritization#

The Scrum team must prioritize tasks based on their importance and value to both the end-users and company goals.

This prioritization is a continually evolving process that starts at the beginning of the project and continues until its successful completion.

Time-boxing#

The time-boxing principal schedules and allocates amounts of time for the different activities.

Scrum’s time-boxed elements include-

Sprints-2-4 weeks long

Sprint Planning meetings-1-2 hours for task determination

Daily standupmeetings-15 min for task discussion and monitoring

Sprint Review-1–2 hours evaluation of tasks and release cycles

Sprint Retrospective-Maximum upto3 hours for monthly sprint & less than that

Iterative development#

Scrum project requirements are always evolving and changing, requiring constant adjustment and revision.

This principle emphasizes how to manage these changes more productively and effectively, resulting in products that better serve the customer’s needs.

The software development activities in the Scrum framework must be repeated, revisited, and reworked.