The hard part of successful DevOps isn’t implementing the technology; it's ensuring you have the right culture in your organization. You need to break down silos and align competing priorities and individual incentives to gain real benefits from DevOps. Move beyond thinking about technology alone and look at the people side of the equation. Here are seven ways to create a successful team that delivers the benefits of DevOps.
There is a lot of talk in the testing world about shifting left. Basically, “shift left” refers to moving the test process to an earlier point in the development process, independent of the development approach. This article explores a case in which shift-left has been applied, and the lesson is that shifting left cannot be achieved by testers alone—it must result from a team effort.
When it comes to achieving sustainable test automation, having an appropriate test automation team structure in place is the most important first step to take. This article has some proven practices for a few different test automation adoption scenarios—led by an automation team or a regression team, and with agile adaptations—that have helped organizations enjoy long-term test automation success.
Ambiguity abounds about value streams, so it’s good to clarify what they are, why they matter, and how to exploit them. It's important to help employees understand the organization's definition of value, to provide visibility on how business value is created, and to focus on the fast flow of value through the value streams. If everyone understands which direction to row the boat, they can steer toward it together.
Just because a software team adopts agility doesn’t mean they’ll see results. Being flexible has its benefits, but ensuring that the team is given total responsibility to make decisions may be more important.
Most software developers are in either the agile or the waterfall camp. Agile is required to be competitive, but many enterprise processes still rely on waterfall practices for stability. They can coexist.
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, Jason Wick, senior manager at MakeMusic, discusses his STAREAST presentation about eight ways you could be making your one-on-one meetings completely useless. He discusses in depth what he feels is the number one way to ruin these meetings: holding back on feedback. He also offers advice on how you can educate your team leader to avoid the pitfalls that lead to ineffective one-on-ones.
In this interview, Melissa Tondi, senior QA strategist at Rainforest, discusses the foundation you need in order to have a positive introduction for new tools and technologies. She explains why the team leader has to understand what motivates each individual and how to get them excited about their job. Melissa says team members also have to realize that if they are in any way involved in testing software, they are a technologist, so they have to embrace the tools and technology that will continuously improve and streamline repetitive tasks.
Adam Auerbach, VP of Quality Engineering at EPAM Systems, chats with TechWell Community Manager Owen Gotimer about how an inexperienced team can start its agile transformation, the value of stand-ups and retrospectives, and how to make remote teams feel more connected.
Drawing from her own experiences across twenty years in a range of industry roles, Jaimee Newberry shares true stories of at least a dozen tiny but important things she still sees every day that could make all the difference in how people work with you.
AWS Lambda is a serverless architecture that relieves you of hardware and scaling setup concerns. AWS Lambda functions are used by many organizations for serverless application development and automating DevOps tasks.
Most teams that do agile development start with Scrum. And why not? Scrum is a proven method for focusing your team, ensuring that work adds value, and minimizing the risk with release. Then, after awhile, Scrum becomes stagnant.
Teams can hesitate to adopt agile practices, even when there’s a clear desire for transformation at the executive level. But there are strategies for coaching agile-skeptical teams into an agile mindset.