Get certified - Transform your world of work today

Close

Agile Manifesto Principles Behind Scrum Activities

26 April 2017


We are aware of the fact that there are 12 principles behind Agile Manifesto. Here is a simple way to understand and practice these principles. We can do this by correlating the principles to Scrum activities.

In the Scrum framework, there are specific activities that can be stated as follows:
  1. Establish and maintain the customer relationship.
  2. Create and manage the product backlog.
  3. Hold sprint planning.
  4. Practice the Daily Scrum.
  5. Hold sprint reviews.
  6. Hold sprint retrospectives.
We now uncover the principles behind these activities and associate them.
 

1. Establish and maintain the customer relationship

image-1.jpg

In order to establish the customer relationship, we have to present something that the customer desires. And, to maintain a persistent customer relationship, we have to meet the customer’s expectations of the quality, cost, and meeting the schedule of the deliverables. The business and technical teams work together to remove gaps in each other’s perceptions of the product vision and to be on the same page.

Principles

image-2.jpg
 image-3.jpg


2. Create and manage the product backlog

image-4.jpg

The product owner works with the business to create the product backlog with requirements. In order to identify the high-priority items in the product backlog, not all the requirements should be treated with equal importance. With due diligence and input from the business, the product backlog gets prioritized by the product owner. The amount of work to be done is minimized when the team has settled on a small list of items that have high priority. The product backlog is visited regularly to add new items and reprioritize existing items according to changing market conditions or business needs.

Principles

image-5.jpg
image-6.jpg 

3. Hold sprint planning

image-7.jpg

The development team analyzes the existing architecture and design to determine whether they need to tweak the existing architecture or design to suit the requirements or to create a new one. Based on the conclusion, they estimate the amount of work that needs to be done to convert the requirements into working software. The necessary environment and support have to be provisioned to the development team to let them work toward the sprint goal.


Principles

image-8.jpg
image-9.jpg 
image-10.jpg


4. Practice the Daily Scrum

image-11.jpg
The Daily Scrum is administered by and for the development team, and they are expected to participate regardless of the presence or absence of ScrumMaster or product owner. They should adhere to the 15-minute time limit and plan their discussion accordingly. Predominantly, people have the ability to read a face effectively and get the feel of atmosphere around rather than elicit the situation solely from the tone of the individual's voice. Hence, face-to-face conversation is encouraged, and it conserves time as the exchange of information via emails or telecommunication requires an investment of time and effort.

Principles


image-12.jpg
 

5. Hold sprint reviews

image-13.jpg

The stakeholders review the working software and provide their feedback. This could be acceptance or amendment or rejection of the deliverable. The amendment could be an improvement or complete rework. Regardless of the essence of the assessment, it has to be accepted by the Scrum Team, as the future sprints' work depends on it. Ultimately, the recommendations get incorporated into the product backlog and prioritized.

Principles

IMAGE-14.jpg
image-15.jpg
 
image-16.jpg


6. Hold sprint retrospectives

image-17.jpg
The Scrum Team always works toward betterment in everything they do. But to err is human, so the best thing to do is to learn from mistakes. The team introspects their work for the sprint and identifies the causes of failure and determines solutions. They employ the solutions for future sprints as required.

Principles

IMAge-18.jpg

 

Opinions represent those of the author and not of Scrum Alliance. The sharing of member-contributed content on this site does not imply endorsement of specific Scrum methods or practices beyond those taught by Scrum Alliance Certified Trainers and Coaches.



Article Rating

Current rating: 4.2 (5 ratings)

Comments

Nagarajendra Kumar Tippa, CSP,CSM, 4/28/2017 3:08:02 AM
Good explanation of the agile principles.

You must Login or Signup to comment.

The community welcomes feedback that is constructive and supportive, in the spirit of better understanding and implementation of Scrum.

 

Newsletter Sign-Up

Subscribe