With more than 25 years in the industry, I understand the need for Quality Software Craft practices. Software creation is a complex endeavor that requires great minds to think about not only solving the problems but also about how to create easy maintainability and extensibility.
I teach teams how to create well-crafted software and processes for maturing into high-performing teams. I believe in Quality Craft practices like TDD, Pair & Mob programming, CI/CD and SecDevOps Teams.
| Pronouns | He/Him |
"Visualizing Work" is an important aspect of Fluid Scaling Technology (#FaST).
The practice of "making all the work visible to anyone interested at any time" has the radical effect of speeding up the development of a product.
This happens for several reasons:
- Less time spent in meetings
- More trust across teams and roles
- Better understanding of code interactions
Fluid Scaling Technology (#FaST) has many supporting features, and one of the most important is "Mastery"
Growing the knowledge and abilities of your employees creates a better product, a better code base, higher employee engagement, and team responsibility, along with enjoyment and pride in the work.
Mastery is a key component of creating an environment where innovation thrives. If learning time is not part of your work, your company is not achieving its fullest potential.
Are your teams making learning a priority?
Does your company value the growth of its employees?
Why or why not?
How does that manifest in your day-to-day work?
How do your teams handle working in the complex domain?
Software is a Complex Endeavor, it cannot be made effectively using complicated processes and organizational structure. Creating teams based on skill sets (or functionality) is a command and control practice.
Fluid Scaling Technology (FaST) brings all the people together and allows them to form around the work. This creates a motivated, knowledgeable team that feels a sense of ownership around their work.
Are your teams feeling the same?
Instead of creating teams and then splitting the work between them, you should be forming teams around the work that needs to be done.
Creating feature teams slows your development processes, creates dependencies, and causes organizational silos that promote an Us vs Them atmosphere.
Fluid Scaling Technology brings dependent teams together to form around the work, allowing the right people to work on the right work, right now.
How did you get into conference speaking? I have been talking with co-workers about how they should start, but have only my experiences.
What are your experiences?
What advise would you give someone who's interested, but unsure if they have anything new to say?
Mob Programming is a fabulous way to work.
It produces higher quality code at a more rapid pace than working solo.
It spreads knowledge to the team and removes silos.
Unless you're doing it wrong...
Then you're just paying people to watch others write code.
Let's have a chat about how your teams can get the best out of working collaboratively.
