This book will teach you, the software student, practitioner and/or manager, how to become competitive in the global resource pool in which we reside. In sometimes humorous, mostly direct conversation, this book discusses understanding the customer, serving the customer, and learning to discern what really matters along the way by exploring some difficult and often unpopular subjects:

1. The professional software talent pool is truly global and we are only grains of sand on a world beach

2. There is more value in seeing the forest than worshiping the tree

3. Know when to solve a problem, when to simplify, and when to be quiet

4. Delivering a technical solution is a social problem · Overpay the right people for the right reasons

5. Serve the customer and provide immediate value or someone else will

This book takes you on a journey through the wonderful world of FitNesse, a great web-based collaboration tool for software acceptance testing. FitNesse enables software developers and business people to build a shared understanding of the domain and helps produce software that is genuinely fit for purpose.

The book is primarily aimed at .NET developers interested in starting with TDD and those who already practise unit testing and want to move beyond that into development driven by acceptance tests. Java developers can also benefit from the third part of this book, which presents best practices for using FitNesse in a team environment and integrating FitNesse into the wider software development ecosystem, including web and database tests.

Test Driven .NET Development with FitNesse provides practical advice for solving real-world problems, based on experience from several big .NET projects. Here are some of the topics covered in this book:

• Applying test-driven development principles and practices to guide projects and improve the quality of code
• Writing FitNesse tests for .NET code effectively
• Getting customers involved in testing
• Building a shared understanding between business people and developers using acceptance tests
• Setting up and managing FitNesse in a team environment
• Using FitNesse and Selenium for Web interface testing
• Testing legacy code and databases
• Extending FitNesse to meet your particular project needs
• Understanding how FIT and FitNesse work under the hood

The Art of Agile Development contains practical guidance for anyone considering or applying agile development for building valuable software. Plenty of books describe what agile development is or why it helps software projects succeed, but very few combine information for developers, managers, testers, and customers into a single package that they can apply directly.

This book provides no-nonsense advice on agile planning, development, delivery, and management taken from the authors’ many years of experience with Extreme Programming (XP). You get a gestalt view of the agile development process, including comprehensive guidance for non-technical readers and hands-on technical practices for developers and testers.

Klar, alle entwickeln inzwischen “agil”. Fast jeder hat schon einmal vom Agilen Manifest gehört, häufige Iterationen werden inzwischen für die meisten IT-Projekte angestrebt, und dass die zwischenmenschliche Komponente auch “irgendwie” wichtig ist, wissen wir doch auch nicht erst seit gestern. Aber “agil” ist nicht so vage und schon gar nicht beliebig.

Java Champion Michael Hüttermann erklärt, was Agile Softwareentwicklung wirklich bedeutet, und zeigt, wie sie sich konkret in die Tat umsetzen lässt. Dabei geht er auch auf Lean Development, XP und Scrum ein, verdeutlicht den Nutzen für alle Beteiligten und berichtet von zahlreichen Fallstricken in der Praxis. Von der Methodik über die richtige Einführung agilen Vorgehens in Unternehmen führt er bis zu den konkreten Werkzeugen, mit denen sich diese Prinzipien in Java-Projekten realisieren lassen: JUnit und TestNG für Komponententests, Selenium und WebTest sowie Jemmy für funktionale und Akzeptanztests für Java Web- und Swing-Anwendungen, Subversion, Ant, Maven und CruiseControl für Konfigurationsmanagement und Buildprozess, ergänzende Werkzeuge wie EasyMock, IntelliJ IDEA und Trac—sie alle lassen sich zu einer hervorragenden Infrastruktur verknüpfen, mit der man die Anforderungen moderner Java-Projekte effektiv erfüllen kann. Zahlreiche typische Szenarien spielt der Autor auch mit konkreten Code-Beispielen durch.

I wrote this book because there’s so much ignorance about programmers: who they are, how they think, and even what they do in a typical day. Of course you know all these things because you live them every day, but you’d be amazed how many other people are clueless: coaches, therapists, counselors, family members, news reporters – almost everyone.

