Scrum Methodology in Project Management: A Comprehensive Analysis for Holmes Software Technologies

HI5029

IS Project Management Individual Assignment

Student name:

Student Id:

Introduction

In this report, the scrum methodology in the project will be discussed with deep insights. The main objective of this project is to describe the clarity over and facilitate the overall understanding of the scrum methodology for Holmes software technologies. Several concepts of scrum methodology will be discussed in the literature review part. After that, a discussion part will be described in which the analysis of the literature review will be explained. In the last, there will be a conclusion statement that reflects the selection of scrum methodology for Holmes software technologies.

Literature review

Methods of scrum methodology

Daily Scrum

The daily scrum is a type of meeting that is a crucial part of the overall success of the scrum sprint. Daily scrum meetings are considered part of the regular scrum workflow. Daily scrum meetings are used to track the progress accordingly, the project manager will discuss the matters that can arise in the project. Daily scrum helps the team members to work upon the obstructions. Due to this, the team members will be able to make them prepare themselves for the future hurdles that can appear in the project. The team members of the project can pre-plan a strategy for future obstructions and make themselves ready to deal with the problem. Daily scrum can be better organized in the form of a meeting where the team members provide updates about the project. Daily scrum meetings must be short in time so that a correct conclusion can be made by project team members. Daily scrum meetings are the ones that reduce the complexity of uncertain problems. With the help of daily scrum meetings, the project team members will be able to sync the progress of their projects. Daily scrum meetings are a necessary part of the coordination of team members and task discussions (Dobrigkeit et al, 2021, p2(2)). In those meetings, team members will be able to share their perspectives on the project so that improvements can be made correctly.

Sprint planning

Sprint planning is a process by which a project management team uses it to determine what type of work will be completed and how it will be completed. It is very necessary that which work is essential for the team, that work will be completed first. If any project team is not able to decide which work needs to be completed first then they will waste lots of time on the work which is not so important. Scrum projects are the one which has to be completed within a short period. If not, then it will cost lots of expenses to the company which can be the loss factor for them. Due to the delay of the project, the customer will also not be satisfied with the company and provide negative reviews to them. Sprint planning is generally an event framework by which the team members decide the backlog of the product on which they will work.

Behavior-driven development

Behavior-driven development is a process that is gaining attraction currently in software industries. Business-driven development is an approach to the development of software. There are three principles on which the behaviour-driven development process focuses. The first principle describes the focus on desired behaviour, the second principle is the coordination between the developers, stakeholders of the business, and testers. The third principle is the utilization of a common language for communication and understanding. Business-driven development is a three-step process including the discovery, formulation, and automation phases. The first step which is discovery is inclusive of the goal in which the business has to deliver the project. The project must be delivered with high quality and will be discussed within the team meetings by team members. In this phase, it will be discussed what will be the customer demand and how it will be correctly assessed by them. In the second phase which is the formulation, the process of the project formulation will be done. The projects will be planned in such a way that they can be understood by every team member with observability and controllability (Tuglular & Co?kun, 2021, p230(7)). The third phase describes the process, which will show the example of the project and how it will be implemented in real-world scenarios.

Release planning

Release planning in scrum methodology is a process in which there will be the generation of the process which is of a very high-level plan for the multiple sprints of the scrum. Release planning refers to the guidelines reflect that what features need to be included in the project. Release planning also refers to the base planning for tracking the progress of the project. The iterative philosophy which is followed by the project team and their managers will come to a face which is release planning. Release planning g in scrum methodology is considered a crucial part of software development. Due to this, the team members will be able to deliver projects that are aligned with the goals of the business. This will ensure the project which is developed by the project team, meets the demands of the customer and the development process will be optimized.

Challenges in scrum methodology

Issues in module integration

There are chances of module integration issues because when the project was released very quickly by the project team, the testing could not be done. Due to that, issues can arise in the integration of the module. This will decrease the completion of the projects. Module integration is created more precisely which has to be matched with the optimum requirements of the client’s project (Wuni & Shen 2020, p4(2)). The testing process of the sprint requires lots of time to test. Without doing the full testing process, the project team members cannot get the exact quality assurance. Lack of quality assurance in the project can hinder the overall success factors of the project. Issues in the module integration can arise due to poor data communication. The testing of sprints is necessary, but many of the time the testing of the module integration becomes very complex. Due to the complexity, the modules cannot have clear communication between them. This affects the overall assurance of the project quality.

Quality issues in code

Code quality is a major factor in the development of the project. Code quality is a factor that helps to maintain the collaboration factor by which the projects adapt to the change quickly and easily. Lack of good collaboration leaders the less effective, then the team members of the product will not own the quality code practices. Less adherence to the code formation will decrease the progress tracking of the project. Due to that, the team members can find out the areas for improvement.

Teamwork disturbances

