When should you engage with the testing team on waterfall projects?

I appreciate that most software development these days is done using the 'agile methodology' or a variation thereof. With agile, the testing team is (or at least should be) heavily involved with every sprint.

However, many organisations also deliver other types of projects that don’t have a continuous development path. These are one-and-done projects like bringing in or patching a 3rd party’s software; upgrading or replacing hardware or a whole range of changes that can impact your user base.

Best Practices for Virtual UAT

Today we welcome back our popular guest author, Renée Elizabeth Mineart.

If I were asked to encapsulate what makes humans unique in a single sentence, I’d probably say: “...our ability to achieve the impossible.” This trait is often best demonstrated when we are faced with adversity - a planet-wide pandemic, for example.

A Safe Environment for Failure

Today we welcome back our popular guest author, Renee Mineart.

In my previous blog on this topic, I introduced a few ideas that might improve your communication with your UAT testers and how to set expectations on what you want them to do.

I’d now like to expand on this and explore the ways you can provide a safe environment for failure in order to promote success. To do this, I’d like to take you back in time to 1990.

Our Communication Styles

Today we welcome back our popular guest author, Renée Elizabeth Mineart.

Welcome back to my series on how to successfully deliver a failed project. If you’ve not read the introductory blog post yet, it can be found here. We left off talking about communication and I’d like to dive a bit deeper into this topic if I may.