Agile, Blog 2, CS 200W

The Agile Team and the backlog

The Agile Team and what is a Backlog? What are they for and why are they important?

This blog continues on the last week’s blog about introducing Agile to newcomers to the practice. The focus this week is on 2 things – The agile team and the artifacts that they work on, namely “backlogs”.

Agile Team

Agile team is a self contained team that can by itself complete a user story in the backlog. Let’s take the example of “Scrum” which is a popular Agile framework. In scrum, there could be dependencies with external teams. But it is up to the Scrum Master to resolve these dependencies. Otherwise, the team would flag such User Stories as having ‘impediments’ and move on to the next one.

Typically a Scrum team consists of the following roles

  • Scrum Master – Person who is in charge of the sprints
  • Product Owner – Person who represents the stakeholders
  • Team – Consists of different people who collectively have skills to complete tasks in the backlog.

Below is a short summary of responsibilities for each role.

Scrum Master:

  • Manages 1 sprint at a time
  • Facilitates Sprint Planning, Review & Retrospective
  • Finds and works to remove roadblocks
  • Helps to motivate the team and keep them excited
  • Protects team from outside distractions
  • Facilitates communication between roles for every aspect of the project
  • Responsible for keeping release/project information consolidated, organized and up to date
  • Drives the cross-functional team at all levels
  • Responsible for throughput
  • Drives the execution of sprint items

Product Owner:

  • Responsible for market, business case, and competitive analysis
  • Responsible for long and short term product vision
  • Responsible for ROI and Net Profit
  • Prioritizes features for releases based upon expected ROI
  • Writes Acceptance Criteria
  • Writes user stories
  • Makes tradeoff decisions between scope and schedule


  • Responsible for implementation of the backlog items as per the acceptance criteria
  • The team could contain people with specialized skills
    • Architect to define the design and ensure that best practices are followed.
    • Developers to develop and unit test the features
    • Quality engineers to test the features and ensure that they have been done as per the acceptance criteria
    • User Experience Designers to take care of the human interaction perspective
    • ..etc.


The product backlog in Scrum is a list of features that are desired for a product at that point in time. Features are short descriptions of the functionality that is needed and these are prioritized. They could contain new features, bugs, technical debt..etc. Typically a team picks few features from the top of the list during ‘Sprint Grooming’ sessions. During ‘Sprint Planning’, the product owner shows up with the prioritized list and the team take these, estimates and locks the features that could be accomplished in a sprint (called ‘Sprint backlog’).



4 thoughts on “The Agile Team and the backlog

  1. Good explanation of every role in a scrum team i.e Scrum master, Product owner and the team. Diagrams plays a major role in the blog posts.I liked the detailed explanation of each role in a team which has given me an immense knowledge regarding the Agile. Explanation is regarding backlog is informative. I read the entire blog post in which I haven’t seen any images. With the help of images, a naive user can visualize the scrum team and also user can understand the importance of having Agile software methodology in a company. It would be great if you can add some images or charts about agile team. Images make your blog more informative. Overall, great post. Thanks a lot for the detailed explanation.

    Liked by 1 person

  2. Your blog post serves as a great reference to the different roles in an Agile team. If I ever get assigned to the role of Scrum Master, I can just look up your post and I will immediately know what to do, which is great. I also liked your definition of team, it highlights the fact that an Agile team is not only composed of developers, but of every person that can bring a project to reality. One thing that I would like to see clarified in your blog post though, is the fact that the backlog is composed of user stories, not just features.


  3. You have very clearly defined the agile team members and what are their roles. The point wise distinction of actions expected from a team member performing a particular role whether it’s ScrumMaster or Product Owner or team is really good. I like the to-the-point explanation of product backlog. With just one line the reader can understand what the backlog is. One thing thats missing is some image or graph but overall a nice blog.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s