[bruce343434]

What has been, in your experience, a repeatable process for quality engineering? How much does it depend on the kind of software one is engineering, or is it applicable to any kind of software with any kind of constraints?

[EchoChamberMan]

Repeatable processes require long term strategy.

[edit] Too many of these people want tomatos, so they plant a tomato, when really they want seasonal tomatos, and need to consider a farm, and take into account growth cycles. The term I like is "sustainable development."

[bruce343434]

I was hoping for more actionable, or at least concrete, advice...

[EchoChamberMan]

Some complexity is irreducible.

As mentioned by user "phkahler":

> 1) Come to work.

> 2) Look at the current state.

> 3) Decide what the product needs from you.

> 4) Do that.

> 5) Use git.

> Steps 2 and 3 may involve communication. Step 5 is tracking changes. Have a PM that tracks main things people are working on and estimated dates (not dictated dates).

> This is how my current job works and we are unbelievably productive.

[edit]

I like the book "phoenix project," and I think they wrote "Team Topologies" which I am curious to read.

[edit]

In general, psychological safety was the number one factor for productive teams, according to a massive google study. From this viewpoint, it's easy to see why there are so few productive teams, as there is little to no safety for most people. Remember though, "There are no silver bullets."

[Edit]

The goal should be continuous delivery imo.