The waterfall method of developing software is a bunch of translation activities: The design is a translation of the requirements into the language of architecture, the code is another, and a formal test process is a third. And with each translation, there’s the opportunity to introduce error. When your DevOps team is isolated, it creates another handoff, and another point of failure.
When there is a system outage or other serious problem, most organizations have a critical incident response team to handle communication with all relevant stakeholders. But what happens when communication among the technology experts is not going well? How do you go about understanding the problem and helping each contributor work effectively with the entire response team?
Business stakeholders and DevOps teams both have to take an active approach to app development, but neither faction should have to change practices and processes in order to get their needs across. Investing the time to establish communication between these teams will drive delivery of the applications customers demand.
The power that comes from our positions and roles matters most in terms of our own influence and ability to achieve desired results. You may have limited ability to change your position within a structure, but you have limitless potential to understand and make the most of positional power.
Jaimee Newberry, co-founder and CEO at Picture This Clothing, chats with TechWell community manager Owen Gotimer about the power of communication, the HIPPO in the room, and how to create psychological safety in brainstorming sessions.
In this interview, visionary speaker Selena Delesie explains how successful teams embrace specific principles, including listening deeply, believing people truly matter, having an addiction to learning, serving others, flowing through change, moving through fear, and following joy.
Testers tend to be innately curious creatures. Being curious and evaluating risks—that is what the testing job is about. Often it is the statement “I don’t know” that drives our curiosity in testing. Find out not only how to push past the fear of not knowing but how to embrace your curiosity.
Communication is at the heart of our profession. No matter how advanced our testing capabilities are, if we can’t convey our concerns in ways that connect with key members of the project team, our contribution is likely to be ignored. Because we act solely in an advisory capacity, rather...
Thomas McCoy, Australian Department of Social Services