Day 2 – a dive into agile software development

Test Driven Development Laboratory

The participants get started with TDD, by programming on a number of exercises in pairs. At the end of this laboratory, participants have a more thorough understanding of how TDD works, and what its effects in practice are. They now have some hands-on experience.

Introducing Agile project management with Scrum

Agile project management answers questions such as: what makes the work of an agile project manager different, in what ways does the team work differently – with respect to planning, as well as interactions between the team roles. What information is available to the team to steer themselves, and what information is necessary to manage effectively? We use the planning process called Scrum as an example.

Story writing and acceptance testing

Testing and test driven development on the unit level is valuable, but not sufficient. A second heartbeat is at least as important: delivering value to the customer, usually through working, tested software that has been developed with close customer collaboration.  In this module we introduce the user story as a way to discuss and plan features. Participants learn how powerful user stories as a tool can be by writing some.

Besides user stories, we tackle a more difficult subject of agile software development: (automated) acceptance tests.  Participants learn to see the value of acceptance testing, and they understand when automated acceptance and integration testing is (im)possible – with creativity automated testing can be used more often than most developers believe. That way, more time is available for creative ways of testing, as well as delivering more business value to the customer.