What does it mean to be a professional software developer? What rules do we follow? What attitudes do we hold? And how can we maintain our professionalism in the face of schedule pressure? In this talk Robert C. Martin outlines the practices used by software craftsmen to maintain their professional ethics. He resolves the dilemma of speed vs. quality, and mess vs schedule. He provides a set of principles and simple Dos and Don’ts for teams who want to be counted as professional craftsmen.

Over the last ten years, Test-Driven Development has grown from something exotic, that only a handful of people knew about, to near- commodity. So there’s nothing left to say, right? We don’t think so.

In this talk, we’ll review some of the landmarks in the history of Test-Driven Development and what they tell us about how to develop software; the ideas, techniques, objections, and misunderstandings.

We’ll talk about our experiences of discovering TDD and what we’ve learned about how to do it well, how to adopt it, and how to bring it into existing code.

Agile teams practicing Acceptance Test Driven Development (ATDD) define acceptance tests collaboratively while discussing each story. This practice helps uncover assumptions and confirm that everyone has a shared understanding of “Done”. During implementation, the technical team automates the natural-language Acceptance Tests by writing code to wire them to the emerging software. In this way, ATDD tests become executable requirements. This session is a demo of the full ATDD workflow from initial discussions to distilling tests into an automatable format to implementing code to the final demo.

Of the many benefits of agility, none is more transforming than the power of self-organizing teams. Yet, building such teams remains one of the most elusive goals. This is due to the challenging transition functional managers must make to develop the right organizational environment for teams to mature. This session is for managers who are challenged in building strong self-organizing teams. This session will develop your agile organizational leadership awareness and competencies to build committed, disciplined and self-organizing teams who share responsibility.

Traditional development emphasizes “following a plan with minimal changes,” whereas agile stresses “adapting successfully to inevitable changes.” If agility is delivering customer value by being flexible, then how can measuring agile performance by adherence to schedule, cost, and scope be valid? We need to modify project success measures in order to build effective agile organizations. The session will build a case for changing performance measurement from the traditional Iron Triangle of cost, schedule, and scope to an Agile Triangle that focuses on value, quality, and constraints.