Agile project management with XP Manual

MANUAL GESTIÓN DE PROYECTOS ÁGILES

maintenance is kept to a minimum, which in the medium term reduces the costs and risks of the project. Sometimes quality is at odds with simplicity. A more maintainable solution may be more complex and costly than a simpler but less maintainable solution. The rule of thumb would be: try to do the best you can with the time available. The next iteration will improve on the work of the first iteration as a base. This can be seen as a waste of time, but it is also a way to fight analysis-paralysis, bring value to the customer from the beginning and reduce risks. 13. Child steps: try to make the steps as small as possible, this will reduce the risk of failure of large steps. For example, run tests for every small code change you make. This will allow you to detect potential bugs more quickly. Don't wait two years to release a new version, try to offer updates as often as possible to users. A priori it may seem that small steps slow down development, but, in practice, small steps mitigate many risks and problems are solved much faster.

14. Accepted responsibility: Responsibility cannot be imposed, it can only be accepted voluntarily. XP practices reflect this principle. The team that has to do a job estimates the cost of doing that job and takes responsibility for meeting that estimate to the best of its ability. Similarly, the person responsible for implementing a user story takes responsibility for the design, implementation and testing of that story.

The principles allow a better understanding of the technical practices proposed in XP. Furthermore, by following the principles, new practices can be developed that are more suitable for certain types of projects.

20

European Open Business School