Software Company Culture
A healthy software company culture fosters creative ideas, energetic coworkers, and people who care so much about work they produce excellent products.
Software company culture that supports the needs of knowledge workers is the missing ingredient from many software development teams that focus too much on technology or agile practices!
Culture is how people work together to produce winning products. People are harder to control than technology, and putting everyone under tight chains of process actually inhibits their creativity and problem solving.
The culture on a team, or at a company, can encompass a variety of aspects. The history of the company, successes and setbacks, and the attitudes and values of the staff will impact how you need to communicate to inspire.
All Content about Software Company Culture
January 15, 2024 | 29:21
If you’re about to get a new tech job, sometimes the red flags are obvious. But what happens when you want the gig anyway?
October 23, 2023 | 29:10
Trusting people is getting tougher than ever these days, and nobody seems to have a harder time than programmers and managers.
July 27, 2022 | 16:51
When programmers estimate code on software projects and they turn out wrong, who’s to blame?
March 12, 2019 | 1:08:10
Woody Zuill, the leading voice in our industry around the concept of Mob Programming, joins me to talk about how it produces better developer teamwork.
March 8, 2019 | 25:03
Does it ever feel like you’d get so much more done if it weren’t for how much work people have you do on agile teams to make commitments?
February 26, 2019 | 18:12
In working with many teams and companies, when developers are frustrated on their agile project – it’s often forecasting that’s the culprit.
February 21, 2019 | 25:11
To keep an agile team from becoming toxic, you should know how the background of the founders of the company impacts hiring.
February 15, 2019 | 14:20
The core values, or motivation for starting the software company that the founders have can keep an agile team from becoming toxic.
June 22, 2018 | 45:26
John Cutler is an experienced Product Manager, writer, and consultant. I interviewed him about agile industry dogma – and where software culture is headed.
May 30, 2018 | 18:15
At some software companies, it can be hard for people to learn from mistakes they make together on a software project.
May 18, 2018 | 15:28
Let me tell you a story about one of the weirder software projects I’ve been on – and how trying to change the culture went wrong.
May 13, 2018 | 1:09:31
In this interview, Scott Nimrod and I discuss dynamics between consultants and hiring managers, career growth, and the direction of the industry.
May 8, 2018 | 18:51
Does it sometimes feel like the decisions made by leaders are almost trying to get programmers to hate their software development projects?
March 27, 2018 | 5:34
When high turnover in tech companies strikes, there’s a programmer skill gap! Many teams believe the lie that people can be productive on day one.
November 9, 2017 | 15:19
Get that sinking feeling the people running your company don’t know what they’re doing? Here’s 5 signs your software business is led by amateurs!
October 17, 2017 | 16:46
To let the customer take a larger role in deciding what’s in your product, and release it multiple times per day — you’ll have to overcome attachment.
September 10, 2017 | 35:48
A team that learns from software project failure produces better software – when you plan to exploit this ability.
August 16, 2017 | 32:33
I’d like to offer some insights that may help men avoid developer bro culture so we’re not damaging our careers.
July 25, 2017 | 20:00
Cross functional teams get people with different disciplines to work together better when developing software.
July 22, 2017 | 12:01
If you’re asking team members or maybe your entire company to change the way some aspect of software development is done – be careful!
July 8, 2017 | 21:25
Since software development is “knowledge work”, it benefits from the creative ideas and experiences individuals bring to each problem.