Scrum Methodology: Benefits, Challenges, and Recommendations for Small-Scale IT Companies

CHAPTER 2 LITERATURE REVIEW

INTRODUCTION

This chapter is an important part of the research as it is related to the core theme of the study. The chapter is divided into various sections which will discuss the important aspects of the study. The first section of this chapter will discuss a few definitions such as what is agile and scrum. The other section will discuss the need of Scrum and its importance in the small-scale organisation. This section will also highlight various benefits of using Scrum in the small-scale IT companies. The next section will discuss about the issues and challenges face by the small-scale IT companies due to Scrum. The next section will discuss the strategies that the organisation can use to resolve the issue of scrum methodology. At last, the researcher will discuss the gap of study in literature review which would give idea to the researcher to conduct the study in future in a better way.

WHAT IS AGILE

Agile is the term which is referred to a group of software which provides solution to the problems of organisation. Agile methodology has become the need of every organisation (Maruping et al., 2009). Everybody is looking forward to the effective practices that could help organization to gain competitive advantage. Agile software development is the term which refers to the group of software development methodologies based on iterative development, where the teams of different organisation collaborate to resolve the problems and fulfil the requirement of functional team in the organisation (Maruping et al., 2009).

Agile methods promote a disciplined project management process which encourages to the company to adopt new methods and proper inspection of the products and services. A leadership philosophy in the agile methodology includes the best framework which encourages the team to work in an effective manner (Maruping et al., 2009). The best agile practices in the organisation include rapid delivery of the software, no compromises with the quality of the software, and a business approach which allows companies to develop the business by understanding the needs of the customers (Srivastava et al., 2017).

Agile development could be understood as the development process which is generally aligned with the agile manifesto concepts. One of the common and effective agile methodologies is scrum (Maruping et al., 2009).

Figure- agile methodology

Source- (Maruping et al., 2009)

WHAT IS SCRUM?

Scrum is one of the agile methodologies which is designed to guide the teams in the iterative and incremental deliveries of the products (Kumar and Bhatia, 2012). It provides an agile management framework to the company. Scrum is mostly focused on the use of an empirical process which allows the team to respond quickly, effectively, and efficiently in the changing environment of organisations. Scrum is the simple agile approach that is implemented by the companies for the product development. There are also various agile approaches such as crystal, XP, etc. (Schwaber, 2004).

In other words, scrum is the subset of agile (Srivastava et al., 2017). It is the best framework for agile development. Scrum is a set of practices which allow companies to complete the process and become consistence to objectives of the company. Scrum is different from the agile process by some specific concepts and practices (Kumar and Bhatia, 2012). In the organisation generally, scrum is used to manage complex software and for the product management and development. The scrum is used to increase the productivity and reduce the operation time. The methodology is effective than the traditional method used for managing the problems in the organisation in the past years (Kumar and Bhatia, 2012).

NEED OF SCRUM IN ORGANISATION

The scrum technology was first introduced and applied by Jeff Sutherland and Ken Schwaber in 1996 (Singh et al., 2019). Both the owners have set the framework in which the scrum will work. The purpose of introducing scrum was to connect the multiple teams in a network in order to reduce the complexities of the business easily (Maximini et al., 2018). After 2001 it has become popular in the industries by associating with the scale of agile.

According to Schwaber, scrum is the framework not a methodology. Purpose of scrum is to provide the delivery structure rather than explaining practices that how it could be specifically implemented in the organisation to get the effective results (Larman and Vodde, 2016). In the organisation adding more people in the project becomes harder; adding more people in the project brings the solution for the complex problems (Maximini et al., 2018). From many years the companies are trying to find out the effective way to increase their connection among the teams. The organisations implement Scrum in the organisation as it offers a way to connect the team with the other team (Larman and Vodde, 2016). Multiple teams could be connected together to work and to deliver complex solutions. It brings transparency among the team while working in the same projects. It allows the owner to inspect the working of the team and improve their scalability (Maximini et al., 2018).

SCRUM MANAGEMENT PRACTICES

Scrum allows the customers to change their requirements at every point at every time. In Scrum, the development team are highly committed with the quality of the product and to respond the customers frequently. There are some best Scrum management practices that the company implements to get good results (Alavandhar and ?ikiforova, 2017).

PRODUCT BACKLOG AND PRIORITIZATION