Disturbances in teamwork can be seen from various sources. The disturbance from technology-related issues can be the major issue. These types of issues impact the ability of the team members who were working on the project. There will be fewer teamwork disturbances when there is effective mentorship on the team (Iacob & Faily, 2020). Many times, the product owners introduce the changes according to their timing. The timing of introducing the new change in the project hinders the project's progress. The team members will not be able to focus on the ongoing process of projects which will directly impact the delaying of the projects. Every team member is working on the completion of sprint and the changes introduced by the owner will hinder the process of achieving the project completion on time.

Lack of backlog management

The backlog is the list of change requirements which is based on the customer’s needs and wants. The backlog is the expected list of customers they want in their projects (Houck, 2020, p317(1)). Project team members use the backlog lists which helps them to work on the project needs correctly. Due to the lack of backlog management in the scrum projects, the team members will not be able to focus on their project formation and competition. Technical limitations can also be the backlog items in future periods for project team members (Floru? & Buchmann, 2022). This is because when the priorities of the customer are not clear, then there will be no systematic way to work on the project. The completion date assigned for the project will be missed by the team members of the project. This will also decrease the overall quality of the project which will decrease the overall satisfaction of the customer. Team members of the project will be confused in their project formation and cannot move in the correct direction.

Project scope management strategies

Generation of project scope management plan

A project scope management plan is a process in which the project will focus on the needs and wants of the projects. Project scope planning helps to define which work needs to be prioritized by the team for the completion of the project. This is the step that reflects on the clarity over the goals, deliverables, and the other things on which the team of the project will work. When planning for the goals and other crucial things of the project, the team members and the project must prepare a plan in advance. This will help the team to deal with the uncertain changes. Due to this, the team members of the project will not have any bottlenecks in their formation and completion of the project. A scope management plan for the project is very essential for the timely completion of the project (Qiao, 2021, p62(2)). This is the strategy that aims to document the resources that are required for the achievement of project objectives.

Requirement gathering and defining the scope of the project

For successful project completion, the data must be collected by the team members in a systematic order. This will help to arrange the data in the correct order. The data must be collected based on the demands and requirements of the project. To work on the project more efficiently, the project team must look at the client's demands. According to that, only the team members must move to collect the data for the project. On the other hand, the stakeholder will not be able to make an approximation of their exact project features. For the exact result of the features for the project, a process can be followed. In that process, several tests will be done on the features that seem to be relevant in the context of the project. The feature which will be most relevant will be selected for the project.

Generating work breakdown structure.

Generating work breakdown is the process in which the various types of work will be divided into smaller parts. High complex tasks that need to be completed carefully, a work breakdown will be a good option. The task will be divided among every team member for efficient completion of the project. This is the strategy where the team members will focus on the deliverables more instead of the actions included in the project. Work breakdown structure describes the work and how it will be organized. Work breakdown structure is considered a crucial tool for the structuring of the project (Al-Kasasbeh et al, 2021, p13(1)). Also, the work breakdown structure facilitates the rapid development of the schedule through which work will be allotted without any hustles in it. Due to that, there will be a smooth flow of work for the completion of the project.

Discussion

In the literature review, it has been seen that scrum methodology is discussed in various aspects. Scrum methodology is the most flexible strategy which is the most affordable management solution for the management of the project in the company. Scrum methodology for Holmes software technology will be the most beneficial part by which they will be able to work effectively and efficiently on their client demands. It is the set of meetings, tools, and a type of framework for nth project teams in the company. When applied effectively in the company it will ensure the team members self-manage their work and can learn from the experience. After that, various aspects of scrum methodology define the overall understanding of the scrum methodology. It is inclusive of the challenges, methods, and scope management strategies for the project. In the methods, part of scrum methodology has been seen there are four major parts of the methods. The first method is the daily scrum planning. Daily scrum meetings enhance the communication process between team members of the project (Andersson, 2022, p5(3)). In this method, it has been discussed that it is a quick meeting process in which the team members of the project discuss and review the development of the project. The daily scrum is the method by which the project manager and team members discuss the obstruction that can arise in the future. With the help of that, the manager of the project and team members can create a plan in advance. They will be notified about that obstruction. The second method is sprint planning in which the discussion is about the planning of the sprints. This reflects the way of doing the work and how it will be done by the team members. This ensures a systematic way of completing the work. The project will not be delayed from the completion date given by the client. The third method is inclusive of behaviour-driven development in which the work is divided according to the knowledge and skills of the team members of the project. If any team member is an expert in a coding field, then that individual will be assigned to the work of coding quality. The second part of the literature review is about the challenges in scrum methodology. The Scrum framework assists in the evolvement of the team into a holistic movement (Reddy et al, 2021, p3(6)). The challenges are inclusive of issues in the integration of the module, issues in the quality of code, lack of management of backlog lists, and disturbances in teamwork. The coding that will be used for the project has issues in its quality then it will affect the project after the delivery to the client. Modules are the basis for the self-arrangement of the work. The challenge of backlog list management is the priority on which the team members work and the teamwork will be disturbed by the instant changes demanded by the client will delay the project formation and its effectiveness. The third part of the literature review was the scope management strategies for the project. These are the strategies that will help to improve the operations of the project that have been taken by the company. If Holmes Software Technologies wants to maintain its scrum project operations correctly then it works effectively on the challenges so that it may not have any complex problems future. The methods suggested earlier can be very beneficial in carrying out the operations of the project. If any obstruction arises uncertainly in the formation of the project, scope management strategies that have been described above can be used to tackle and manage them efficiently.

