Agile Model Part 2

Scrum

      Scrum is a type of agile process which is used for software development.
  1. EPIC(Requirement):   Complete set of requirement is called as Epic in agile model. Epic will be created by the scrum master or product owner in project management.
  2. Stories or User Stories: Features or Modules or Functionalities is called as stories in agile model.
  3. Story Point(It's like test cycle): It is a rough estimation given by the developers and test engineers to develop and test each and every individual stories.
  4. SWAG: It is a rough estimation given by developer and test engineers for each and every individual stories in terms of hours.

Test Engineer Story Points

  1. Time taken to understand the requirement.
  2. Time taken to write scenario.
  3. Time taken to write test cases.
  4. Time taken to review test cases.
  5. Time taken for defect tracking.
 By considering there points test engineer will give story point.

Development Story Points

  1. Time taken to understand requirement.
  2. Time taken to design.
  3. Time taken to write the code.
  4. Time taken to do white box testing.
  5. Time taken for code review.
  6. Time taken for fixing the defect.
By considering all these things developer will give story point.

RELEASE

Combination of sprints is called as Release.

SPRINT

It is the actual time taken by developers and test engineers to develop and test one or more stories.

Agile Model Part 2

Sprint Planning or Sprint Planning Meeting

  1. Sprint Planning is a meeting conducted by the scrum master on the first day or every sprint.
  2. Developers, Test Engineers, Business Analyst, Project Manager and Scrum Master will be part of this meeting sometimes customer will also join this meeting.
  3. Business Analyst will explain the requirement to the entire team and he will also explain how each and every story should work and also customer business workflow to the entire team.
  4. Scrum Master will prioritize the stories from customer business point of view and assign the stories to developers and test engineers based on their availability.
  5. Scrum Master will calculate available hours of every individual engineers in this meeting.

Previous
Next Post »