Catálogo de publicaciones - libros

Compartir en
redes sociales


Pro .NET 2.0 Extreme Programming

Greg Pearman James Goodwill

Resumen/Descripción – provisto por la editorial

No disponible.

Palabras clave – provistas por la editorial

Software Engineering/Programming and Operating Systems

Disponibilidad
Institución detectada Año de publicación Navegá Descargá Solicitá
No detectada 2006 SpringerLink

Información

Tipo de recurso:

libros

ISBN impreso

978-1-59059-480-3

ISBN electrónico

978-1-4302-0179-3

Editor responsable

Springer Nature

País de edición

Reino Unido

Fecha de publicación

Información sobre derechos de publicación

© Apress 2006

Tabla de contenidos

Release Planning—The Journey Begins

Greg Pearman; James Goodwill

By expanding your tool set with a mock object tool, you can now test your application without worrying too much about external dependent resources. This will allow you to sustain a better velocity and improve the feedback that your application gives you.

The next tool that you will find valuable is CruiseControl.NET, covered in the next chapter. This tool will allow you to take all the other tools you have acquired and automate their use.

Part 3 - XP in Action | Pp. 111-132

Iteration Planning for the First Iteration

Greg Pearman; James Goodwill

Psychophysics sheds light on one of the key problems of psychology as a science, namely the applicability of mathematics to the measurement of psychic phenomena, an issue which had also been addressed, but left unresolved, by Kant. But as the question entered the realm of the exact sciences it carried with it the traces of metaphysical disputes.

Part 3 - XP in Action | Pp. 133-147

First Iteration

Greg Pearman; James Goodwill

In this first iteration, the team members successfully delivered all the included user stories. There was neither an increase nor a decrease in velocity for the team. Therefore, next iteration, the team will sign up for the same amount of work.

As the source code evolved, there were areas that were identified as needing refactoring (like the connection string). We will address those areas in the next iteration (Chapter 15), but we could have handled them in this iteration as well.

Next, you will start the second iteration by iteration planning again. This will allow you to make any adjustments to the plan based on what you learned from this iteration.

Part 3 - XP in Action | Pp. 149-200

Iteration Planning for the Second Iteration

Greg Pearman; James Goodwill

In this iteration planning phase, we started with the remaining user stories in the release. Because their story points did not add up to the team’s velocity for the iteration, the customer was able to pull more functionality into the iteration and the release. In this case, we went all the way back to the stories that were originally outside the release plan. Lastly, we made sure that all the developers had signed up for as much work as possible without overcommitting themselves.

Part 3 - XP in Action | Pp. 201-213

Second Iteration

Greg Pearman; James Goodwill

By now, you should be getting a feel for the XP process. You have seen how to take a testdriven development approach to coding. You have witnessed how an iterative approach can provide a lot of feedback in the form of unit and acceptance tests. Daily stand-ups and the graphs and charts generated by the tracker create a better environment for communication. All of this communication allows the team members to better gauge where they are at meeting their targets.

You are well on your way down the XP path.

Part 3 - XP in Action | Pp. 215-277