It is the initial and important management practice for the Scrum team. The working of the team starts with the product backlog in which team makes the list of everything such as the needs of product and list of orders on priority (Shafiee et al., 2020). Scrum allows stakeholders, customers, and owners to make changes in the list. The list continuously changes with the changes in the requirement. This management practice improves the quality of the product. As every demand of involved people are included in the list which takes the product development in the right direction. Based on the priority list, the working team gets the estimation of the task and needs (Shafiee et al., 2020).

Figure- Scrum practices

Source- (Singh et al., 2019)

SPRINT PLAN AND REQUIREMENT REFINEMENT

The other management process is sprint plan and requirement refinement in which the Scrum team makes proper plan and discuss with each other to complete the task in an effective manner (Alavandhar and ?ikiforova, 2017). The Scrum team breakdown the tasks to find the requirements. If the requirements of the task are not clear to the working team it creates difficulties and also increases the time of working span. Scrum allows sprints to complete the process in thirty days in which planning, developing, testing and delivery are included. Scrum allows spirits to provide 100% shippable item (Shafiee et al., 2020).

START SPRINTS AND STAND-UPS

It is the third management practice where Scrum team starts working on the projects after finalising the start and end dates (Alavandhar and ?ikiforova, 2017). The team works on the Scrum rule in which working team finishes the task in the sprint and make sure it must meet to the customers who they have committed. In this management practice, the working team connects with the other members on the daily basis so that every member of team must be aware of the issues and concerns that can be the barrier in the product development (Shafiee et al., 2020).

BURN DOWN CHART

In this management practice, the working team detects the issues in the early stage and starts working on it (Alavandhar and ?ikiforova, 2017). This management practice of identifying the issues in the early stage is very crucial for the team. As disturbances affect the efficiency of the team. Scrum allows the team to track the daily activities to check daily progress. Scrum methodology allows the companies to use burndown chart which also highlight the pending task of the members (Hidalgo, 2019).

TIME LINE

Completing every task on the particular time gives benefits to the organisation (Kumar and Bhatia, 2012). The team could easily move to the next task by completing the task on time. Determination towards the completion of the work allows the team to deliver the products rapidly to the customers with in time limit (Oprins et al., 2019).

SPRINT REVIEW

At the end of sprint, the working team holds the meeting for the reviewing of the products (Kumar and Bhatia, 2012). This meeting involves everyone and review on the tasks that were completed to develop the products. The meeting provides the idea to everyone about the project competition. Once the sprint is completed by the team, the team discusses about the product and its delivery to the customers (Oprins et al., 2019).

BENEFITS OF IMPLEMENTING SCRUM IN SMALL SCALE COMPANY

Scrum provides various benefits to the organisation, team, products, and individuals which are discussed below-

BETTER QUALITY

Better quality of the product and software increases the customer satisfaction (Kumar and Bhatia, 2012). The Scrum provides a better framework to the organisation which allows teams to take the feedbacks of the customers and expose the best quality product to the customers. Scrum helps the teams to ensure that the best quality of the product must reach to the customers in a possible way (Srivastava et al., 2017). Scrum defines and elaborates the needs of the customers time to time so that team work to improve their knowledge related to the product and features the qualities in the product to gain competitive advantage. To ensure better quality of the product Scrum allows the working team to test the product or their software (Srivastava et al., 2017). This includes the feedback of the owner and customers which allows the team to innovate the product. The fresh issues related to the product or software is highly discussed with the owner of the company and thus the product development process completes in a proper way to gain competitive advantage (Kumar and Bhatia, 2012).

DECREASED TIME TO MARKET

Scrum is an effective approach for rapid delivery of the product to the customers (Kumar and Bhatia, 2012). It increases the delivery time to around 30 to 40% faster than the traditional approach. Scrum allows the working team to separate the orders according to the priority wise. The high priority projects complete faster than the lower priority projects. This definitely decreases the delivery time to complete the delivery to the customers and also reduces risks of failure of the projects. The customers need not to wait to get their requirements (Srivastava et al., 2017).

INCREASED RETURN ON INVESTMENT

Scrum allows the company to meet the customer requirement in shorter time which also increases the return on investment of the company (Kumar and Bhatia, 2012). Because company starts receiving the benefits and profits sooner which means total rate of return will be more over the time. The working team continuously receives the feedback of the customers with the help of spirits. This allows the company to make the corrections as soon as possible and it also reduces the time consumption that the later process requires. Scrum also allows the working team to test the product in a good manner which reduces the wastage of time and faster delivery. Effective testing ensures a reduction in cost of project failure (Srivastava et al., 2017).