Conclusion

In conclusion, it can be seen that the scrum methodology is the most relevant methodology for Holmes software technology. For that, a literature review is described above which consists of the challenges, methods, and scope management strategies for the project. By adopting the methods of scrum mythology, Holmes software technologies will be able to work more efficiently for the project. Working on the challenges and preparing themselves in advance to deal with them will be the most appropriate option. Scope management strategies are a quick schedule for the changes which can appear indecisively. After that, a discussion part is explained in which the analysis of the literature review is described. With the help of that clarity will be there for the selection of the scrum methodology.

References

1. Al-Kasasbeh, M., Abudayyeh, O. & Liu, H. 2021. An integrated decision support system for building asset management based on BIM and Work Breakdown Structure, Journal of Building Engineering, 34, pp.1-41, https://www.researchgate.net/profile/Hexu-Liu/publication/345350510_An_Integrated_Decision_Support_System_for_Building_Asset_Management_based_on_BIM_and_Work_Breakdown_Structure/links/5fa4b270458515157bef9950/An-Integrated-Decision-Support-System-for-Building-Asset-Management-based-on-BIM-and-Work-Breakdown-Structure.pdf

2. Andersson, M. 2022. Paradox of the daily stand-up meetings in agile software development context (Bachelor's thesis, M. Andersson), pp.1-25, https://oulurepo.oulu.fi/bitstream/handle/10024/20199/nbnfioulu-202206213095.pdf?sequence=1

3. Dobrigkeit, F., Matthies, C., Teusner, R. & Perscheid, M. 2021. Joining forces: Applying design thinking techniques in scrum meetings, Design Thinking Research: Translation, Prototyping, and Measurement, pp.1-30, https://arxiv.org/pdf/2109.06578

4. Floru?, C. & Buchmann, R.A. 2022. Modeling Tool for Managing Requirements and Backlogs in Agile Software Development, In CEUR Workshop Proc, https://ceur-ws.org/Vol-3122/PT-paper-5.pdf

5. Houck, M.M. 2020. Backlogs are a dynamic system, not a warehousing problem, Forensic Science International: Synergy, 2, pp.317-324, https://www.sciencedirect.com/science/article/pii/S2589871X20300620

6. Iacob, C. & Faily, S. 2020. The impact of undergraduate mentorship on student satisfaction and engagement, teamwork performance, and team dysfunction in a software engineering group project, In Proceedings of the 51st ACM Technical Symposium on Computer Science Education, http://eprints.bournemouth.ac.uk/32927/1/SIGCSE20.pdf

7. Qiao, C. 2021. Project Completion Probability Analysis Based on Bayesian Network, Academic Journal of Engineering and Technology Science, vol.1, no.4, pp.62-69, https://francis-press.com/uploads/papers/RVCWqQiWa0uepb4ysQGkbmJVSAIjK2B6P24ISkDW.pdf

8. Reddy, P.C., Nachiyappan, S., Ramakrishna, V., Senthil, R. & Anwer, M.S. 2021. Hybrid model using scrum methodology for softwar development system, J Nucl Ene Sci Power Generat Techno, vol.10, no.9, pp.1-6, https://www.researchgate.net/profile/P-Chandrashaker-Reddy/publication/355986623_Hybrid_Model_Using_Scrum_Methodology_for_Softwar_Development_System/links/6189295a07be5f31b758f2cb/Hybrid-Model-Using-Scrum-Methodology-for-Softwar-Development-System.pdf

9. Tuglular, T. & Co?kun, D.E. 2021. Behavior-driven development of software product lines, In 2021 8th International Conference on Dependable Systems and Their Applications (DSA) , pp. 230-239, IEEE. https://dsa21.techconf.org/download/DSA2021_FULL/pdfs/DSA2021-1sP33wTCujRJmnnXDjv3mG/439100a230/439100a230.pdf

10. Wuni, I.Y. & Shen, G.Q. 2020. Barriers to the adoption of modular integrated construction: Systematic review and meta-analysis, integrated conceptual framework, and strategies, Journal of Cleaner Production, 249, pp.1-37, https://ira.lib.polyu.edu.hk/bitstream/10397/89197/1/Wuni_Barriers_Adoption_Modular.pdf