Agile | Agile Development Process

Basically, there are five types of meeting in the Agile Development Process. These meetings get started after kickoff meeting of the Project.

These meetings are mentioned below:

Backlog Creation/Backlog Refinement

Backlog Creation: Once all the requirements being analyzed and entire project split into the various modules, all the requirements get converted into the user-stories. These user stories are collectively known as ‘Product Backlog‘.

Backlog Refinement: The process of extracting the requirements(user stories) from the Product Backlog, for a particular Sprint. These requirements would be based on the priority and complexity of the Product. This Process is required before starting each Sprint.

Ownership: Product Owner, Scrum Master, Business Analyst

Sprint Planning

Sprint: A Sprint is a predefined time duration in which a set of the task should be completed. After completion of each Sprint, a working application should get ready for client release.

Meeting Agenda: Extracting prioritized user stories from product backlog which will be implemented in the next Sprint is called ‘Sprint Backlog‘. The process of analyzing and prioritize the requirements is called the Sprint Planning. It also includes the analysis of requirements, resource requirement, skill requirement, effort estimation, team size etc.

Ownership: Product Owner, Scrum Master, Business Analyst, Team Leads

Scrum Meeting/Daily Standup

Scrum: Scrum is the team who are responsible for successful execution of the Sprint with quality and in a given time frame. Scrum team would be lead by Scrum Master.

Scrum Master: A Scrum Master is a person who helps the Scrum Team to achieve their goals on time and with quality. Scrum Master is responsible that Scrum Team is fully functional.

Daily Standup: Sometimes it is called ‘Scrum Meeting’.  This meeting has been lead by the Scrum Master on daily basis to keep track the status of the Project. The duration of the meeting depends on the size of the Scrum Team. Idol time duration for daily standup has been set 15 minutes.

Meeting Agenda: In this meeting, the focus will be on following points and asked from each team member:

  • What he(she) done yesterday?
  • What he(she) will do today?
  • Is there any impediment? [Note: Impediment is the blocker issue whether it is related to the technical issue, any functional defect, skill requirement, resource requirement etc.]

Ownership: Scrum Master, Scrum Team, Product Owner(Optional)

Sprint Review Meeting

Meeting Agenda: At the end of the Sprint, Sprint Review meeting get started. This meeting would be lead by Product Owner or Scrum Master. This meeting is held to make sure that all the requirements have been implemented according to the Sprint Backlog and now build is ready for Customer Release for review. Product Owner can accept or Reject the build as per the quality of the build.

Ownership: Product Owner, Scrum Master, Scrum Team, Business Analyst

Sprint Retrospective Meeting

Meeting Agenda: Once the build has been delivered to the Customer for review, Sprint Retrospective Meeting will be held. In this meeting, the entire project team is involved and each member shares his(her) feedback or experience with the team to improve the development process and quality of the Product. This requires a deep level of the brainstorming.

Ownership: Product Owner, Scrum Master, Scrum Team, Business Analyst

Agile Meetings
Agile Meetings
Roles and Responsibility
  • Product Owner(PO):
    • PO is the person who owns the product. In some cases, Project Manager plays the role of PO. Responsibilities of a PO is mentioned below:
      • Responsible for profit and loss of the project.
      • Decides the release dates of each Sprint and Project deadlines.
      • Defines feature of the Product.
      • Prioritize and adjust the feature of Product during each Sprint.
      • Accept or Reject the work result after each Sprint.
      • Responsible for conducting Sprint Review and Sprint Retrospective meeting.
      • Responsible for improving the development process.
  • Scrum Master(SM):
    • Scrum Master is responsible for all the scrum activities. Scrum Master is responsible that Scrum Team is fully functional. Responsibilities of SM is mentioned below:
      • Conduct the daily scrum meeting and keep an eye on the status of the Product.
      • Help Scrum Team to achieve their goal within given time frame.
      • Removes the impediments during each Sprint.
      • Motivate the Scrum Team to work efficiently and effectively.
      • Make sure that team is working in the collaborative mode.
      • Make sure that team is fully functional and on right track.
      • Make sure that all the requirement get implement on time.
      • Responsible for delivering a quality product to the customer after each Sprint.
  • Scrum Team:
    • A Scrum Team is a set of people with cross-functional skills. It includes experts from each field i.e. UX Team, Tech Team, Testing Team, SME(Subject Matter Expert), Architect etc. All the members should have the capability of working in the collaborative mode. Responsibilities of Scrum Team is mentioned below:
      • Implement their skills and experience to improve the development process.
      • Work smartly to achieve the organizational goal within given time frame.
      • Maintain the quality of the product during each Sprint.
      • Complete their task on daily basis.
      • Attend the Scrum meeting daily and have their status on fingertips.
      • If any impediment is present raise the same on right time.
      • Put their thoughts in front of the team during the meetings.

2 thoughts on “Agile | Agile Development Process”

Leave a Comment

Your email address will not be published. Required fields are marked *

   YouTube ChannelQuora

            Ashok Kumar is working in an IT Company as a QA Consultant. He has started his career as a Test Trainee in manual testing in August 2010. Then he moves towards the automation testing after 4 years. He started learning JAVA and Selenium by self to get the knowledge of automation.

       While learning these tools and working on multiple projects, he found that sometimes people get stuck in live scenarios in their project and they have to do lots of RnD to get out of it. So he decided to start blogging only for such scenarios, where anyone facing any problem in their project, can ask any question or give a solution or you can say an alternate solution to achieve the goal successfully.

Later on, he observed that some people want to learn Java but they have few questions in their mind like how to start Java, whether we should go for the online or offline course. So he started writing tutorials on Java, Jira, Selenium, Excel etc.