HIGHER CUSTOMER SATISFACTION

The Scrum teams in the organisation are committed to the quality of the products. It takes feedback from the stakeholder and customers many times so that they can provide better quality of the product (Kumar and Bhatia, 2012). Collaboration with the customers is such an effective process which increases the involvement of the customers throughout the projects. The company allow the owner to check the requirement of the customers with the product and to give an expert advice in order to increase customer satisfaction. The delivery of the product in the Scrum approach also increases the customer satisfaction and makes a healthy relationship with the customers (Srivastava et al., 2017).

HIGHER TEAM MORALE

Happy working environment in the company improves the morale of the employees (Oprins et al., 2019). The satisfying team works effectively in the organisation. Self-management allows the employees and leaders to take effective decisions (Kumar and Bhatia, 2012). Scrum ensures high morale of the team members in many ways such as when working member becomes the part of self-management and self-organising team this allows them to be creative with the product and introduce innovations (Oprins et al., 2019). They work as experts in their field. Scrum allows every team member to work in a specific way with specific personalities which makes the team creative and innovative. Scrum also allows the team to take decisions by their own to maintain their personal and professional life which increases the morale of the employees. Better relationship in the company also allows employees to share their problem with their colleagues and leaders which is very helpful to break the barriers that affect the team to work effectively and meet the business objectives (Kumar and Bhatia, 2012).

INCREASE COLLABORATION AND OWNERSHIP

Scrum team takes the responsibility of the projects and products to ensure good results (Maruping et al., 2009). The scrum team collaborates and take the ownership of the quality and project performance. The Scrum team plans to conduct the meetings which allow the team to work in an organized way to give the priority to the business. These Scrum meetings are organized daily which allows the team to revolve around the work and complete the work in an effective manner (Oprins et al., 2019).

Figure- benefits of scrum

Source- (Maruping et al., 2009)

PRACTICAL CHALLENGES FACES BY IT COMPANY IN IMPLEMENTING SCRUM

Scrum has basic and light weight rules and practices but is difficult for the companies to become a master in implementing scrum (Maruping et al., 2009). As soon as company apply it, it becomes challenging for the companies. Scrum was developed to resolve the complexities that were faced by the organisation but it has so many “hows” which are not clear which becomes difficult for the organisation. Scrum does not solve the problem but it allows company to share their problem and share it with the other team to get the solution of the problem (Singh et al., 2019).

Resistance to change

Apart from all the benefits scrum also has various disadvantages. The companies face various challenges while implementing scrum in the companies which are discussed further. Scrum increases resistance to change (Jurado et al., 2017). It is a type of roadblock which reduces the ability to change the culture, working process, values. In the Scrum, it becomes difficult for the organisations to change the working process, especially in the IT sectors. Companies who develop software face difficulties in order to change as they fear if people do not like their apps or software it will affect their business. Employees have tendency to resists the change when it comes to their daily routine and comfort zone. This has become a challenge for the companies to implement Scrum and also change the working process to gain a competitive advantage (Jurado et al., 2017).

For the newly established organizations, Scrum is the challenge to deploy (Maruping et al., 2009). Implementing Scrum in the organisation require to change in the frequent mind-set of the employees that it will shake up their old habits and transforms them into more effective ones (Singh et al., 2019). The rapid change of technology, trend and needs in the market leads to change in the working culture, process, and management. This in turn becomes more challenging for small companies in order to improve their product quality by implementing scrum (Singh et al., 2019).

Distributed team

It is a perception that co-located scrum team ensures good communication and also delivers the work better than a distributed team (Maruping et al., 2009). Scrum team allows team member to complete the task from different locations. So, it becomes important for the scrum distributed team to find out the challenges that team members face due to different locations. Communication is the major challenge which can create major issues (Singh et al., 2019). Lack of communications affects the project as moving forward to the next task requires proper communication. Scrum distributed team works from different locations on different time. This different work and time zone leads to a poor-quality communication among team members (Srivastava et al., 2017). This affects the sustainability and productivity of the Scrum team. Also distributed team with different locations have different cultures and language barriers this may lead to misunderstanding which also affects the productivity of the organisation. Also, in addition to this, in IT sector the people of the different region have different IT skills based on their knowledge, academics and experience. This may create a class system in the remote teams. Also, the teams have different perceptions on the different technologies (Srivastava et al., 2017).

