Catálogo de publicaciones - libros

In far too many software projects the value of the documentation delivered is not high enough to motivate the effort spent to write it. An outdated document can be as misleading as a good, up to date one can be helpful. This demonstration will show how unit tests complemented with descriptive comments can be used to generate documentation that is constantly up to date. It is demonstrated by example how both the static and dynamic features of a software system can be salvaged with very little effort to be presented to a bigger audience as relevant, readable documentation.

Open Source Software (contrasted with proprietary or “closed” software) has become a more widely accepted enterprise solution not withstanding some issues related to intellectual property rights and issues of liability and indemnification. Open Source Software (OSS) takes collaborative software development to a global extreme – OSS also provides a mechanism for decreasing time-to-market, improved quality, and reduced development costs. This panel will serve as a catalyst to discuss strategies, tools, and communities focused on the development and application of open source software.

Politics and Religion are traditionally taboo topics in polite after-dinner conversation. In this panel, we are going to discuss taboo topics in agile software development. Technical teams ought to choose technology based on the immediate needs of the current project and organization. But we all know that technology and methodology choices are often driven by people enhancing their resume – this conflict can start religious wars! On agile projects, we ask our customers to prioritize stories purely by business value, as if this is a straightforward thing to do and company politics are irrelevant. We need to recognize that projects that only deliver working software can still be classed as failures from an organizational perspective. If we pretend that the political dimension does not exist on agile projects then we cannot develop and share practices that help us handle these situations. This panel brings industry professionals to share their perspectives and experiences, the audience should come prepared to both ask and answer questions.

Does the discipline inherent in Agile/XP methods change the way a company does business in contrast to the influences of "traditional" plan-driven or ad-hoc software development practices? Are there differences in strategies for customer engagement, staff resourcing, and program management? Companies live or die depending on the accuracy of scheduling/budgeting projections and the ability to do more with less. Lean development, SCRUM, XP, and other agile methods may stress companies in hitherto unanticipated ways leading to both evolutionary and revolutionary organizational change. This panel will dis cuss the differences and similarities between XP/Agile and more traditional software development practices with regard to their impact on companies.