How We Do Spikes
medium.com
How We Do Spikes
1–10 of 15 posts
Re: How We Do Spikes
#2I found this very helpful. Thank you for the advice, Sophie.
Re: How We Do Spikes
#3Great article! What did you end up replacing the asset pipeline with?
Re: How We Do Spikes
#4This is very good article - gave me much info into how I could manage spikes. Thank you
Re: How We Do Spikes
#5The idea of putting a timebox around a spike is really good. Then the spike is done whenever you get an answer or the timebox runs out, and "We don't know yet" is an acceptable answer. That clearly distinguishes spikes from other development stories.
So often, our development stories depend on assumptions about how/if a new technology is going to make the change we want to make work. It might not work, and estimating with unfamiliar tech is really hard.
Re: How We Do Spikes
#6Great article! What did you end up replacing the asset pipeline with?
We decided to use Gulp and a bunch of real frontend tools like Browserify and Sass. We moved all the assets to a `frontend` directory, uninstalled the gem wrappers for js libraries and switched to npm to manage them. The assets pipeline is good for small apps, but when you grow, you need the right tools. Frontend tools are good for frontend, no matter how you like or dislike the Javascript ecosystem.
Re: How We Do Spikes
#7Following this approach is very effective for getting R&D credits in Canada. Documenting your process in a lightweight manner like this helps tremendously.
Re: How We Do Spikes
#8Great article! What did you end up replacing the asset pipeline with?
I'm curious about this too. I'm at the point in my current project where the asset pipeline is becoming somewhat of a burden, and want to know what others have done to replace it or mitigate it.
Re: How We Do Spikes
#9Nice article, thanks for sharing.
In addition to the great information you've provided, we identify features/decisions/choices that require spikes based on assessment that they are high risk and/or we have low confidence in our estimate. In addition, we sometimes use spikes to break xxx-large estimates into smaller pieces.
That way, until a project/plan/item has low (enough) risk, and high (enough) confidence, it needs more spikes.
We've found this model is a great way of identifying what needs spiking, and when a spike is 'done'. And, it also helps to ensure spikes don't end up consuming too much time.
Hope this is useful.
Re: How We Do Spikes
#10Nice article, thanks for sharing. In addition to the great information you've provided, we identify features/decisions/choices that require spikes based on assessment that they are high risk and/or we have low confidence in our estimate. In addition, we sometimes use spikes to break xxx-large estimates into smaller pieces. That way, until a project/plan/item has low (enough) risk, and high (enough) confidence, it nee…
Yes, I think it is a great idea to use spike to break down large estimates!