So why would you, a programmer, want to buy this? Well, it might make a nice present for your significant other, your parents, your boss, or anyone else who really needs to understand you, your job, and your aspirations, but just doesn’t have the background.

On-time and in-budget delivery of business change programmes and projects has never been more vital. Since 1994, the DSDM Consortium has been at the forefront in developing processes which combat the common causes of project failure – thereby ensuring time, quality and cost targets are always achievable.

Atern is the culmination of practitioners’ experiences drawn from a wide range of public and private sector projects over more than a decade. This unparalleled expertise has resulted in a robust, but agile framework, which can be successfully applied across a variety of organisational and project contexts.

With so many potential applications in mind, the Atern Pocketbook has been designed to offer a clear introduction to project delivery for all comers. It can be either read “front-to-back” or dipped into for references purposes.

In-depth information, resources and case studies about Atern are available on our website at www.dsdm.org

As more and more people move towards adoption of Agile practices, they are looking for guidance and advice on how to adopt Agile successfully. Unfortunately many of the questions they have such as: “Where do I start?”, “What specific practices should I adopt?”, “How can I adopt incrementally?” and “Where can I expect pitfalls?” are not adequately addressed.

This book answers these questions by guiding the reader in crafting their own adoption strategy focused on their business values and environment. This strategy is then directly tied to patterns of agile practice adoption that describe how many teams have successfully (and unsuccessfully) adopted practices like test-first development, simple design, and others.

188 pages, 6” x 9”, ISBN# 978-1-4303-1488-2

This is the first truly impartial book that offers expert objective analysis of Agile software development methods. It reviews the philosophical underpinnings and objectives of the Agile Manifesto and the 12 Agile Principles, and discusses in concrete detail each practice of the six most widely recognized Agile methods. Managers find concise and unbiased insight into adoption implications, the possible benefits that may accrue, and the potential pitfalls of the practices. Forewords by Kent Beck (author of Extreme Programming Explained): “This book presents the alternatives for improvement fairly and impartially.” and Mark Paulk (principal contributor to the CMM): “Alan’s book can be a useful tool for making informed decisions about the appropriateness of agile methods in your environment.”

In diesem Buch wird die XP-Thematik anschaulich und praxisorientiert dargestellt. Alle XP-Techniken werden erläutert, zu jeder Technik wird neben einer kurzen Beschreibung vor allem auf konkrete Erfahrungen und Empfehlungen eingegangen. Weitere Themen sind Rollen in XP-Projekten, die Projektorganisation und organisatorische Randbedingungen bei XP. Die Explorationsphase, die Einführung von XP in Projekte und Unternehmen sowie ausführliche reale Projektberichte bilden jeweils eigene Kapitel. Auch das Anpassen von XP an unterschiedliche Kontexte wie Outsourcing, Zertifizierung und eingebettete Systeme wird erläutert. Die 2. Auflage behandelt neu die agilen Methoden Scrum, Feature Driven Development (FDD) und industrial XP (IXP), neue XP-Techniken sowie Aufwandsschätzungen für große Projekte und Projektkontrolling.

Refactoring bedeutet, die interne Struktur der Software zu modifizieren, um sie verstÃndlicher und leichter Ãnderbar zu gestalten, ohne dass sich das gewünschte funktionale Verhalten Ãndert. WÃhrend Refactorings bei kleinen Projekten noch Ãberschaubar sind, werden sie in graeren Projekten leicht zu unangenehmen Aufgaben. Vor allem komplexere Umstrukturierungen , VerÃffentlichungen von APIs und solche, die die Datenbank betreffen, fahren haufig zu Problemen. Wie man als Entwickler oder Projektleiter damit umgehen kann, zeigen die Autoren dieses Buches anhand eigener Erfahrungen in kommerziellen Projekten. Sie geben dem Leser eine Reihe von Tipps und Tricks mit auf den Weg, wie er Refactorings großer Systeme in seinen eigenen Entwicklungsprojekten bewaltigen kann. Erläutert werden klassische Fragen, u.a.: Wie kannen große Refactorings in kleine Schritte zerlegt werden, oder wie kannen komplexe Refactorings in die tägliche Entwicklung integriert werden?