... you will never turn back
(Munich, Germany) Some time ago, I wrote about the value taken with the execution of Proof of Concepts (POCs), and how important they are to give us confidence for future decisions. I would like to go back to this matter because I believe POCs are an important starting points to scale product complexity. At the same time, there is a task we can handle in order to improve product quality: User acceptance tests (UAT). So if we do it well
(Berlin, Germany) Sometimes the most obvious Agile concepts are not so easy to be applied when we need to make a practical usage of them. Specially if we need to bring into a consistent and common understanding a product or portfolio vision for later implementation. My goal with this post is to share a very personal opinion about how and whom should fulfill those Agile requirements levels.
A backlog is such an important asset for each Agile Team and even more important for a company who understands the value to demand for high quality content and well organized backlogs. What I would like to share with you today is a set learnings I did since I’m working in Agile.
Sometime it can be really a challenge to make a decision about which Proof of Concept should we develop out of the infinite number of feature we would like to add to our product.