Skip to main content

Agile Model - SCRUM Process Overview

Lot of testers have interest to know about,
1. What is agile model?
2. What is the advantage of it over other models?

Agile - Simply we can say "On demand, more monitored and controlled testing"
Agile model have benefits like,
1. Easy adoption of requirement changes at any stage.
2. Piece of working product will be arrived very early in life cycle.
3. More monitoring on team so every team members will be in same path and goal.

SCRUM is one of a process of agile methodology. SCRUM involves below terms,
1. Sprint
2. Scrum master
3. User Stories
4. Work Items
5. Sprint Back Logs
6. Sprint retrospective item, etc.

Sprint - Sprint is nothing but the scrum period. i.e. The no of days for between each release like 30 days, 15 days. This is mainly based on customer requirement. If your every sprint consists 30 days, then every 30 days there will be a release. Sometimes release will not be there based on customer request.

Scrum Master - The person responsible to assign the tasks to team members and monitor the team.

User Stories - User Stories are the original requirements from customer. This may be "New functionality" or "Change Request".

Sprint Work Items - Work Items are the Task items created by Scrum Master with Estimated time for each User story. Normally scrum master will create task item for each user story and assign it to some team member with estimated time.

Sprint BackLog Item - Sprint back log items are the sub task items created by every team member for each assigned work item. Team member will create this sprint back log item for each assigned work item and he will set estimated time. This is used to track the daily effort done by team member and to update the status like how much hrs actually worked on this sprint back log item. Automatically this will affect the Work Item related to this Sprint back log item. So finally the User story will be finished by doing all the work items related to that user story.

Sprint Retrospective Item - Retrospective item will be created after sprint release. This should cover the answers for below 2 questions.
1. What went well?
2. What can be Improved?

Now, you should be aware of above terms. Let's see, how actually scrum will be followed in real time projects.
1. Customers will enter the User Stories in your ALM system like TFS, QC, etc.
2. Once received user stories, scrum master will arrange a meeting called Sprint Planning Meeting
3. In Sprint planning meeting, scrum master will discuss with team members like
    What are the user stories we can select for this sprint?,
    Which user story going to handle every team member?, etc.
4. After planning meeting, scrum master will create Sprint Work Items for each user story and assign them to team members. For ex. Login Module is the user story. For this story, scrum master will create work items like Development of Login Module, Testing of Login Module, Regression and Retesting of Login module, etc. and he/she will put the estimated time to finish each work item.
5. Now, team members will pick up their work item and create Sprint Back Log Items i.e. sub work items. For ex. Team member will create sprint back log items like UI development, functionality development, unit testing, etc for Development of Login module work item.
6. Daily team members will work on their tasks and update their actual worked hours (i.e. burning worked hours) against estimated hours in sprint back log items.
7. This will give progress status for every sprint back log item which in-turn update sprint work item's progress. Finally every one can able to know the progress status of each user story.
8. Daily 10 to 15 mins quick meeting will be arranged by scrum master to update daily status, showstoppers and any blockings to continue the planned tasks. Based on this, they will continue their progress. This is called Daliy Scrum Meeting
8. Once everything is OK and working fine and tested, then we will go for release.
9.After the release, scrum master will arrange a meeting called Sprint Retrospective Meeting. In this meeting, every will discuss about the 2 points mentioned above and will create retrospective items if any.
10. In future releases, team members will concentrate to cover the created retrospective items as part of sprint tasks.

Hope this will give you basic idea about the scrum process in agile model...


  1. Hey Interesting, I have included your blog in one of my blogs dedicated exclusively for Coimbatore Bloggers

  2. Nice information . thanks for sharing.
    I have question which is out of this topic but related to testing .I am looking for test plan template which is in tabular format not in 10/15 pages document .Does anyone have samplet test plan template used in their company or any idea in creating it(what are the columns need to be added when creating this template)? For any kind of information regarding this can anyone please email me at
    Thanks in advance!


  3. Thanks for sharing great information in your blog. Got to learn new things from your Blog . It was very nice blog to learn about Selenium


Post a Comment

Popular posts from this blog

QTP - Object Identification - Prerequesties

While starting a new project or proof of concept or after new QTP installation, we would face the issue in identifying objects as QTP built objects like WinList, WebEdit, etc.; instead everything will be identified as WinObject.

Here are some steps to ensure you did the environment setup RIGHT before start automating.
Did you enabled required Add-ins only while launchingDid you selected "Record >> Record and Run Settings" - This should be based on what type of application you are working with
Windows app - Windows >> Record and run test on any windows applications. Web app - Web >> Record and run test on any open browser.
Did you tried to launch UFT/QTP and then AUT.If its web, ensure browser zoom level set to 100%Try disabling the protected mode in IE for web.Launch UFT and AUT using RUN AS ADMINISTRATORAlso see the Object Identification Methods if you are interested.

Change IE Browser ZOOM settings

Lot of UI automation testers could have faced this problem as we could change the zoom settings while operating manually for our convenience and forgot to reset to 100%.
But our QTP and some other related tools would operate the browser perfectly if browser zoom is 100%. So wee need to change the zoom before start to run the scripts. Its better to have a code snippet in our framework to change this zoom setting right?
Here we go...

1. We can simply change the Registry values before Invoking IE
Function ChangeRegistry Dim objShell Set objShell = CreateObject("WScript.Shell")  objShell.RegWrite "HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Zoom\ZoomFactor", "100000", "REG_DWORD" Set objShell = Nothing EndFunction This option is very useful. But in real time, lot of customers could have restricted write access to windows registry. So we can try other options.

2. Use IE COM object and Change Settings
Function ChangeIEZoom Dim intZoomLevel, objIE  intZoo…

QTP - Common error messages

Always I am seeing  many of my friends asking for help if any error occurs while running script in QTP without googling for help. How much troubleshooting you guys are doing will directly reflect your knowledge on the tool. I agree, no one knows each and every error occurs in the software. But we can improve our knowledge by googling and doing workarounds...
Whenever the question "How much level you know QTP?" arrows me, always I am comfortable with the answer "below 10%". But after answered, my mind will have an inner thought like, What are the things I have to learn to fulfill the answer I have told because I never used lot of features in QTP.

Here I am listing out some of the errors, situations and what might be the original issue things etc. I hope this will give you some ideas to improve your debug ability and to solve your errors. Kindly correct me If I am wrong in any point.

Type mismatch:
- Mostly doing operations with different data types without doing type co…