Talk:Spike

(the SPIKE page is still being worked on).. I'll leave a note when I'm ready for other's to edit).

Hi everyone,

Can I start by thanking everyone for giving me back such great feedback. It's always fun to get new opinions and ideas about things.

I'll put something up on the WIKI soon and everyone can then take it from there.

Here are some comments from myself and I what I feel I have learned from this discussion.

- It seems that most of you are OK with just using the same namewith some explanation of it's roots..... so, that's what I'll use.. SPIKE. I'll even put a reference to XP (at least that's where I know it from). If someone knows of other sources, that could always be adjusted on the WIKI.

- I would like to thank Zsolt for the specific mention about not counting in the "points" or "velocity" for the release. I can see how my original message may have come across that way. I'll make it clear it's for Planning and allocating time for the team and the Artifact of Knowledge isn't something that has to be counted towards the Velocity (unless maybe you're an R & D company I guess).

- I understand from Garry that a sort of "informal" card thing might work where someone agrees to "squeeze" it in if it can be done without the team losing their commitment to work. Garry's comment was that likely the team will do it "if they can"... I agree that most teams would try...I'll try and make some distinction about this being related to if it HAS to get done or if it would be nice to get done.

- Mishkin and Mark talked a bit about software-specific vs. not. I think the example is definately software specific, and I'll show it as such but as a whole, I think it's a valuable tool for the tool-belt and could be used in any industry though... I'll see if I can find something appropriate out there (or maybe there's an artist in the group) that wants to send along for me to use when I'm at that point :->

- Some other really important factors were.

- Time-Boxed so that we stay focused - Learning is shared with other team members - Avenues explored

My take on "avenues explored" is that the idea of this would be that it's not just one person who takes the results of the Spike and decides the results, but shares the knowledge of what was learned for the team to decide how it benefits (or does not) benefit them.

I'll post an update when it's on the WIKI and it can be taken from there.

Thanks

Mike Caspar