Agile scrum is one of the famous as well as advanced model used nowadays in software testing. The dictionary meaning of scrum is a team of various people who are having their own special skill sets. In this field of software testing, scrum is a team which includes developers as well as testers.
• It is the famous and advanced SDLC model to develop the project based and product based software.
•
It develops the software
as increment by increment, called as
Sprint.
•
It releases the sprints
to client or market in incremental
spiral process.
•
Actually, one sprint is a
combination of previous sprint and some
other extra features.
•
Here, Sprint means piece of software which is
potentially shippable (release) to
the client or market.
•
For every sprint development and testing, we
actually need team size of 7 to 10
members and duration as
approximately 30 working days. In this 7 to 10 members team, the ratio of developers to testers is 3:1
a) Agile Scrum Process:
b) Agile Scrum Process Components:
C) Roles in Agile Scrum:
•
Client
•
Stake Holders
•
Higher Management (CEO)
•
Product Owner (PO)
•
Scrum Master (SM)
•
Scrum Team (Scrum Team
)(Developers + Testers)
•
Change Control Board
(CCB)
Client
responsibilities in Agile Scrum:
•
Responsible to send proposal to the software company.
•
Responsible to approve PO selection.
•
Responsible to sit with PO to share the requirements.
•
Responsible to appoint the stake holders (If Software
is Project Based)
•
Responsible to involve in
every sprint review to give feedback.
• Responsible to involve in
product backlog refinement meeting
to give changes in requirements if needed
Stake Holders responsibilities in Agile Scrum:
•
Responsible to approve the PO selection.
•
Responsible to share client requirements to
PO.
•
Responsible to select some user stories from all user stories.
•
Responsible to involve in daily scrum meeting.
•
Responsible to involve in
every sprint review to give feedback
from client.
•
Responsible to involve in
product backlog refinement meeting.
Higher Management (CEO) responsibilities in Agile Scrum:
• Responsible to receive proposal from client in project
based software and prepare own
proposal in product based software.
•
Responsible to appoint stakeholders (Model SH’s) in
product based software.
•
Responsible to select PO.
Product Owner (PO) responsibilities in Agile Scrum:
• Responsible to create user stories by talking with clients
and SH’s. The list of all user
stories is called as product backlog.
• Sometimes PO can take the
help of Subject Matter Expert (SME)
to get clarity on client requirement. But SME
is outsider.
•
PO can divide big user stories (Epic) into smaller user stories if needed.
•
PO can sit with SH’s, SM
and ST to select some user stories from
all user stories.
•
PO can participate in daily scrum meet along
with SH’s, SM and ST for status reporting.
•
PO can join with SH’s, SM
and ST to take feedback from client on
every sprint.
• PO is responsible for sprint release if required. (Some
companies can release final sprint only
i.e. whole software.
User
Story ID
|
As
a
|
I
would like to
|
So
that
|
Acceptance
Criteria
|
US
Login
|
Registered
Users
|
-Launch
site
-Enter
user id which is alphanumeric from 4 to 16 positions
-
Enter password which is alphanumeric uppercase from 4 to 16 positions
|
-next
page for valid data
-error
message for invalid data
|
-Login
is easy to use
-Login
is possible with IE/Chrome/Safari/FF/Opera browsers in Windows/Linux/Mac OS
and Android/iOS/Windows mobiles
|
---
|
---
|
---
|
---
|
---
|
Ex. Product Backlog for all user stories
•
PO can join with SH’s,
SM, ST to get refinements (changes) in
user stories from client.
•
In agile scrum, PO is decision maker.
Scrum Master (SM) responsibilities in Agile Scrum:
•
Scrum master is a facilitator.
•
Responsible to organize sprint planning meeting.
•
Responsible to organize daily scrum meet.
•
Responsible to organize sprint review meeting.
•
Responsible to organize sprint retrospective meeting
with ST only.
•
Responsible to organize product backlog refinement meeting.
Scrum Team Developer (ST) responsibilities in Agile Scrum:
•
Responsible to involve in sprint planning meeting
along with PO, SH’s, SM and ST Testers.
• Responsible to design sprint, implement sprint, unit testing,
integration and integration testing.
•
Responsible to release sprint to ST testers.
•
Responsible to receive the bugs from ST Testers. Bug report
can also be called as defect, issue, ticket, and incident.
•
Responsible to resolve bugs and release modified sprint to ST
Testers.
•
Responsible to involve in daily scrum meeting.
•
Responsible to involve in every sprint review meeting.
•
Responsible to involve in sprint retrospective meeting.
•
Responsible to involve in product backlog refinement
meeting.
Scrum Team Tester (ST) responsibilities in Agile Scrum:
•
Responsible to involve in sprint planning meeting
along with PO, SH’s, SM and ST Testers.
• Responsible to study user stories and go to test design. Test
design includes test scenarios and test cases.
•
Responsible to receive sprint from ST developer.
•
Responsible to execute test cases (Real Testing) on sprint to
detect bugs. (manual)
•
Responsible to report the bugs to ST developers and get
modified sprint.
• Responsible to execute test cases (Retesting) on modified
sprint ensure the bug fixing correctness. (manual / Automation)
•
Responsible to involve in daily scrum meeting.
•
Responsible to involve in every sprint review meeting.
•
Responsible to involve in sprint retrospective meeting.
•
Responsible to involve in product backlog refinement
meeting.
Change Control Board (CCB) Fresher’s responsibilities in Agile
Scrum:
•
Responsible for released sprint maintenance.
•
Responsible to receive change request from client site.
•
Responsible to perform changes in sprint and release patch
files to client site
C) Ceremonies (Meetings) in Agile Scrum:
a) Kick of Meeting:
•
Participants:
CEO and PO category people.
•
Agenda of Meeting:
to select one PO who can handle current project/Product.
•
Time Box: 1 to 2 hours.
b) Product Backlog Grooming Meeting:
•
Participants:
PO, SME (optional), client and SH’s.
•
Agenda of Meeting:
to gather all requirements and to prepare all user stories.
•
Time Box: No specific/exact time.
c) Sprint Planning Meeting:
•
Participants:
PO, SH’s, SM and ST (Developers + Testers).
•
Agenda of Meeting:
to select some user stories from all user stories.
•
Time Box: 2 to 3 hours.
d) Daily Scrum Meeting (Stand-up meeting):
•
Participants:
SH’s, PO, SM and ST.
•
Agenda of Meeting:
to gather information about…
•
What did you did today?
•
What will you do
tomorrow?
•
What obstacles are there
in your way?
•
Time Box: 15 minutes.
e) Sprint Review Meeting:
•
Participants:
Client, SH’s, PO, SM and ST.
• Agenda of Meeting:
Collecting feedback on every sprint from client and perform instant changes in
sprint if needed.
•
Time Box: 2 to 3 hours.
f) Sprint Retrospective Meeting:
•
Participants:
SM and ST only.
•
Agenda of Meeting:
to identify and solve issues related to scrum team.
•
Time Box: 2 to 3 hours.
g) Product Backlog Refinement Meeting:
•
Participants:
Client, SH’s, PO, SM and ST.
•
Agenda of Meeting:
to perform the changes in user stories to be developed.
•
Time Box: 2 to 3 hours.
e) Artifacts (Documents) in Agile Scrum:
•
Traceability Matrix:
It is the summary table of sprint
testing.
Features
in Sprint
|
Test
|
Passed/Failed
|
Defect
Report
|
Closed/Deferred
(Postponed)
|
Login
|
Test1
Test2
Test3
|
Passed
Passed
Failed
|
-
-
D1
|
-
-
Closed
|
---
|
---
|
---
|
---
|
---
|
•
Sprint Burn-down Chart:
(Scrum Team Size (10))* (8 hours Working
Days)*(30 Days) = 2400 hours.
f) Multi-Scrum Process:
When the project is big, organization can follow multi-scrum process. From this process,
organization can divide big project into
multiple sub projects. Organization can maintain separate ST with SM and PO to handle every sub project.
Organization can maintain
master PO and chief SM to make the
co-ordination among multiple ST’s which are working for corresponding sub
projects.
f) Agile Certification:
Steps:
•
Go to scrumstudy.com
•
Click Register
•
Fill all fields
•
Click Submit
•
Click Login
•
Click on “Scrum
Fundamental” exam.
•
Answer all questions
Comments
Post a Comment