When you’re designing a dashboard to track and display metrics, it is important to consider the needs and expectations of the users of the dashboard and the information that is available. There are several aspects to consider when creating a new dashboard in order to make it a useful tool. For a mnemonic device to help you easily remember the qualities that make a good dashboard, just remember the acronym “VITAL.”
Choosing agile metrics that will be most effective in measuring application success is a challenge, and then tracking those metrics can be tricky as well. But with a good strategy, agile metrics can be a powerful tool for sharing the team’s progress and identifying existing and possible roadblocks. These meaningful metrics can reduce confusion and bring clarity throughout the application development cycle.
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.
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.
We’ve all been placed in the situation where a boss asks you to perform more work than you can possibly handle. Johanna Rothman knows firsthand that there is a better way to respond that benefits you and your manager.
Our latest generation of programmers, project managers, and testers is perceived to be uninterested, unmotivated, and difficult to manage. Jason Garber presents innovative techniques you can use to lead your next rising star.
To complement functional validation, software teams are expected to validate performance. But, according to Jun Zhuang, you must be prepared to invest time, personnel, and resources to benefit from performance testing.
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, Mike Trites, a senior test consultant, talks about his upcoming presentation at STAREAST 2014, the future of metrics, the importance of improving the efficiency of your metrics, and even an interesting take on the old phrase that numbers never lie.
Pat Arcady is an agile and executive coach with FreeStanding Agility. In this interview, Pat discusses ways conflict manifests itself in an organization, the importance of nonviolent communication, and a useful four-step protocol for achieving positive outcomes for all parties.
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.