In Value Stream, Should we include Spikes as spikes are a preparation for a story and has technical approach and not demo able.

Hi Sid! Spikes are usually not part of the regular planned work. They are ad-hoc short-term experiments, tests or research, done only when needed, and done for the minimum sufficient and necessary, usually to make a better decision about something technical. They are not supposed to take a relevant amount of time, and should be timeboxed. I'd add them to the board just to create visibility for the entire team.

Hi Rafael, Thanks for your response, I wanted to know how to map spikes and it efforts in a value stream implement as spike are technical and cannot be demoed and would bring value until they are implement, however spike are needed to be investigated in a technical upgrade , what would be a better approach to map the efforts and should they be done before a PI planning and if needed to be taken up during the sprint should we track them as a task.

Hi Sid! Could you please clarify your question? What do you mean by including spikes in a value stream? A spike is usually an amount of time allocated for researching or experimenting for gaining the knowledge necessary to reduce a technical risk. A value stream is a defined set of =activities performed to deliver value to the end customer. One or more spikes can be part of a sprint or a flow of work, but they are done as necessary - they are not part of the regular process.