Agile Manifesto Case Study

1Agile Manifesto” in which they defined a set of principles [68] Table 2.1 Agile Manifesto Agile Manifesto ID Description M1 Satisfying the client via immediate and uninterrupted delivery of software is our utmost priority. M2 Welcome varying requirements, even at maturity level of development. M3 Deliver functioning software normally, 1with a preference to the shorter timescale. M4 Professional people and developers must be functioning together daily to throughout the project. M5 Build projects around motivated individuals. Give them the environment and support they need , and trust them to do the job M6 The most effective and operative way of conveying information to and within a development team is face-to-face conversation. M7 Working software
More clearly, 1for the Agile Manifesto and agile approaches which define unambiguous practices, these aspects can be seen as the result of using an agile practice from a certain subset of agile practices. We will describe each of these aspects by giving a description of what the aspect needs followed by a clarification of how exactly the aspect is reflected in the Agile Manifesto. A1 Close collaboration between the members of the development team A1 alarms that all participants of the development team should work together daily throughout the project in a very close way, while communicating regularly. This aspect is reflected in the Agile Manifesto in the following way: For one it urges that Professional people and developers must be functioning together daily to throughout the project (M4). 1For teams to be self-organizing the members need to work together closely. Lastly, it claims the most effective and operative way of conveying information to and within a development team is face-to-face conversation.
The Agile Manifesto emphasizes the importance of the customer in the development process. Again we refer to the fact that the Agile Manifesto Satisfying the client via immediate and uninterrupted delivery of software is our highest priority (M1). Also it states that Welcome varying requirements, even at maturity level of development (M2). 1Besides this also in the values of the Agile Manifesto the importance of this aspect can be seen, as these both mention the importance of customer collaboration and responding to change. A5 Collective ownership of work A5 involves that all the work is done is the product of whole team not of a single one. No one team participant owns, or is dependable for a particular code segment and whole work can be reformed by the team, without any permission. This feature also linked with the team having a shared vision and responsibility of the system to be built. The whole team is working together, aiming for a single goal and is collectively responsible that this goal is reached. This aspect is found in a indirect manner in the researched methodologies. Chao et al. [70] states numerous agile methods