A Brief Introduction To Scrum Process

Posted By : Kuldeep Sidana | 27-Feb-2018

Scrum Process

Scrum,  the most famous agile framework in today’s software development, follows an iterative approach that is its core the sprint. Scrum teams use guidance throughout an agile project to ensure that the team achieves the goals of each part of the process.

Requirement Gathering

Requirements gathering is an important part of any project and of the project management. Understanding completely what a project will deliver is challenging to its success.Requirements gathering sounds like good common sense, but surprisingly, it's an area that is given far too less attention.

  • BA or Project Managers gather the requirements from the client.
  • According to new requirements, BA creates Epic, Stories, Tasks and Bugs.

Sprint Creation and Sprint work Discussion

A sprint — also called as an iteration process — is a short (generally for two to four weeks) period in which the development team develops and gives a  distinct product increment, for e.g. a working milestone version. In JIRA Agile, go to Plan mode on your board to create a sprint, choose whatever issues prioritise and start a sprint. Project manager creates Sprint on the basis of team size, sprint duration and the complexity of work.


  • Project managers discuss with the prospective lead about the work which they have planned to deploy in the sprint.
  • After that discussion, the due date and story points i.e how much hours they have estimated for development is updated in Jira by respective team members.
  • On the particular due date, the work is completed and the task is assigned to the QA team for testing.


Daily Stand-Ups  

 

  • Daily stand-ups meetings to discuss sprint progress with below goals-
  • Completed Tasks yesterday??
  • Plan for Today?
  • Any issues/challenges blocking sprint delivery

Sprint Closure Meeting

  • Discuss if any bottleneck is affecting any task not to be completed in the current sprint, then it is moved to next sprint.
  • All the bugs of the sprint are fixed before it gets closed.
  • After successfully testing of all deliverables the sprint closed by project managers.
  • Also, plan for the next sprint


Production Deployment


   
Release once verified on Development server by the dev team and Staging/QA server by QA team is deployed to the Production environment.

 

About Author

Author Image
Kuldeep Sidana

Kuldeep Sidana is an orient QA Engineer having dexterity in Core Java and vouched with Automation Testing tool (Selenium Web Driver) and Manual Testing.

Request for Proposal

Name is required

Comment is required

Sending message..