Recent research report shows the wide acceptance of agile development methodology to create qualitative software in short development cycles. It encourages the early development of software with more promising quality. Early testing strategies with multiple test cycle decrease the number of defect in product. In each iteration automated testing minimize the test effort and cost of testing. Basic agile practices like pair programming, continuous integration, small release, simple design and re-factoring make the development procedure more promising. Scrum is most widely used agile framework for developing software within four weeks. It keeps the document light and manage requirements in the form of product backlog. Testing is performed on the features which are developed in scrum process. Tester are more integrated with development team and collaborate with customers for early feedback. Automated tools are used to enhance the communication in distributed team members. Planning and meetings are the heart of agile testing. Design is more flexible to accommodate change in requirements. Testing process includes unit, integration and regression testing with non functional testing. Automated tool s are used for unit and regression testing in scrum process. These tools helped significantly to simplify and speed up the development cycle. In this paper the testing process performed in scrum environment is discussed through testing model. Test strategies like unit and regression testing method is adopted in the process. Management of user requirements through product backlog and sprint backlog is discussed with suitable example. Different methodology of backlog estimation i.e initial estimation technique and planning poker method is discussed in this paper.

Agile Software Development, Scrum testing, Backlog management

[1]. "Agile Manifesto" agilemanifesto.org/principles.html.
[2]. J. F. Abrantes and G. H. Travassos. Common agile practices in software processes. IEEE International Symposium on Empirical Software Engineering and
Measurement, 2011.
[3]. A. Ahmed, S. Ahmad, D. N. Ehsan, E. Mirza, and S. Z. Sarwar. Agile software development: Impact on productivity and quality. IEEE ICMIT, 2010.
[4]. A. Aitken and V. Ilango. A comparative analysis of traditional software engineering and agile software development. 46th Hawaii International Conference on System Sciences, 2013.
[5]. E. Collins, A. Dias-Neto, and V. F. de Lucena Jr. Strategies for agile software testing automation: An industrial experience. IEEE 36th International Conference on Computer Software and Applications Workshops, 2012.
[6]. E. Collins, G. Macedo, N. Maia, and A. Dias-Neto. An industrial experience on the application of distributed testing in an agile software development environment. IEEE Seventh International Conference on Global Software Engineering, 2012.
[7]. D. D. Gregorio, PMP, and CBAP. How the business analyst supports and encourages collaboration on agile projects. Information Systems, Infrastructure, & Services - Systems Engineering, IEEE, 2012.
[8]. B. Haugset and G. K. Hanssen. Automated acceptance testing: a literature review and an industrial case study. Agile 2008 Conference, 2008.
[9]. T. Hayata and J. Han. A hybrid model for it project with scrum. IEEE, 2011.
[10]. I. Kayes. Agile testing: Introducing prat as a metric of testing quality in scrum. ACM SIGSOFT Software Engineering Notes.
[11]. H. Kniberg. Scrum and XP from the Trenches. C4Media, Publisher of InfoQ.com., United States of America, 2007.
[12]. E. J. Quaglia and C. A. Tocantins. Simulation projects management using scrum. In Proceedings of the 2011 Winter Simulation Conference IEEE, 2011.
[13]. R. A. Razak and F. R. Fahrurazi. Agile testing with selenium. 5th Malaysian Conference in Software Engineering (MySEC) IEEE, 2011.