In part 1, we explored two concepts, the Starfish Retrospective and the Three little Pigs, each a retrospective activity. They are designed to reflect and analyze an agile team’s way of working to help adapt… More
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:
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.
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.
For as long as I have been in software testing, there has been a constant demand to grow technology, grow skills, automate more, and do it all faster (that is a given). What has been so remarkable recently is the rate at which these demands shift gears and move in different directions, new products, and evolving technologies.