Mobile apps are a necessity for companies of all sizes, and apps are getting more complex all the time. That along with the dizzying array of devices requires a well thought-out mobile testing strategy. And… More
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 the team into a higher rate of efficiency. You can view part 1 here.
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.
If you’ve been in the industry for a long time, you’ll probably remember when test teams sat in their own secluded area, idly waiting for code handoff, and were discouraged from “bothering” developers. There may have been a lot of running around to qualify builds, do smoke tests, verify bug fixes, and comb through the build notes for feature changes.
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: