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.
Jan Jaap Cannegieter, principal consultant at Squerist, chats with TechWell community manager Owen Gotimer about senior management’s new role in agile development, strategies for providing feedback to managers, and why more teams should shift testing right. Continue the conversation with Jan Jaap and Owen (@owen) on the TechWell Hub (http://hub.techwell.com/)!
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.
In this interview, Bob Galen, principal agile coach at Vaco Agile, talks about the importance of getting rid of silos by breaking down the barriers of “them and us” and becoming “we.” He also discusses the need for agile managers to steer away from a tactical management view toward a more strategic leadership view. That means leading their teams by setting expectations and guidelines and being available to help if needed, but ultimately just trusting their teams to get the job done.
Taking a newly formed distributed Scrum team from mediocre to high-performing has its share of challenges, including differences in language, culture, and time zones; a misunderstanding of Scrum; and the "us versus them" mentality.