Agile Model Part 3 ~ Tumblia Test Solution

Scrum Master

Scrum Master is a person who is responsible for delivery of the software to the customer within planned period of time.
Scrum Master will be mainly working on project management tool, where in scrum master will create stories and tasks for the stories and assign the tasks to every individual engineers and scrum master will track each and every activities done by the developers, test engineer and business analyst.

It is a meeting conducted by the scrum master on daily basis (It is also called as stand up meeting). This meeting will be strictly bounded for 15 minutes.
Developer, Test Engineer, Business Analyst, Project Manager, Scrum Master and Customer will be involved in this meeting.

NOTE: Customer and Project Manager will take part in this meeting sometime.

In this meeting we discuss below mentioned 3 points.

It is a meeting conducted by the scrum master on the last day of the every sprint.
Developer, Test Engineer, Business Analyst, Scrum Master, Project Manager and Customer will be part of this meeting.

NOTE: Customer and Project Manager will take part in this meeting sometime.

In this meeting we discuss below mentioned 3 points.

It is a meeting conducted by scrum master on the last day of the release.
Developer, Test Engineer, Business Analyst, Scrum Master, Project Manager and Customer will be part of this meeting.

NOTE: Customer and Project Manager will take part in this meeting sometime.

In this meeting we discuss below mentioned 3 points.

It is a meeting conducted by test engineer or business analyst one week before the release or sprint.
Developer, Test Engineer, Business Analyst, Scrum Master will be part of this meeting.
Test Engineer will get the list of all the pending and open defects which are not fixed by the developers in the current release and the previous release re-prioritize the defect from the customer business point of view and decide which bugs can be fixed in current release and which defect can be moved to the next upcoming releases. This is called as bug Priogeing.

It is a meeting conducted by scrum master or business analyst a week before the release.
Business Analyst , developer, test engineer, scrum master, customer and project manager will be part of the meeting.
In this meeting we will get the list of all the pending stories or features which cannot be implemented in the current release and we re-prioritize the stories from customer business point of view and decide which story can be implemented in the current release and which story can be move to the upcoming releases. This is called as product backlog meeting.

NOTE: Customer and Project Manager will take part in this meeting sometime.

Bug Bucket is an epic or story created by the scrum master in the project management tool. Bug Bucket consists of all the old and pending defects which are not fixed by the developers.
Bug Bucket should be handled as a part of every release.
Advantages- Used to reduce the bug count.