Wasteful daily stand-up meetings

Scrum includes effective daily meetings of 15 minutes maximum. In Scrum meetings team of nine members, each takes 5 minutes to discuss which takes 45 minutes (Srivastava et al., 2017). This may lead to the tiredness of the members also may lose their concentration. Due to which productivity of the team member decreases. This is the very common pain which the Scrum team faces in the IT Company (Miler and Kaidy, 2018). As time equals to the money and this is an unnecessary expense in IT company. The Scrum teams are generally very large and listening to everyone’s problem related to their current work may be unnecessary for the other team members. Many times, other team members also add up their opinions which may lead to re-plan or re-schedule the project dates. This is another issue which is time-consuming for the other Scrum team members. Meeting of every member is very crucial in Scrum. If the team does not meet daily it is no more Scrum team (Miler and Kaidy, 2018).

Handling bugs and urgent on-demand tasks

If the Scrum team has started the work which means there would be no changes accepted from the customers at last moment especially in the IT Company. So, team members have to wait for the next turn (Conboy and Carroll, 2019). Not this may be an issue for the team members as not all the issues can wait to the next sprints. Some have to be managed on the urgent basis as per the demands of the clients. This is very far from peaceful environment in the team. Also, other team members don’t like the interference of the other members while they work on the project. Changing the clients’ demands creates disturbances for the other members (Miler and Kaidy, 2018).

Scrum allows team members to plan an effective schedule to complete the project which allows team members to focus on their task without any disturbance (Conboy and Carroll, 2019). And the iterative product development in the IT companies is on priority which takes the lead to reach its success. The interruption of the clients may affect the productivity of the Scrum team (Miler and Kaidy, 2018).

Testing in sprint

Scrum allows teams to test the efficiency and effectiveness of the software in the IT Company (Conboy and Carroll, 2019). The common problem is the team members face in the IT sector is, generally the development team works on the project till the last date which creates pressure on the testing team to test the software in the short period (Conboy and Carroll, 2019). So, the common challenge for the testing team is they struggle to figure out the issue in the software. Also, the testing team face the challenges including performing functional and regression tests, taking approval from the product owner and many others. This is generally a challenge for the IT professionals when they realise it in relatively short period (Miler and Kaidy, 2018).

RECOMMENDATIONS TO SOLVE THE PROBLEM RELATED TO SCRUM

The above section has discussed various challenges faces by the Scrum team while working in the IT Company. There are different mitigations to resolve the problems.

GREAT THINGS NEVER CAME FROM COMFORT ZONE

As employees have a tendency to resistance to change in the organisation. Also, IT industries not everyone is expertise in every technology (Conboy and Carroll, 2019). This is a common behaviour of the employees related to the task and technologies. It is very important for the employer to understand why an employee is resisting change and what are their feelings in adopting Scrum in the organization (Ramos et al., 2018). To resolve the issue leaders or employer must try to reach the roots of the problem so that the issue can be identified and re-plan to engage employees in the work. To resolve the issue, the organisation must hire the expertise of the technology which may help other team members to learn to learn other technologies effectively. The practicing of technologies with the help of training sessions may help Scrum teams to regain the interest on the new technologies and also improves the productivity of the Scrum team (Ramos et al., 2018).

EVERYONE MUST BE ON SAME PAGE

As the problem identified in the above section related to the Scrum distribution team. When it comes on assembling the team it is very important that the team must have trust and respect with each other. This may resolve the issue of communication in the companies (Shafiee et al., 2020). Respect and loyalty are very important in the IT Company as team members learn various technologies and skills with the team members. Generally, in IT companies, team members get ownership of their projects which helps the company to enhance their commitments or motivation level (Ramos et al., 2018).

Giving ownership to the team members is also important as they belong to the different nationalities and culture (Shafiee et al., 2020). So, it also motivates employees to be innovative with the project and work effectively. Scrum team also expects good co-ordination between team members and leaders in IT Company. This practical solution is very effective for an IT Company. Also, boot camps are very effective as this allows teams to gang up on the same location and discuss the problems that employees face while working in the team (Shafiee et al., 2020). Meeting with the members also creates enthusiasm in the team members and changes the working environment. Also, in IT companies, it is not possible for everyone to learn the technologies by sitting at the different locations. So, boot camps are effective in order to enhance the skills of the employees (Ramos et al., 2018).

