Technical Spikes: How to?

  • Contemplate what problem are we trying to solve?
  • How does this falls into our software strategy/software architecture?
  • How it affects the increment/outcomes of the product?
  • What work packages in the backlog/roadmap can we not complete because of this?
  • What is value projected?
  • What is the time-box/frame?
  • What software/materials/equipment/man hours do you need to support the spike?
  • Will it help the COE or benefit a large team?
  • Demo the working and tested increment/software.
  • what we learned?
  • How the spike made a difference to the as is status?
  • What work packages in the backlog we could not complete?
  • If it doesn’t work, do you need more time/resources?
  • How does this tie into our software strategy/software architecture?
  • What is the value added?
  • What would it take to roll this out to the Org?
  • Ask Peers for feedback?

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store