0% found this document useful (0 votes)
104 views3 pages

Agil Methodology (Pacman Proyect UVG)

The document discusses a group project to develop the game Pacman using Extreme Programming (XP), an agile methodology. The developer team is made up of 4 students and they chose XP because it is suited for small, collaborative projects with frequent feedback. XP's iterative approach is a better fit than other methodologies like RUP that are aimed at larger projects. The planning section outlines the schedule for modeling, developing, testing and presenting the Pacman game application over the course of the semester.

Uploaded by

Martín Guzmán
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
104 views3 pages

Agil Methodology (Pacman Proyect UVG)

The document discusses a group project to develop the game Pacman using Extreme Programming (XP), an agile methodology. The developer team is made up of 4 students and they chose XP because it is suited for small, collaborative projects with frequent feedback. XP's iterative approach is a better fit than other methodologies like RUP that are aimed at larger projects. The planning section outlines the schedule for modeling, developing, testing and presenting the Pacman game application over the course of the semester.

Uploaded by

Martín Guzmán
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Universidad del Valle de Guatemala

Agile Methodology
XP
Justification and Planning

Héctor Hurtarte
Martín Guzmán
Kevin Sánchez
Karen Tojín

17/03/2009
Agile Methodology: Extreme Programming (XP) for Pacman

The final project that we have chosen is the game Pacman, the goal of the game is to defeat the
opposite player (either machine or human) by "eating" all the pieces of food in the scenery And
to pass levels to get higher scores.

The developer team is conformed by Héctor Hurtarte, Martín Guzmán, Kevin Sánchez and
Karen Tojín.

To achieve the final project purposes we have selected the agile methodology Extreme
Programming (XP) because XP has a disciplined approach to software development. This
methodology takes what is generally called as developing practices and takes them to the
extreme.

The relatively small size of the project also gave us a lead that XP was the right agile
methodology to use, against a unified process methodology like RUP that is more oriented for
large projects. This is because the unified process methodologies are based on the iterative and
incremental development as they meet the needs of different use cases. Our project counts
with a fewer amount of use cases, and for that reason we conclude that we didn’t need a
methodology that involved a big amount of artifacts as the unified process methodologies and
we choose XP.

XP methodology is ideal when working with a small group of programmers, and


multidisciplinary equipment is on line, as in our case. We have a costumer (the teacher) that
tells us what his requirements are, and our group, as developers, has to model, design,
elaborate and implement the system. We also have a limited time and resources for the
system’s developing so we have to improve the elements that we have, this another reason
that made us think that XP was the right methodology for project’s development.
Planning

Activity Date (Each Monday of the week)


Project Assignment February 16
Decide Project February 23 – March 2
Installing software and platform SCM March 9 – March 23
Running tests for the software to use March 9 – March 23
Modeling Project March 9 – March 30
Acquisition of mobile February 23 – March 30
Application Development March 23 – May 11
Design and development of unit tests March 30 – April 6, April 20 – May 18
Installing the application on mobile April 20, May 4 – May 11, 25 May
Design and development of tests in the April 20, May 4 – May 11, 25 May – June
mobile 1
Preparation for project presentation 25 May – June 1
Presentation and final project June 8

You might also like