Application Development Process - Assignment Example

The work Affiliation Application development process can take different approaches. Some of the most popular approaches include the agile method and the Waterfall model. Because of the software development complexities and varying project objectives as well as stakeholders, none of the two approaches can be considered superior to the other. This paper seeks to prepare project outlines for mobile application development using the two approaches. Mobile application development outline – waterfall model application REQUIREMENTS -14 days conducting of analysis of needs -5 daysSketch preliminary application specifications- 3 days developing the initial budget – 2 days reviewing of the application/budget with the team – 4-day Incorporation of feedback on application stipulation – 1-day Development of timeline for delivery – 1 day obtaining the approvals for proceeding (timeline, concept) – 4 daysSecuring resources that are required – 1-day system DESIGN - 14.

5 daysReviewing of application stipulation – 2 daysDevelopment of functional stipulations – 5 days Developing of the prototype on the basis of functional stipulations – 4 daysReviewing of functional stipulations – 2 daysIncorporation of the feedback into functional conditions – 1 dayGet approval for proceeding – 4 days (Microsoft, 2013). MOBILE APLICATION DEVELOPMENT – Agile methodPROJECT KICK OFF – 6DAYSTeam formation – 6 daysIdentification of skill requirements – 2 daysResources identification – 2 daysAssignment of functions to resources – 2 daysENVISIONING-44 daysDefinition of initial requirements – 29 daysManagement of risk – 1 dayDEFINATION OF STRUCTURE OF THE PROJECT – 9 daysDefinition of project tracking process – 5 daysDefinition of solution process for the problem - 4 daysIssue tracking process definition – 3 daysChange control procedure definition – 4 daysAccountability and expectations definition – 2 daysRESEARCH AS WELL AS GATHER ASSUMPTIONS – 26 daysConducting initial user interviews – 2 daysUsage scenario definition – 10 daysPreliminary user profile development -5 daysPreliminary vision statement development – 1 dayDesign goals establishment – 8 days Preliminary solution concept development – 5 days (Mcrosoft, 2013).

DIFFERENCES BETWEEN THE TWO MICROSOFT OUTLINESAgile has made use of short iterations called prints, which last longer. Requirement confirmation is done, development and testing of the application are done and released in the course of the iteration and the next begins. Waterfall used stages. With a waterfall, once the stage is over there is no going back except if a process change is followed which can take longer. In the case of Agile, where requirements are in need to change, then they are handled better with the process.

Waterfall roles generally differ from those of agile. Agile does have the role known as a scrum master is a type of project manager as well as release manager and may fail to be an IT specialist. Waterfall does have a traditional manager of the project who happens to be an IT person always in the sense of tradition. With agile, the application is tested at the end of every stage. With waterfall testing of the application is done at the end of the process. What is needed ideally is a model that combines both the predictability as well as accountability of the waterfall approach with the agility as well as adaptability of the agile approach.

An effective balance between both ideas could come up with a much more efficient model for software development.