Selection of Suitable Development Process

o  Waterfall process (Cobb, 2011)

ü Waterfall model is like the assembly line process. It has unique goals for each stage. Each step-in development moves in one direction without any chances of overlapping.

§ The good thing is you freeze the requirement early in the process and concentrate on the next steps of the cycle later.

§ The bad thing is after you are done with your work, you don’t have a lot of scope for expansion. As you would have already exhausted budget and time.

§ Also, once you are done, there is hardly any scope of changes or retrospection, that is where the maintenance phase kicks on.

o  Rapid Application Development (IMM006 RAPID APPLICATION DEVELOPMENT)

ü RAD is a mix of Waterfall and Agile. You freeze the requirements early in the process and then work on designing and coding part in an iterative fashion. Once it's all done, then you finish the testing.

§ The good thing is that it reduces cost without compromising the quality by effectively reducing the project duration as well as the number of resources involved in a project.

§ Another good part is that it involves customer from the beginning of the development lifecycle. Which ensures full acceptance from the customer.

§ The bad thing is that it tends to have more focus towards the delivery deadline, and in the process compromises on the features and functionality.

o  Agile Process

ü Agile is the most fluid process. You pick one requirement at a time and finish it, from start to end. Once that’s done, you come back, pick a new functionality and start work on it.

§ The good thing about Agile is, the waste is constantly monitored and then you must fix it.

§ Another good thing is, the end of the sprint gives you a shippable application.

§ The focus is more on the resources and meeting in person (Face-to-face).

o  Selecting a Process

ü I have tried to use the methodology selection criteria from the course material provided. (Braude, 2017)

Rating 1 = Poor, 2=Medium, 3=Good, 4=Excellent

Based on the above table I would consider a combination of following processes - Waterfall and a Phased Agile.

ü Why Waterfall:

ü We know the requirements well in advance-

o  promote loyalty, award points on every $ spent.

o  make purchase suggestions based on past purchases, based on the history and the time of the new purchase.

o  specific coffee flavor and breakfast item will be offered combined savings, like a coupon for buy one get one.

o  integrate with social media to provide a review of the drink or the drink ordering process ordered on the app.

ü We also know the time duration-

o  Initial delivery is to be in four months

ü Why will it work best?

ü We have the advantage of knowing the requirements way ahead in the game.

ü Documentation-

o  Since we have just two developers onshore and rest of them are distributed and are in different time zones.

ü Why a Phased Agile (combination of Phased(RAD) and Agile)

ü We know the duration of sprint and what needs to be done-

o  features will change as often as every two weeks.

o  to better fit customer use

ü We are not sure of certain features though and how are we going to achieve it-

o  should be as easy as possible to modify by IT.

o  may be extended in the future to contain dashboard features.

o  served by several internally managed servers or if it will be cloud-hosted.

ü Why will it work best?

ü Because we need to release new features every two weeks.

ü And some of the features will change as we get feedback from the customers.