Another solution for the distribution team is bridging time differences (Shafiee et al., 2020). The employees working in the IT Company from different locations, it is very important for them to overlap the time to clear misunderstanding or to resolve their issues (Karabulut and Ergun, 2018). In this situation, every member working in the IT Company must have screen sharing technologies and video conferencing facilities. This would allow employees to do instant message to their professionals related to any issue (Ramos et al., 2018).

PLAY IT BY RULES

In IT companies, conferences and meetings are very important but at the same time, it is very time-consuming. This may affect the interest of the other team members who are not connected with it (Kuhrmann et al., 2017). A solution for the problem is playing it by rules. An effective Scrum team must understand the purpose of the meeting and their responsibility. The responsibility of the team member is to maintain discipline and focus on the conversation as they could also face the same issue in future (Karabulut and Ergun, 2018). Daily meetings allow team members to understand their daily work and activities. Apart from this, other issues could be resolved personally when Scrum meeting is closed or by involving the connected parties which would save the time of other members (Kuhrmann et al., 2017).

The other possible solution for the leaders to check what team members do daily in the company, must create board in which the task should be recorded. Also, it is very easy for the IT Company to ensure that employees must record their issues on board which would be seen by the leaders or professionals and reach the team member soon to resolve the issue (Kuhrmann et al., 2017).

FIX TIME FOR BUGS

As the problem stated above that Scrum allows clients to add up or change their requirements related to the project which creates an unwanted disturbance in the team and affects the productivity of the team members (Karabulut and Ergun, 2018). To resolve the issue, the Scrum team must fix the time of accepting requirements. This would not waste the time of the team members. Reaching at the last stage of development and changing the requirement may affect the mind-set of the employees. Thus, it is a good idea for the team to fix the time before allocating the schedule to complete the project (Kuhrmann et al., 2017).

DEVELOPMENT AND TESTING SHOULD BE INTEGRATED

As the common challenge face by Scrum testing team of testing the product in short duration, this affects the quality and efficiency of the software (Karabulut and Ergun, 2018). The solution is testers should be connected with the developers on every stage which helps them to test the feature easily. Also, the team must approach to the quality check department on daily basis related to the quality of the product this would allow the team to change the feature if it does not work. The development team must not wait for the last moment to change the feature (Karabulut and Ergun, 2018). Also, the solid feedback of the testers will improve the feature in a way that it would be so effective to improve the quality of the product. Also, the organisation must encourage developers to test the products in smaller chunks as it also reduces the work overload. Once the smaller piece of work goes on testing, it also relaxes both tester and developer (Kuhrmann et al., 2017).

LITERATURE GAP IN STUDY

The literature review contains the information on practical challenges faces by the organisation in implementing scrum in the organisation. to achieve the aim of the research, researcher has designed the objectives of the research which are to identify Scrum management practices in small scale organisation; evaluate the benefits of Scrum in the organisation; to determine the practical challenges that the companies face to implement Scrum and to identify how agile will evolve to be the leading methodology in the software industry. The literature review has covered three objectives and does not contain any information about how agile methodology could be evolve in software industry in future. This objective would be covered in the primary research which will allow researcher to complete the research in an effective manner.

There are various articles available on the topic such as “Adapting the Scrum Framework for Agile Project Management in Science: Case Study of a Distributed Research Initiative” by Hidalgo (2019); “Learn How to Scrum with The Best of them” by ATLASSIAN’S agile coach; “Is Agile Scrum Methodology Right for The Business” by Angeles (2019) and “The Challenges of Implementing Agile Scrum in Information System Project” by Muhamd et al (2018). The researcher has collected the information from these articles to understand the topic thoroughly. To meet the objectives of the research, the researcher needs to read more articles based on the study to enhance the knowledge and make the report effective. The research is important from the aspects of academic purpose as the topic is not much familiar with the students and there are very less researches has been done by the other researcher in past. Thus, the completion of the research will give an opportunity to the students to collect the information on the topic and enhance their knowledge.

CONCLUSION

