Manual Agile project management with XP

MANUAL GESTIÓN DE PROYECTOS ÁGILES

create the best product they have ever dreamed of. Motivation and shared purpose is also one of the aspects that are encouraged. XP is a simple process that puts people to work together to achieve successful applications. XP can be used in distributed teams as well as in teams working within the same company in a common office. The main characteristic they will all have is that they want to create quality software in a fast and flexible way. The customer/user As in Scrum, in XP the customer becomes a member of the team. The usual way of working, before the popularisation of agile methodologies, was to talk to the client when the project was almost at the end and check if everything was correct. Then the client could be faced with unpleasant surprises. On the other hand, if the customer works actively with the development team, he or she can narrow down the problems, offer solutions and even learn new things about the problem. It is always an expert in the problem domain who finds the best and most elegant solutions. In the Scrum methodology, the customer is represented in the team as the Product Owner. The manager Depending on the development methodology we are using in the project, the manager is called by different names and can assume different roles. In the Scrum methodology, the Scrum Master is the figure with the greatest management burden. Although in this methodology the development team is self-managed and its tasks are far from the traditional "command and control" manager, who plans tasks for his subordinates. Generally speaking, the manager does not develop the product, but rather facilitates the context in which the development team develops the product, e.g. by removing impediments. The most important task of a manager is to make sure that everyone can do the work that needs to be done. The programmer analyses, designs, tests the software and integrates it into the system. He/she also estimates the cost of implementing each story and when finally implemented, its speed can be measured. For a developer, the most important thing is to correctly understand the functionality that is described in the user story. If in doubt, the client should be accessible to engage in a conversation to understand the functionality, its motivation, and the mechanism the client will use to verify that the story has been implemented correctly. In addition, the customer should see the following as soon as possible European Open Business School The Programmer

12