In my current company, I began to implement flexible methods, and we set off on a good start. We passed our first release and will soon begin our second release. Although management agreed not to introduce any new work during the iteration, showing that release / function planning is ongoing work. At the same time, I found that we are fighting for where / when to match the spikes that need to be performed during the iteration for the next iteration.
Currently, Management / Project managers collect spikes and give each respective developer the necessary spike at the beginning of the iteration with the notion that the developer will create tasks for the spike in the next environment, so work can be scheduled for the next iteration.
While this works, it seems that there is a better way to put together the requirements around the spikes. How do everyone else plan their time for spikes? We don’t assign all developers 80 hours to iterate, so there is a slight respite for meetings / email / bursts, etc.
Speaking, I want the management not to ask for spikes, if they do not know that the work will be done in the next iteration. Several times they asked for several spikes just to not plan work.
Any suggestions would be greatly appreciated!
source
share