Agile Literatuur

De onderstaande boeken zijn uitgegeven onder de Ordina vlag en zijn gericht op de Agile ontwikkelmethode.

RUP op Maat – Agile IT met RUP, Scrum en PRINCE2

Het boek RUP op Maat is al sinds 2006 toonaangevend in het Agile toepassen van RUP. Zowel bedrijven als diverse HBO-opleidingen gebruiken dit boek intensief. Nieuw in de derde, herziene druk van RUP op Maat is aandacht voor de integratie met Scrum en de aansluiting met business modeling, architectuur en de 2009 versie van PRINCE2. Vanuit hun ervaring in uiteenlopende projecten hebben de auteurs de essentie van Agile ontwikkelen met RUP, Scrum en PRINCE2 kort en krachtig neergezet.

Testen2.0 – de praktijk van Agile Testen

Gebaseerd op de belangrijkste ‘lessons learned’ uit hun testervaringen bieden Anko Tijman en Eric Jimmink een vernieuwende kijk op het vak software testen. Deze visie weten ze concreet handen en voeten te geven. Ze beschrijven een gestructureerde aanpak voor agile testen, waarbij de basis wordt gevormd door de principes van agile sofwareontwikkeling.Het is bestelbaar via Sdu, hier.

Agile Testen

Daarnaast hebben we al in 2007 een klein boekje over agile testen uitgegeven. Dit is de eerste Nederlandse publicatie over gestructureerd testen in agile projecten. Het boek is bestemd voor IT-managers die beslissen over standaarden, processen en werkwijzen en voor testers die zich binnen projecten bezig houden met testen binnen Agile projecten.
Het boek is inmiddels als download verkrijgbaar als  Directe download.

Andere interessante literatuur

Specification by Example – How successful teams deliver the right software

“Specification by Example” is a must read for anyone serious about delivering software that matters. In it, author Gojko Adzic shares the secrets of how teams all over the world specify, develop, test, and deliver the right software, without defects, in very short iterative delivery cycles. Based on dozens of interviews with successful teams worldwide, this brilliantly rich and informative book will change the way software developers work.

Leading Lean Software Development – Result are not the point

Building on their breakthrough bestsellers Lean Software Development: Concept to Cash and Implementing Lean Software Development: An Agile Toolkit, Mary and Tom Poppendieck’s latest book shows software leaders and team members exactly how to drive high-value change throughout a software organization – and make it stick.

The Tester’s Pocketbook

The first aim of this book is to provide a brief introduction to the discipline called testing. This Pocketbook presents a set of Test Axioms that will help you determine what your testing mission should be and how to gain commitment and understanding from your management. The second aim of this Pocketbook is to provide a handy reference, an aide memoire or prompter for testing practitioners. But it isn’t a pocket dictionary or summary of procedures, techniques or processes. When you are stuck for what to do next, or believe there’s something wrong in your own or someone else’s testing or you want to understand their testing or improve it, this Pocketbook might be of help.

Management 3.0 – Leading Agile Developers, Developing Agile Leaders

In many organizations, management is the biggest obstacle to successful Agile development. Unfortunately, reliable guidance on Agile management has been scarce indeed. Now, leading Agile manager Jurgen Appelo fills that gap, introducing a realistic approach to leading, managing, and growing your Agile team or organization. Writing for current managers and developers moving into management, Appelo shares insights that are grounded in modern complex systems theory, reflecting the intense complexity of modern software development. Appelo’s Management 3.0 model recognizes that today’s organizations are living, networked systems; and that management is primarily about people and relationships.

Bridging the Communication Gap – Specification by Example and Agile Acceptance Testing

Bridging the Communication Gap by Gojko Adzic  is a book about improving communication between customers, business analysts, developers and testers on software projects, especially by using specification by example and agile acceptance testing. These two key emerging software development practices can significantly improve the chances of success of a software project. They ensure that all project participants speak the same language, and build a shared and consistent understanding of the domain. This leads to better specifications, flushes out incorrect assumptions and ensures that functional gaps are discovered before the development starts.

Comming soon:
Disciplined Agile Delivery – A Practitioner’s Guide to Agile Software Delivery in the Enterprise

This book (from Scott Ambler) is a practical guide to getting started today with Agile practices that are structured within a disciplined approach consistent with the needs of enterprise-scale, mission-critical projects.
There are several ways that you’ll benefit from reading this book:
It describes an end-to-end agile delivery lifecycle.
It describes common agile practices, how they fit into the lifecycle, and how they work together.
It describes how agile teams work effectively within your overall organization in an “enterprise aware” manner, without assuming everyone else is going to be agile too.
It uses consistent, sensible terminology but also provides a map to terminology used by other methods. And many more…

Geef een reactie

Vul je gegevens in of klik op een icoon om in te loggen.

WordPress.com logo

Je reageert onder je WordPress.com account. Log uit / Bijwerken )

Twitter-afbeelding

Je reageert onder je Twitter account. Log uit / Bijwerken )

Facebook foto

Je reageert onder je Facebook account. Log uit / Bijwerken )

Google+ photo

Je reageert onder je Google+ account. Log uit / Bijwerken )

Verbinden met %s