Enough about Process, Let’s Use Patterns
When new developers and testers join the company, we want them to learn the “way we do software here.” So we give them the “stone tablets”―the volumes of process documentation― to study. However, the problem is that the details in this documentation are primarily for beginners and don’t give practitioners what they need to perform at a high level. Paul McMahon has found a better way to achieve and sustain high performance—by focusing on common patterns that repeat in organizations to help practitioners make better decisions. Join Paul as he shares common software development patterns he has observed, questions practitioners should be asking, and tips and warnings to help them make better decisions. Take away practical and easy-to-use techniques to identify and communicate repeating patterns specific to your organization, patterns that can help less experienced practitioners learn faster and consistently perform at a higher level.