Adaptive Development Methodology
Software and systems have emerged as one of the major tool for the development of the organisations because of the ease in operations they offer. Hence, to leverage the technology Odd Jobs Ltd. is planning to develop a system for their operations. The first step in the development process is designing and development of the mobile application to support its contracting staff in updating job details after they have been completed. The mobile application will assist the contracting staff to detail the job by adding customer details, vehicle and their operational details along with other details. Hence, the report in discussion is aiming to discuss the adaptive methodology for software development because Collin Gray, manager believes that it is suitable for the development. Thus the following sections have discussed adaptive methodology and its types along with their pros and cons with suitable recommendation for the selection of adaptive methodology.
The development of a system needs to account for the requirement of the system which may vary with time. The variable needs to be induced in the system so that it can offer relevance to the organisation. One of the methodology that offers integration of change to the system during its development phase is the adaptive methodology. The methodology acts in phases and after each phase the system is tested for flaws and additional requirement. Based on the testing results and the requirements that needs to be added the next phase of the system development is proceeded with. The adoption of this methodology offers many benefit to the system owner, the first and foremost is that the system will be flawless and will offer effective and accurate results because of the continuous testing. Hence, the discussion above can be summarised to state that the discussed methodology is client driven as the client can add requirement during the system development phase which can also be emphasised to state that it change thriving in nature. The change thriving nature of the methodology is to induct new tools and technologies to mitigate the threat identified in the tests post completion of each phase. Additionally, as changes are continuous during the system development phase along with changes that are inducted in the system it would be justified to state the system as a learning methodology. Hence, the methodology is change thriving, client driven and learning methodology that offers prominent advantage to the system developers and the owners.
Scrum Development Methodology
Scrum development methodology is an adaptive framework that is used for management, development and completion of complex projects through iterative development. The approach offers the developers and clients with the advantage of meeting unpredictable changes at any phase of the product development. It attains the discussed objective by adopting innovative approach to meet up with the unpredictable challenges and also maintaining the presence of the client at every phase of the development and designing. The presence of client is maintained by receiving their feedbacks and responses at every stage based upon which the changes are made to improve the system. The followers of the discussed methodology are more devoted towards resolving the problem by maximisation of the team effort rather than understanding the problem. This approach ensures that the team is working towards a common goal and no personal agenda or objective will influence the final outcome of the project. Though, it should be noted that the methodology along with certain strong points in the development of a project also exposes certain weak points and they have been discussed below in the table as pros and cons of the methodology.
|
Pros |
Cons |
|
Involvement of client and stakeholders for the development of quality product. |
Scope creep can be developed due to unavailability of any deadline. |
|
The result development is rapid and the development is easily testable. |
The adding and removing of requirement during the development phase can add to the cost and delivery time. |
|
Regular meeting as part of the project development enables sharing of progress update and identifies any additional need that is to be added or removed. |
It demands a committed team and is feasible for small team sizes only. Leaving of the team member will pose an adverse impact o the project. |
|
Scheduled delivery of the product is ensured and is also budget friendly. |
Novice team members cannot leverage the methodology. |
|
The level of flexibility in development phase is high. |
High pressure is imposed on the team member. |
|
The level of transparency is very high. |
Table 1: Pros and Cons of Scrum
(Source: Created by Author)
Like the above discussed methodology, it is also aimed at improving the final delivery by accumulating and responding to the changing needs of client. The discussed methodology differs from the above by believing in the idea that documentation and meetings are waste of time rather verbal communication is enough to understand the needs and convey message. The time saved from avoiding the meetings should be utilised in focusing on the product development. The pros and cons of the methodology has been listed as follows:
|
Pros |
Cons |
|
Cost friendly because it avoid certain activities to focus on the main work saving time and cost. |
The changing cost and scope deems need for detailed planning. |
|
Use of pair programming techniques mitigate the risk by mitigating dependency on an individual. |
It does not measure the quality of the product and rather focusses on the functionality. |
|
The simplicity of the methodology brings robustness into the final delivery with less or no flaws. |
Due to the presence of pair programming, it can lead to duplication of data and codes. |
|
XP uses the user stories at the initial phase and a continuous feedback offers a dependable outcome. |
It is hard to adopt because it will require team discipline and customer devotion. |
Table 2: Pros and Cons of XP
(Source: Created by Author)
Recommendations/ Conclusion
Both Scrum and XP have their share of advantages and some of them are common. However, both of them differ in terms of the operations of project and the advantage of budget friendliness, robustness and risk mitigation offers a more reliable outcome and hence XP is recommended for the app. Though measurement and detailing of the project should be given proper attention to attain relevant results.
To: Odd Jobs Ltd.
From: Name of the Student
CC: Name of the Professor
Address: Name of University and Address
Subject: Requirement Gathering Plan for System Development
Date: Date of Submission
The memo is aimed at offering the plan and measures that will be adopted for the gathering of the requirements for the development of the system to support the operations of the Odd Jobs Ltd. This step needs proper detailing because based on the collected requirement the accuracy of the developed app will depend. Therefore, the approaches and plan for requirement collect ion have been discussed in the sections below.
Pros and Cons of Scrum
Description of Requirement Gathering:
The requirement will be gathered through two different means the first being case studies and reviewable of the similar apps and systems that are being used by different organisations. The second will be by understanding the requirement of the business. The business requirement will be understood by conducting a survey whose participants will be the organisational employee, management and the customers. The benefits of conducting the survey would be that the employee, customer and the business owners will be able to discuss their requirement based on which necessary list of requirement can be developed. The requirements can then be filtered and summarised to identify the crucial requirements for the development of the system. These requirements are crucial because the developed app will be used by the respondents of the survey and hence, it becomes necessary that they are comfortable with the app and it is useful for their purposes. The reviewable of the apps that are similar in nature and is being used by different organisations will enable brainstorming and based on that the features of the offering can be enhanced to includes more operations with a high level of accuracy. Hence, both of the methods are crucial and feasible for the collection of requirements.
The first step that includes studying of the case studies and reviewing of similar apps will be done by collecting resources from online sources. However, it should be noted that only reliable sources available will be considered. The reliable sources refer to peer reviewed articles and the case studies that are available on the blogs of trusted firms such as Google, Amazon, Microsoft and others. Post collection of the generalised requirement the second approach will be to compare and contrast the data with the business requirement. It can be done by distributing a survey form to the firm’s stakeholders. The collection of requirement from the survey will then compared and contrasted with the other data collected from internet sources. The final finding will be considered as the requirement for the app development.
Making of the application will be more suitable because the developed app will then be reach in features at a global scale and will also support the ecosystem of the firm and its associates. The development of the app will also cost less for the firm than buying. Additionally, maintaining of the application will also be simple because it will be a home developed and hence, the details about the app will be available with the firm. The training process of the employee will even receive a buff due to the making of data. However, it should be noted that the investment of the resources, effort and time will be high. If the firm wish to reduce the effort, resource and time investment then they can buy the application from a trusted app vendor.
It is recommended that the firm should devote at least a month in requirement collection and filtration of the data to have a well-depended outcome and should store it will adequate attention to prevent any loss in requirement. Another recommendation would be to own an in-house developed application so that they get a ease of maintenance, budget and training of the app along with its use.
Abdelaziz, A.A., El-Tahir, Y. and Osman, R., 2015, September. Adaptive Software Development for developing safety critical software. In Computing, Control, Networking, Electronics and Embedded Systems Engineering (ICCNEEE), 2015 International Conference on (pp. 41-46). IEEE.
Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J., 2017. Agile software development methods: Review and analysis. arXiv preprint arXiv:1709.08439.
Kniberg, H., 2015. Scrum and XP from the Trenches. Lulu. com.
Matharu, G.S., Mishra, A., Singh, H. and Upadhyay, P., 2015. Empirical study of agile software development methodologies: A comparative analysis. ACM SIGSOFT Software Engineering Notes, 40(1), pp.1-6.
Theocharis, G., Kuhrmann, M., Münch, J. and Diebold, P., 2015, December. Is water-scrum-fall reality? on the use of agile and traditional development practices. In International Conference on Product-Focused Software Process Improvement (pp. 149-166). Springer, Cham.
Turk, D., France, R. and Rumpe, B., 2014. Limitations of agile software processes. arXiv preprint arXiv:1409.6600.
Order an Essay Now & Get These Features For Free:
Turnitin Report
Formatting
Title Page
Citation
Outline
