3 Ways To Spice Up Your Next Retrospective (Part 1)

3 Ways To Spice Up Your Next Retrospective

Sprint retrospective is an opportunity for agile teams to reflect on their way of working, and to continuously improve in what they do. No matter how productive or successful your team is, there’s always room for improvement. There are always ways to do things better. The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Sprint Retrospective occurs after the Sprint Review and provides a formal opportunity to focus on inspection and adaptation.

Continue reading “3 Ways To Spice Up Your Next Retrospective (Part 1)”

Facebooktwittergoogle_pluspinterestlinkedinmail

Why thinking like a customer is so important for QA teams

Quality assurance traditionally entailed only of teams evaluating the code and ensuring that nothing was breaking or performing abnormally. In these setups, there wasn’t time to worry about how end users would take it, it just mattered that the app would work. However, in today’s world of endless software, quality assurance must make the customer the priority driving their work. Thinking like the customer is going to be crucial for QA teams for a few important reasons:

Continue reading “Why thinking like a customer is so important for QA teams”

Facebooktwittergoogle_pluspinterestlinkedinmail

Celebrate Microsoft’s Visual Studio 20th anniversary with TestArchitect for Visual Studio

MS-Studio-20th--TA

Microsoft’s Visual Studio is kick starting their 20th anniversary with the new launch of their upgraded tool: Visual Studio 2017. The IDE improvement will be ready to download on Tuesday March 7, 2017, and will coincide with Microsoft’s virtual event taking place March 7 – 8th.

Continue reading “Celebrate Microsoft’s Visual Studio 20th anniversary with TestArchitect for Visual Studio”

Facebooktwittergoogle_pluspinterestlinkedinmail

How to define your testing scope

Development and quality assurance teams are under strict deadlines to send out deliverables and complete other tasks within a sprint. As these timeframes continue to tighten, it’s important for teams to effectively use agile testing methodologies to keep up with all requirements. Teams must realize that a significant amount of available time will go toward creating features, and that there isn’t going to be infinite space for QA processes.

Continue reading “How to define your testing scope”

Facebooktwittergoogle_pluspinterestlinkedinmail