No, QA is not your designated tester
No, QA is not your designated tester. “QA” is a process, not a role: its real job is to help the team grow.
No, QA is not your designated tester. “QA” is a process, not a role: its real job is to help the team grow.
Measure an outcome rather than an output. This way, you empower your teams and align them with your company’s goals.
Producing high-quality software involves organizational aspects that go beyond technology and can undermine the CTO’s efforts.
The road to hell is paved with good intentions, and your Quality Department is no exception: it’s impossible to distinguish between “doing” and “doing better.”
This phrase, a DevOps mantra, is rooted in common sense. Yet the organization sometimes resists its implementation. CEOs, lay the groundwork.
2 common mistakes in dividing into Bounded Contexts: dividing by technical layers and dividing by entities. Think action verbs!
If you’re thinking about creating a custom framework, think twice: some have tried it, and they’ve had their share of problems!
Separating the IT function from the business units it serves is a fundamental mistake, because IT is viewed solely through the lens of its cost.
No-code and low-code tools have their place, provided their use is properly managed to avoid unpleasant surprises (shadow IT).
As it has become more widespread, the DevOps approach has strayed from its original spirit, sometimes to the point of being misinterpreted. Let’s set the record straight.