Value of Technical Spikes
π Many times, in interest of moving fast, engineering teams forget the value of technical spikes.
π‘ Technical design reviews are useful, but going one step further and prototyping the most riskiest piece just enough to de-risk the project actually accelerates the execution.
π₯ It is most effective if the senior team member pairs with the engineer who wrote the technical design and executes the spike.
π¨βπ« Junior engineer can learn from senior team member, and spike execution happens fast too.
π In addition to de-risking, a prototype solution surfaces other technical nuances that are otherwise hard to uncover during tech design review.
πͺ Technical spike doesnβt have to be perfect, it just need to be good enough to build confidence in teamβs ability to execute the proposed solution.
What are your thoughts on technical spikes? Have you used them in your projects?