Yeah, I think it works well. Of course, it also depends on which state the API is in. E.g. it’s different if you’re integrating with API that is working for years and it’s stable vs API that is also in development. For us, it was the second case. And this proof-of-concept really helps, because we could give the other vendor early feedback about what they should improve. Still, there was plenty of discussion with them during the development itself. But yeah, it helped. We would definitely do it again.
For me, this proof-of-concepting is actually part of the shaping phase. Basically, it’s technical shaping and you need to dedicate time for it. We start this in cool-down, but we didn’t finish, so we simply say “okay, this is important, let’s postpone the next cycle for a week, and let’s really finish the proof-of-concept to make sure there will be no surprises.” So, yes it was a little bit unorthodox because we had 2 weeks of cool-down, then 1 week of “technical shaping” and then 6 weeks of the cycle.