Serious Scrum
Published in

Serious Scrum

6 common mistakes when using spikes

During refinement a team member says:”I have no clue how to build this feature”. She warns we should not start working on the feature before doing a spike.

Mentioning spikes often creates confusion in a team. Every team member has their own opinion about what a spike is and the right time to use one. I was part of teams that wanted a spike for almost everything they worked on. I also worked with teams that rarely used spikes. Both approaches were suboptimal. When is using a spike appropriate?

--

--

--

Content by and for Scrum Practitioners.

Recommended from Medium

Continuous Integration with Gitlab

Network Routing

CAN Conformance: The Ultimate Testing Method for CAN and CAN FD Protocol Software

Perfect Number

NXDF X EdenSol Partnership Event

All change

Enterprise software program agency Locofy.ai has secured $3 million in a funding spherical

Podcast S3E4: John and Adam Isom — Skipping College, CS Degree vs Launch School, and Making Six…

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
Maarten Dalmijn

Maarten Dalmijn

Product Management Leader. Follow me at https://mdalmijn.com

More from Medium

How to Measure Agile Maturity

How you can forecast the future in software development

Must haves…. Before getting started with adopting Agile Ways of Working — Part 1

Source of Image : Ekipa Malaysia

How Work On The Scrum Team Survey Taught Us 10 Lessons About Agile