Impact mapping is a strategic planning technique to help you manage goals, decide on priorities, and spot risks, as well as figure out solutions. One of the most important advantages of impact mapping is that it supports stakeholders while making roadmap decisions and let them adapt quickly to the changing business environment.
Imagine: you have a product which you have built with a development partner. They provide a full stack development team to secure the success of the product. Obviously, they are responsible for technical implementation and testing, but how can your in-house Product Manager make sure that the business vision is clearly transmitted to the people who will bring it to life?
Nowadays, it’s hardly a cutting-edge statement that quality assurance is ‘baked in’ to agile and lean iterative development approaches. But it’s important to mention that the quality-related activities differ according to the phases of the product life cycle. Why is that? Basically, the reason for a diversified QA approach lies in the needs and goals that originate in each phase's purpose. If your team's approach to quality and testing is the same regardless of the maturity of the product, you can be sure that something is not quite right.
Functional testing in Arabic - how to ensure the quality of the product? Building a digital product for a specific market and region, so different from your own, is always a challenge. To ensure the quality of the product, not only a QA specialist but the whole development team has to channel their efforts on the product and treat it as if it was their “own.”
We start each product with some kind of kick-off workshop that help the development team get to know the client’s business better. So far, we have used several approaches (e.g. user story mapping, product vision canvas, user journey). In this article, I would like to share with you our experience from the first two event storming workshops that we held.