From the literature review, it is concluded that Scrum methodology plays a very crucial role in the IT Company to increase the effectiveness of the team. The literature review was effective in meeting the objectives of the research such as Scrum management practices in small scale organisation; evaluate the benefits of Scrum in the organisation and practical challenges that the companies face to implement Scrum. The data collected in the literature review is very effective to understand how Scrum affects the success of the organisation positively.

REFERENCES

Alavandhar, J.V. and ?ikiforova, O., 2017. Several Ideas on Integration of SCRUM Practices within Microsoft Solutions Framework. Applied Computer Systems, 21(1), pp.71-79.

Beerbaum, D., 2019. Applying Agile Methodology to regulatory compliance projects in the financial industry: A case study research. Journal of Applied Research in the Digital Economy (JADE), Special Issue, 2.

Conboy, K. and Carroll, N., 2019. Implementing large-scale agile frameworks: challenges and recommendations. IEEE Software, 36(2), pp.44-50.

Hidalgo, E.S., 2019. Adapting the scrum framework for agile project management in science: case study of a distributed research initiative. Heliyon, 5(3), p.e01447.

Karabulut, A.T. and Ergun, E., 2018. A new way of management: A scrum management. International Journal of Commerce and Finance, 4(2), pp.108-117.

Klünder, J.A.C., Hohl, P., Prenner, N. and Schneider, K., 2019. Transformation towards agile software product line engineering in large companies: A literature review. Journal of Software: Evolution and Process, 31(5), p.e2168.

Kuhrmann, M., Diebold, P., Münch, J., Tell, P., Garousi, V., Felderer, M., Trektere, K., McCaffery, F., Linssen, O., Hanser, E. and Prause, C.R., 2017, July. Hybrid software and system development in practice: waterfall, scrum, and beyond. In Proceedings of the 2017 International Conference on Software and System Process (pp. 30-39).

Kumar, G. and Bhatia, P.K., 2012. Impact of agile methodology on software development process. International Journal of Computer Technology and Electronics Engineering (IJCTEE), 2(4), pp.46-50.

Larman, C. and Vodde, B., 2016. Small-scale scrum: More with LeSS. Addison-Wesley Professional.

Maruping, L.M., Venkatesh, V. and Agarwal, R., 2009. A control theory perspective on agile methodology use and changing user requirements. Information Systems Research, 20(3), pp.377-399.

Maximini, D., Maximini and Rauscher, 2018. Scrum Culture. Springer International Publishing AG, part of Springer Nature.

Miler, J. and Kaidy, K., 2018, September. Problems and solutions of software design in scrum projects. In 2018 Federated Conference on Computer Science and Information Systems (FedCSIS) (pp. 975-978). IEEE.

Nowosielski, K., 2018. Benefits of utilising Agile Scrum Management in Web Development projects: A case study at Mirum Agency.

Oprins, R.J., Frijns, H.A. and Stettina, C.J., 2019, May. Evolution of Scrum Transcending Business Domains and the Future of Agile Project Management. In International Conference on Agile Software Development (pp. 244-259). Springer, Cham.

Pfeffer, J. and Berchez, J.P., 2017. Agile working practices with scrum. ATZelektronik worldwide, 12(5), pp.52-55.

Ramos, F.B.A., Costa, A.A.M., Perkusich, M., Almeida, H.O. and Perkusich, A., 2018, July. A Non-Functional Requirements Recommendation System for Scrum-based Projects. In SEKE (pp. 149-148).

Shafiee, S., Wautelet, Y., Hvam, L., Sandrin, E. and Forza, C., 2020. Scrum versus Rational Unified Process in facing the main challenges of product configuration systems development. Journal of Systems and Software, 170, p.110732.

Shafiee, S., Wautelet, Y., Hvam, L., Sandrin, E. and Forza, C., 2020. Scrum versus Rational Unified Process in facing the main challenges of product configuration systems development. Journal of Systems and Software, 170, p.110732.

Singh, R., Kumar, D. and Sagar, B.B., 2019, November. Analytical study of agile methodology in information technology sector. In 2019 4th International Conference on Information Systems and Computer Networks (ISCON) (pp. 422-426). IEEE.

Srivastava, A., Bhardwaj, S. and Saraswat, S., 2017, May. SCRUM model for agile methodology. In 2017 International Conference on Computing, Communication and Automation (ICCCA) (pp. 864-869). IEEE.