Instilling a culture of craftsmanship
When companies are struggling to increase the quality of their deliverables they tend to turn towards quick technology fixes, for example pushing for more test automation. The real solution isn't a technology fix but a cultural one. We need to change our culture to one that embraces, nurtures and encourages software craftsmanship.
It's only when your employees care about the quality of their work and when your organization rewards quality over speed that you'll make a lasting impact. Let's explore what this means and how we can start this culture shift.
Some of the things we'll look into:
- How to implement code reviews that become primers for mentoring each other.
- How performance reviews can impact the quality of your software
- How a CICD improves software quality
- Changing your management style towards Management 3.0
Outline/Structure of the Talk
- What is a software craftsman? Where did this idea come from?
- If Agile came from developers, why did it move away from them?
- How do we bring Agile back to developers, how do we get them back on track for better quality?
- TDD is great, but what about creating an entire culture around craftsmanship?
- What is your company doing that blocks it from happening?
- Effective steps you can do at the team level to raise the bar in quality
- What can you do at an organizational level to incentivize craftsmanship
The main objective of the talk is to bring awareness that code quality isn't just a technical problem, it's also an organizational culture problem. If you don't change the culture, you won't have any success in solving the technical problems.
Prerequisites for Attendees
An understanding of the impact delivering sub-par quality software.
schedule Submitted 2 years ago
People who liked this proposal, also liked:
Sanjiv Augustine - Driving Flow, Value, and Innovation with the Agile VMO™Sanjiv AugustineFounder and CEOLitheSpeed LLC
schedule 2 years agoSold Out!
Historically, Project Managers (PMs) and other middle managers have hustled in a bureaucratic system to drive teams to deliver value. As organizations transition from a project to product model, where can these leaders best add value in a fast-moving, Agile and entrepreneurial world? In this new and exciting world, middle managers are enabling rapid delivery of value and successful business outcomes via the creation of the Agile Value Management Office™. Learn how an Agile VMO™ drives business agility through small batches, frequent releases, and continuous adaptation. We'll explore how to:
- Create a collaborative management team-of-teams
- Bring Lean discipline to product portfolio prioritization
- Establish an End-to-End team model of resource management
- Track in-flight product work using a Visual Management System
We'll explore the transition for PMs and other leaders into this exciting role: facilitating the delivery of flow, value, and innovation end-to-end on the Agile VMO™, even as they support their Agile teams in the quest for business agility.
Raj Indugula / George Lively - Being Test-driven: It's Not Really About Testing
Good news: Test-driven practices have jumped the chasm to general acceptance! The bad news, though, is that while TDD, BDD, and ATDD are prominent buzzwords in the industry today, they are rife with misconceptions, with many people incorrectly assuming that being test-driven is all about testing.
In this talk, learners will leave with a clearer understanding of Test-Driven Development (TDD), Behavior Driven-Development (BDD), and Acceptance Test-Driven Development (ATDD), and gain practical insights into how these practices can help teams develop better software. We will gain an appreciation for TDD as being primarily a specification and design technique, and how to get the whole team involved earlier in the delivery cycle using a BDD approach.
M. Scott Ford - Building a Bridge to a Legacy Application - How Hard Can that Be?M. Scott FordFounder and Chief Code WhispererCorgibytes LLC
schedule 2 years agoSold Out!
My team was asked to build an integration with an old legacy application which had no programming API whatsoever, and we were so excited. How did we tackle that challenge? Did we succeed? What happened next? Come and listen to find out. And I promise the ending will surprise and/or depress you.