|dc.description.abstract||Healthcare information technology is one of the fastest growing industries in the world. There are millions of errors made in the medical paper chart at hospitals around the world, resulting in mistaken medication and death. Healthcare information technology provides a way to eliminate these errors and to allow patients access to their medical record from anywhere in the world. Corporation X is the foremost leader in the industry and has been providing solutions to hospitals and doctors’ offices for the past 30+ years. Developing software that affects peoples’ lives requires many processes and certifications. As a result, the software development process is instrumental in providing high quality software for Corporation X’s clients.
In the past, Corporation X has employed the Waterfall Software Methodology to design and implement their software. This methodology or process has been in use since the beginning of software. There are distinct phases that need to be sequentially followed, requiring much up-front work. There are many advantages and disadvantages to this process. As the healthcare information technology industry grows and new competitors make their way to market, Corporation X has been forced to re-think this process and adapt to the ever-changing external environment.
The recent popularity of Agile Software Development has spread across the world. In the past 10 years, Agile has become the most used process for software development. In 2010, Corporation X decided to switch from Waterfall to Agile, to keep up with the industry and improve it’s own processes.
The advantages of the switch to Agile have proven to be a great asset to Corporation X’s engineering teams. The new process has increased code quality, increased client satisfaction, and produced more revenue for Corporation X.
There were, however, a few disadvantages such as resource pooling and team morale.. A new concept was introduced with Agile, resource pooling. This was Corporation X’s own spin on resourcing, not something that is traditionally a part of Agile practices at most companies. This proved to be a disadvantage because it caused teams to lose that camaraderie and closeness that is typical of a team. Engineers had to start over with people with every project. Corporation X also put a new defect accountability process in place to help drive down the number of defects by introducing the feeling of ownership. And with this new process, engineers became more aware of the number of defects being introduced to clients. All of these factors will be discussed and explained in this study. This study will help dissect the transition from Waterfall to Agile from the software engineers’ viewpoint.||