Agile Roles and Responsibilities in a Company

Posted By : Inahoto Aye | 28-Jul-2019

Terms used in Agile, Roles, and Responsibilities

Agile is a software development Methodology(Set of methods and Practices followed) to build a software continuously using short sprint so that Product is delivered to the client continuously.

Following are the different terms, Roles, and Responsibility in Agile Methodology:


1. Backlog
2. Product Backlog
3. Sprint
4. Scrum Roles:

  • Project Manager,
  • Product Owner and
  • Scrum Master

 

5. Scrum meetings:

  • Sprint Planning Meetings
  • Daily stand up meetings
  • Sprint Review Meeting
  • Sprint Retrospect Meeting.

 


1.Backlog:

  • List of a requirement to be developed.
  • It has a list of all the requirement from the client which is not Prioritized. 

 


2. Product Backlog:

  • It is a list of Requirement which is Prioritized.
  • Product Owner Prioritizes different task by deciding which feature that needs to be released first on which Sprint according to his Business needs.
  • Sometimes it is also called a User story.

 


3. Sprint:

  • It is a number of days taken to completely develop and Test some set of features that need to be released.
  • It usually 5 to 10 days, 15 to 20 days. Everyone in the team is assigned with different Task and accordingly, all the teams work together to achieve different task assigned.
  • However, the number of days is not fixed and it can be changed according to the complexity and feature.

 

4. Scrum Roles: There are different roles and Responsibilities in Agile Scrum:

a. Product owner:

  • He is Responsible for Prioritizing the Backlog.
  • He will Decide which feature to be released first on which sprint.
  • He is Responsible for Sprint Planning Meeting which is held before new Sprint Starts. 

b.Project Manager:

  • He is responsible for developing the software.
  • He is the architect/design. He tells how to develop the software.
  • He is Responsible to attend Sprint Planning MeetingSprint Review MeetingSprint Retrospect meeting(Closure).

c. Scrum Master:

  • He is Responsible Conducting Daily Stand Up Meetings.
  • He asks the teams mainly 3 basic things(What you did yesterday?, What You are Doing Today? and Any Query/ problems Faced?).
  • He decides who should develop and who should Test.

5. Scrum Meetings: Under Scrum Meetings, we have different types of meeting frequently held-
 

a.Sprint Planning Meetings:

In this Sprint planning Meetings, Product Owner, Project manager, and Scrum Master are Responsible.

  • Product Owner tells what features to be developed first.
  • Project Manager explains the architecture of the software how to develop.
  • Scrum Master decides who will be responsible for Testing and Developing.

b. Daily Stand Up Meetings: Scrum master is responsible for these meetings.

  • Every day for around 15 minutes Scrum Master alone with his teams holds a meeting and ask each member in the team what task they are performing and if there is any issue facing.
  • To keep Updates/track for all the works team member are performing each day this meeting is held.

c. Sprint Review Meeting: This meeting is usually held at the end of each sprint.

  • It is Meeting where all the team members will be present- Project manager, Product Owner, Scrum Master, Developer Team and Testing Team.
  • Test Engineer will give a brief description of the task completed in the sprint.
  • Product Owner review whether the requirement planned were up-to mark or not. The product can tell some changes to be made in the product at this meeting. Scrum Meeting can also be held once changes are implemented.

d.Sprint Retrospect Meeting: This is usually held at the end of every sprint.

  • Project Manager alone with Scrum master, Developer team and Testing Team discuss good approaches and Bad approaches that were followed in the sprint.
  • This meeting is held so that From the Next Sprint Mistakes made does not Repeat and only good approaches are followed.

 

Note: The above terms and methodology are explained as per my experience and understanding working in a company. Any Correction/Comment with respect to this Blog is welcome.

Related Tags

About Author

Author Image
Inahoto Aye

Inahoto Aye has been working with Oodles since February 2018 as Quality Assurance-Software Testing. He has good Domain Knowledge over ERP. His Skills Include:- Manual testing, API Testing, Selenium and Performance testing

Request for Proposal

Name is required

Comment is required

Sending message..