One common metric in agile measures team health or team happiness, but creating a way to measure this that is valued by the team is not an easy task. It’s having clarity on the reason you’re measuring these metrics and who benefits from it that gives you real value. Here are some ways you can measure this elusive quality, as well as how to make sure you're gaining useful information.
Many surveys indicate that more teams work in distributed environments. But agile approaches work best when people collocate, huddle around a problem, and closely collaborate on the best solutions that will deliver value. Is collocation the only option these days? Does distributed always imply “dysfunctional”? Does technology help or hinder? Maybe the problem is how we think about the working environment. Mark Kilby will share key principles of successful distributed agile teams that help define better working environments. Understand how the principles apply to different types of distributed teams, and discover how agile practices change in distributed teams and how they may vary from team to team. You'll take back ways to assess your current distributed team environment and generate ideas for improvement.
Hiring trained talent has been a challenge for IT organizations for several years now. How do you find a steady source of qualified candidates for entry-level QA and QE positions, especially considering colleges and universities don't include a software quality assurance curriculum?...
Although processes and tools play an important role in software testing, the most important testing tool is the mind. Like scientists, testers search for new knowledge and share discoveries—hopefully for the betterment of people’s lives. More than sixty years ago, William I.B. Beveridge reframed discussion of scientific research in his classic book The Art of Scientific Investigation. Rather than add to the many texts on the scientific method, he focused on the mind of the scientist. Join Ben Simo as he applies Beveridge’s principles and techniques for scientific investigation to software testing today. Learn to discover and communicate new knowledge that matters; to think—and test—like scientists; and to continually prepare, experiment, exploit chance, imagine productively, apply intuition and reason, tune observation, and overcome resistance.
It's important to create a culture that inspires and infuses your development team with great ideas. But ideas are not action. Ideas in and of themselves are nothing more than unrefined, random thoughts, and worse, most ideas never get implemented. Even when you do follow through on some of the best ideas, they can cause great harm without proper planning and execution. While creativity is an asset, unbridled creativity where disparate ideas abound outside a sound decision-making and execution framework will create distraction and chaos. In this session, Melissa Petak will show you how to transform your organization into a value-creating machine. Using Forbes 15 elements of spurring innovation, Melissa will show you how to balance your innovation portfolio, establish a competitive advantage, and drive business engagement. You'll learn how to create a corporate culture that turns ideas into innovation.
Even today, communication breakdowns are a primary cause of software project failures. Marcia Buzzella’s research shows that increasing the success rate of projects across agile, DevOps, and waterfall methods requires a balance of social and technical capabilities. Social interactions enable us to assess situations and course correct in ways machines cannot. By strengthening your individual social capabilities (i.e., improving communication techniques and building supportive relationships), you can help transform how testing activities are perceived and help stakeholders understand how testing objectives align with overall project goals. Marcia offers guidance on assessing your current communication skills—what you do well and what needs to improve—and tactics for enhancing your skills and the skills of your team.
With the transparency of agile and the granularity of team-based metrics, it's important to be responsible in how you use your measurements. There are five principles Joel Bancroft-Connors adheres to when dealing with metrics: start collecting early and often, be consistent, stay focused, measure the project and the teams separately, and—most importantly—measure responsibly.