Applying Extreme Programming for Agile Project Delivery, Thesis of Programming Methodologies

The use of agile software development methodology, specifically extreme programming (xp), in software development. The methodology consists of four phases: planning, designing, coding, and testing. User stories are used to assess client needs and requirements, and acceptance testing is performed to ensure the software meets specifications. Small releases allow for feedback from clients and identification of bugs or errors. Agile teams organize work and define realistic scopes for iterations, and each team member has specific duties. Acceptance testing is the final phase before making the software available for use.

Typology: Thesis

2020/2021

Uploaded on 07/10/2022

pengesagot
pengesagot 🇵🇭

3.3

(3)

2 documents

1 / 3

Toggle sidebar

This page cannot be seen from the preview

Don't miss anything!

bg1
Software Development Methodology
The researchers used the Agile Model Extreme Programming
The methodology consists of four supporting phases: planning, designing, coding, and testing.
According to Ekaterina Novoseltseva (2020), an agile software development
methodology which is intended to improve software quality and responsiveness to changing customer
requirements. It emphasizes business results first and takes an incremental, “get something started”
approach to build the product, using continual testing and revision. It advocates frequent releases in
short development cycles, which is intended to improve productivity and introduce checkpoints at which
new customer requirements can be adopted. It really simplifies and speed up the process of developing
new software, making it possible to launch a new product as fast as possible with a solid MVP.
The researchers used Extreme Programming to reduce risk related to programming,
develop a finer way of design, lessen a project failure, and other aspects to help the researchers to build
improved development. The researchers might follow the steps or concepts of how the Extreme
Programming Model works.
User Stories - is a scenario, a description of a (potential) real use of a system. It takes the
customer or user perspective and represents a team’s shared understanding of what the system should
do. (Bill Wake 2021).
Using XP, the developers used user stories as a standard for their clients to accept the
application. The developers used user stories to assess the client’s needs and requirements before
pf3

Partial preview of the text

Download Applying Extreme Programming for Agile Project Delivery and more Thesis Programming Methodologies in PDF only on Docsity!

Software Development Methodology The researchers used the Agile Model Extreme Programming The methodology consists of four supporting phases: planning, designing, coding, and testing. According to Ekaterina Novoseltseva (2020), an agile software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. It emphasizes business results first and takes an incremental, “get something started” approach to build the product, using continual testing and revision. It advocates frequent releases in short development cycles, which is intended to improve productivity and introduce checkpoints at which new customer requirements can be adopted. It really simplifies and speed up the process of developing new software, making it possible to launch a new product as fast as possible with a solid MVP. The researchers used Extreme Programming to reduce risk related to programming, develop a finer way of design, lessen a project failure, and other aspects to help the researchers to build improved development. The researchers might follow the steps or concepts of how the Extreme Programming Model works. User Stories - is a scenario, a description of a (potential) real use of a system. It takes the customer or user perspective and represents a team’s shared understanding of what the system should do. (Bill Wake 2021). Using XP, the developers used user stories as a standard for their clients to accept the application. The developers used user stories to assess the client’s needs and requirements before

coding the program. This way the developers can save time thinking about features and criteria for their clients to like the system. User stories are also used to gauge release planning in meetings in the XP structure. In this stage, the researchers together with their clients arranged a meeting to plan, brainstorm, and collaborate in designing and implementing the proposed application. The researchers provided a communication letter which is signed by the respected client/s as proof of approval for the proposal. Release Planning - In the phase of commitment, customers prioritize user stories based on business value, and the developers prioritize user stories based on risk and confirm the development velocity. Finally, the customer chooses the user story to be completed for the next release. (Zentao 2020). Researchers with the client to partake in a meeting to conduct plans in releasing the project program, in this phase the researchers and client discuss the project’s general objective. At the level of the product, it is a crucial phase of the specifications coding process. At this phase, these version schedules are created for each iteration. The release schedule for the entire project was constructed by the researchers using it. Using the client's and the target user's preferences as a starting point, the researcher will design the suggested application. Aside from that, the researcher compiles information on the development's necessary components. The information from the study confirms if the components are appropriate and sufficient for usage in the final product. Iteration - is to organize the work and define a realistic scope for the iteration. Each Agile Team agrees on a set of stories for the upcoming iteration (the iteration backlog) and summarizes those stories into a set of iteration goals. The iteration backlog and goals are based on the team’s capacity and allow for consideration of each story’s complexity, size, and dependencies on other stories and other teams. (Scaled Agile, Inc. 2021) Throughout this phase, the researchers allocated each member, team leader, programmer, tester, and technical writer their respective duties. In this part, the programmer created and developed the application that is intended to be cozy and well-organized. A coding component for reworking in testing and improving code quality. Using Unity Engine, the researcher created and developed the application. The functions for the game's features are built using C# programming. Acceptance Testing - According to GreeksforGreek (2022) Acceptance Testing is the last phase of software testing performed after System Testing and before making the system available for actual use.