As the Chief Information Officer, it is important to distinguish the advantages and disadvantages for different application methodologies. Since the company does not want to remain with SDLC, I am required to recommend either Joint Application Development (JAD) or Rapid Application Development (RAD). Therefore, I will provide information and allow the company president to make a decision based upon my research. JAD is a methodology that uses the design and development processes of an application. It is an information gathering technique used to design and develop computer-based systems. RAD is a shorter version of JAD; it reduces the time taken to develop an application (UMSL, 2014). The disadvantages of JAD are actually strengthening to a project; they just require a lot of accuracy. JAD require significant planning and scheduling to ensure the project is on task in correlation to the project plan. Furthermore, it involves much time and effort of stakeholders. For a successful project, JAD demands experienced and trained personnel (Directutor, 2010). On the contrary, the advantages of JAD are very relaxed and unrushed. It allows time for the gathering and reviewing large amounts of information. In result, high quality work may be produced. Discrepancies can be properly handled. Finally, team communication is increased. Overall, time is the number one advantage associated with JAD (Directutor, 2010). The disadvantages of RAD software development are that it should not be used for complex projects. Since it is a rapid development, teams must be motivated and determined to work towards the vision of the project. Furthermore, produced quality may have to be sacrificed in order to meet the project’s life cycle. In addition, RAD requires a lot of technical skills from the developers (PM Expert, 2009). On the other hand, the advantages of RAD are very beneficial. The time of a project is reduced, ultimately saving resources. Prototypes can be reused from project to project. It is much easier to estimate project costs and controls. It decreases the overall price for the minimum budget. Normally used with repositories to save time and money as a result. Lastly, this type of development ensures the project is constantly moving forwards and maximizes team participation (PM Expert, 2009). In my opinion, JAD and RAD are used in different situation depending on the team’s and stakeholder’s timeframe and/or deadline. JAD is more of a longer process which includes high quality. RAD is a shorter process that sacrifices quality for time. In result, the advantages and disadvantages of each methodology are greatly impacted by project visions and goals. I recommend applying JAD when possible and used RAD as a second resort. I would only sacrifice quality for less time as needed; not as a primary development. JAD is more useful when time is not of the essence while RAD is. RAD is more useful when money is an issue while JAD is not. Is it worth giving up quality to save time; is it worth giving up quality to save money? Is quality not a money maker? “Quality is never an accident. It is always the result of intelligent effort.” – John Ruskin (Brainy Quote, 2014). Reference
Brainy Quote. (2014). “ John Ruskin.” Retrieved from: http://www.brainyquote.com/quotes/quotes/j/johnruskin130005.html
Directutor. (2010). “Joint Application Development (JAD) Technique.” Retrieved from: http://www.directutor.com/content/joint-application-development-jad-technique
PM Expert. (2009). “The Advantages and Disadvantages of RAD Software Development.”
Retrieved from: http://www.my-project-management-expert.com/the-advantages-and-disadvantages-of-rad-software-development.html
UMSL. (2014). “Systems Development Methodology – JAD and RAD.” Retrieved from: http://www.umsl.edu/~sauterv/analysis/488_f02_papers/JADandRAD.html