This report comes as a feedback to the request of Odd Jobs Limited Manager Colin Grey to expound on the knowledge of implementing the new mobile application using adaptive software development methodology. The report discusses adaptive software development methodologies, its pros and cons and further expounds on two major adaptive software development methodologies; Scrum and Extreme programming. The circumstances under which scrum and extreme programming are used, their advantages and disadvantages are indicated in the report. The report further gives a recommendation on what adaptive software methodology, between Scrum and Extreme Programming, should be used by Odd Jobs Limited.
Adaptive software development methodology is based on the adaptation and compatibility concepts of software development, where the developing a system starts with the various modules of the software. The development process then implements and incorporates new user and system requirements as it progresses to completion. For Odd Jobs Limited, the development will start with implementing a mobile based application for contracting staff then will later implement a customer relationship system. This makes adaptive software development methodology incremental and iterative in nature (Satzinger, Jackson and Burd 2011).
It is Adaptive according to Rahimian and Ramsin (2008, June). Adaptive software development methodology as the name suggests, adapts to new user and system requirements as the development proceeds to completion. This ensures that the new OJL mobile application will accommodate storage of customer information, management of vehicles and generation of reports.
Development is simple. During the development of OJL mobile application there is no need for much documentation of requirements and details, the development process starts with the immediate requirements specified by the user.
Feedback is given in the manner of the frequent releases. The frequent releases enable users to establish user stories that have been implemented adequately, those that have been partially implemented and those that have not been implemented at all. This gives the team of developers a chance to get a good grasp of the requirements that need to be implemented and by doing so all the requirements of the OJL mobile application will be catered for.
Association of users, the users will be involved in the development process from the begin of the OJL mobile application development process. The frequent releases where the team of developers get response on the release from users makes it possible for the team of developers to successfully implement the requirements for the system.
Realization of quality, effective and efficient software, with all the functional and non-functional system requirements of OJL mobile application realized, the application generated is of high quality.
It is costly to implement OJL mobile application using adaptive software development methodology. First the development process requires experts who are highly skilled. Paying these experts is quite expensive.
There is no proper documentation of the requirements of OJL mobile application (Williams, 2010). The requirements will always be evolving and increasing. This makes it difficult for maintenance of the mobile application by a different team of experts.
The scope of the mobile application development project for OJL is not defined. The time the development process will take to run to completion is not definite. The development process may take years and years accommodating new requirements.
Scrum is an iterative incremental software development process that will partition OJL mobile application development process into sprints like get customer information, manage vehicles and generate reports. These sprints are like units or modules broken down from the whole project development process (Dyba and Dingsoyr, 2009). Before each sprint the development team has to have sprint planning where a sprint’s objectives are determined and set. After each sprint is when there is a sprint review where what has been developed is checked against the objectives set and the parts of the sprints that are done are presented to the stakeholders. A sprint retrospective is then held to establish what improvements need to be done.
Stakeholders of the project are Odd Jobs Limited who have hired a team of developers to develop the mobile application, customers or users of the mobile application, the team of developers who are responsible for the coding part of the implementation process and the Scrum Master who is the coach of the team of developers and acts as intermediary between the team of developers and Odd Jobs Limited Management.
When there is no dependence of the mobile application of OJL on other external or out sourced modules.
When the team of developers hired by OJL, are in one physical location
When the team of developers consists of experts from different areas of expertise
Compatibility, being an adaptive software development methodology, scrum accommodates user requirements as they evolve all along the development process (Petersen and Wohlin, 2009). This makes it certain for all the requirements of OJL mobile application to be accommodated.
Tool-independence, any tool can be used to develop the mobile application for OJL using scrum software development methodology.
Holding of the daily scrum meetings where the development proceedings are tracked enables identification and correction of errors. This prevents error propagation throughout the mobile application development process.
Realization of quality, effective and efficient software, with all the functional and non-functional system requirements of OJL mobile application realized, the application generated is of high quality.
The scope of the mobile application development project for OJL is not defined. The time the development process will take to run to completion is not definite. The development process may take years and years accommodating new requirements.
It requires a team of very skilled experts in different areas of specialization.
Extreme programming involves extreme coding (West, Grant, Gerush and D’Silva, 2010), of OJL mobile application throughout the development process. The process consists of coding the units, testing of the codes, negotiations, holding meetings and acceptance testing. The units; customer registration and management, vehicle registration and management and report generation are first coded, then each is tested in unit testing then deployed after acceptance testing.
When the team of programmers consists of two to twelve members and not more than twelve
When there is a high risk of developing the new OJL mobile application, XP comes in to reduce the risks involved.
The unit testing (Turk, France. and Rumpe, 2014), where all the modules and units are tested for errors ensure there is no error propagation during the development process.
Compatibility, being an adaptive software development methodology, extreme programming accommodates user requirements as they evolve all along the development process. This makes it certain for all the requirements of OJL mobile application to be accommodated.
Adherence to change, the development team is always willing to listen and implement new user stories. When the time comes the development team will implement the customer relationship module for OJL mobile application.
It is costly to implement because it requires highly skilled experts who are very expensive to hire.
There is no proper documentation of the requirements of OJL mobile application. The requirements will always be evolving and increasing (Livermore, 2008). This makes it difficult for maintenance of the mobile application by a different team of experts
Odd Jobs Limited should choose Extreme programming to implement the new mobile application. This is because extreme programming offers extreme coding which will enable accommodation of all the functional and non-functional requirements of OJL mobile application. It will also enable mitigation of errors at an early stage during the implementation process. This will be realized through the unit tests done at the unit level.
Satzinger, J.W., Jackson, R.B. and Burd, S.D., (2011). Systems analysis and design in a changing world [online]. 1st November 2011. Cengage Learning. Pp.244. Available from: https://books.google.co.ke/books?hl=en&lr=&id=eRQKAAAAQBAJ&oi=fnd&pg=PR3&dq=Satzinger,+J.W.,+Jackson,+R.B.+and+Burd,+S.D.,+2011&ots=ssBzwMrmqW&sig=V8oDy2zbDpXzTdySmbkB565nmsw&redir_esc=y#v=onepage&q&f=false [Accessed 30 September 2018]
Rahimian, V. and Ramsin, R., 2008, June. Designing an agile methodology for mobile software development: A hybrid method engineering approach. In Research Challenges in Information Science, 2008. RCIS 2008. Second International Conference on (pp. 337-342). IEEE.
Williams, L., 2010. Agile software development methodologies and practices. In Advances in Computers (Vol. 80, pp. 1-44). Elsevier.
Petersen, K. and Wohlin, C., 2009. A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case. Journal of systems and software, 82(9), pp.1479-1490.
Dyba, T. and Dingsoyr, T., 2009. What do we know about agile software development?. IEEE software, 26(5), pp.6-9.
West, D., Grant, T., Gerush, M. and D’Silva, D., 2010. Agile development: Mainstream adoption has changed agility. Forrester Research, 2(1), p.41.
Turk, D., France, R. and Rumpe, B., 2014. Limitations of agile software processes. arXiv preprint arXiv:1409.6600.
Livermore, J.A., 2008. Factors that Significantly Impact the Implementation of an Agile Software Development Methodology. JSW, 3(4), pp.31-36.
Essay Writing Service Features
Our Experience
No matter how complex your assignment is, we can find the right professional for your specific task. Contact Essay is an essay writing company that hires only the smartest minds to help you with your projects. Our expertise allows us to provide students with high-quality academic writing, editing & proofreading services.
Free Features
Free revision policy
$10Free bibliography & reference
$8Free title page
$8Free formatting
$8How Our Essay Writing Service Works
First, you will need to complete an order form. It's not difficult but, in case there is anything you find not to be clear, you may always call us so that we can guide you through it. On the order form, you will need to include some basic information concerning your order: subject, topic, number of pages, etc. We also encourage our clients to upload any relevant information or sources that will help.
Complete the order form
Once we have all the information and instructions that we need, we select the most suitable writer for your assignment. While everything seems to be clear, the writer, who has complete knowledge of the subject, may need clarification from you. It is at that point that you would receive a call or email from us.
Writer’s assignment
As soon as the writer has finished, it will be delivered both to the website and to your email address so that you will not miss it. If your deadline is close at hand, we will place a call to you to make sure that you receive the paper on time.
Completing the order and download