Book Image

Agile Technical Practices Distilled

By : Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia
Book Image

Agile Technical Practices Distilled

By: Pedro M. Santos, Marco Consolaro, Alessandro Di Gioia

Overview of this book

The number of popular technical practices has grown exponentially in the last few years. Learning the common fundamental software development practices can help you become a better programmer. This book uses the term Agile as a wide umbrella and covers Agile principles and practices, as well as most methodologies associated with it. You’ll begin by discovering how driver-navigator, chess clock, and other techniques used in the pair programming approach introduce discipline while writing code. You’ll then learn to safely change the design of your code using refactoring. While learning these techniques, you’ll also explore various best practices to write efficient tests. The concluding chapters of the book delve deep into the SOLID principles - the five design principles that you can use to make your software more understandable, flexible and maintainable. By the end of the book, you will have discovered new ideas for improving your software design skills, the relationship within your team, and the way your business works.
Table of Contents (31 chapters)
Free Chapter
Section 1
Section 2
Section 3
Section 4
Chapter 21
License: CyberDojo

From Forming to Performing

When there is team spirit in a group with a common goal, there is no storming phase. In Team C, we never had that experience. We knew exactly what we considered important and shared it with everyone from day one. After the initial coaching on the field, the other two team members arrived and, from then on, user stories began flying on the kanban board.

We had regular product demos with stakeholders, led every time by a different member of Team C. Those who weren't in the meeting were at their desks, working on the backlog.

The level of focus and commitment was outstanding. We had many discussions as a team, but decisions were always made by a consensus in a matter of minutes. We trusted the expertise that each member gave to the service of the team, always willing to try out something suggested by someone who knew more about the matter.

We also decided to take some risks that resulted in accidentally discovering a new, superfast way to work...