3 Comments

Thanks for the shoutout Jordan! Glad you enjoyed the real example 😂

I found that too often a PoC is missing in migration projects. Even assuming you decide to start with a small part (whether it's a microservice/page/whatever), the underline assumption is often that there will be next steps, and there is no pause to reflect how it went.

I try to always start with migrating the smallest thing we can to production, and then pausing to assess how it went. How long did it take, versus how long did we think it'll take? What do the developers feel about it? Often it's hard to rely on data at this stage because as you mentioned it's a lagging indicator, so I'm ok with relying on conversations to decide if the PoC was a success.

Only after the small part is completely finished and released, I think it makes sense to plan the whole project. You'll learn so many things during that small part!

Expand full comment
Oct 20Liked by Jordan Cutler, Maxi Ferreira

Great stuff. The great thing about those 3 steps and it’s a foundation for how to execute any project, not just a migration project. Appreciate y’all sharing!

Expand full comment
author

Yeah, great call. Maxi was actually considering using the technical design doc template I had--which I think can also be used. But you can also make one that's slightly trimmed down and more specific to migrations too

Expand full comment