Importance Of The Software Development Method With Scrum
practices or managing software projects. In this paper, management part will be considered for which Scrum is taken. Agile processes generally promote a disciplined management process and teamwork. It encourages frequent inspection and adaptation to enable organizations to manage the software product whose requirements changes frequently. Scrum significantly increases productivity and reduces time to benefits relative to classic processes. There are 12 principles on which Agile methodology relies , some of the main highlights are; customer as a priority, requirement change adaptation at any stage, frequent delivery of working software, business and developing team members work together, work is defined for the specified time. This paper presents the importance for developing Test Automation using agile development process scrum. An example of process in development of Automation framework for Wireless Layer-1 software-compatible with different platform is demonstrated. In section II, the agile development with Scrum is explained. Section III shows details of the proposed method of developing test automation framework and its advantage. Section IV discusses about a case study on this methodology. Finally, section V presents the …show more content…
PROPOSED DEVELOPMENT PROCESS
Test automation is created to test a developing software product. Development of software test automation is somewhat equivalent to developing a software project. Figure 2 presents the basic software development to deliver cycle. So, initially developing this testing tool may take a jitter period before product developers found it more useful comparing to manual testing. Let say product development and test automation both are being developed in the scrum, so these two scrums named as PD scrum and TA scrum respectively.
The product planning meeting of both PD scrum and TA scrum could be combined as these are interconnected. And two product backlogs should be created. TA scrum PB should have higher priority PBIs based on PBIs of PD scrum and generally more numbers of PBIs are present in TA scrum PB. The risk-based testing helps in deciding the order and functionality to test as everything can’t be tested during the initial stage. Also a large number of automation developers are required at that time. It may be possible to test the product manually for few starting scrums. Few members of TA team could be dedicated to support the manual testing of current PD sprint release