Manual Testing for Beginners – Ceremonies in Scrum in Detail

Manual Testing for Beginners – Ceremonies in Scrum in Detail:

Kick of Meeting:

Software company CEO can conduct this meeting to select product owner (PO). This selection will be approved by customer and stakeholder.

Product Backlog Grooming meeting:

The selected PO can sit with customers and stakeholders to gather requirements as user stories. The list of all user stories is called as product backlog.

Here every user story is a customer requirement. If any requirement user story is big/epic, PO can divide that big requirement in to small user stories.

Note:

Product Owner is responsible to develop product backlog by talking with customer and his/her stakeholders. Here, PO can follow below like format:

Feature

As a

I would like to

So that

Acceptance Criteria

User

Open site -> Enter User id as alphanumeric from 4 to 16 positions

-> Enter Password as Alphabets from 4 to 8 positions

-> Click OK

Next Page will come for valid user and error message will come for invalid user

In Android mobile/ IOS Mobile / Windows computer/ MAC computer/ Linux computer.

User Stories in Product backlog. (IEEE format table).

While preparing product backlog, PO can take the help of external people like domain experts (or) subject matter expert (SME).

Sprint Planning Meeting:

After completion of product backlog grooming meeting and finalization of user stories, corresponding PO can concentrate on the selection of scrum master and scrum team. Here, scrum team is a formation of developer and testers in 3:1 ratio.

After Completion of team formation, corresponding PO can sit with SM and ST members to select some user stories from all user stories in product backlog document. Here, PO can depends on priority to customer or market and size of user stories.

In above example the T-shirt terminology is used to specify the size of the user stories in product backlog. Priority is respect to customer on market need.

Daily Scrum Meet:

During 30 days of sprint process , developers and testers can meet PO, Scrum master and stakeholders to discuss 3 questions related to that day.

What we did today?
What we will do tomorrow?
What obstacles are in our way?

In general, the above like meeting is mandatory on everyday and this meeting time is 15minutes. This meeting is also called as stand-up meeting. This meeting agenda is knowing problems but not solving problems.

Sprint Review Meeting:

This meeting is useful to collect feedback from customer on sprint. If feedback is not good, developers can perform changes and tester can test those changes.

After completion of sprint review meeting (2 hours) Po and scrum master can concentrate on sprint release process.

Sprint Retrospective meeting:

After completion of current sprint release and before going to next sprint, scrum master and scrum team members can conduct a meeting, called as sprint retrospective meeting. Through this meeting, scrum master and scrum team can discuss problems faced in last sprint 30 days and they will discuss solutions to overcome those problems in upcoming sprint 30 days. This meeting is mandatory for first 5 – 6 sprints.

Product Backlog refinement meeting:

During this meeting, PO can go to sit with customer and stakeholders and allow changes in user stories if required.

In this article we have seen Manual Testing for Beginners – Ceremonies in Scrum in Detail

In the next article will see about Agile Scrum Process Diagram.