About Spikes
A spike solution, or spike, is a technical investigation. It's a small experiment to research the answer to a problem. For example, a programmer might not know whether Java throws an exception on arithmetic overflow. A quick ten-minute spike will answer the question.
Group items tagged
STOP EVERYTHING AND READ THIS IMMEDIATELY "How to - 0 views
-
STOP EVERYTHING AND READ THIS IMMEDIATELY "How to Spot Good Gelato from 15 Feet Away" http://t.co/TWCoDMJhoa
Books to read | AgileSparks - 0 views
kanban-for-software-engineering-apr-242.pdf (application/pdf Object) - 0 views
-
Comprehensive write-up of Lean+Kanban. Heavy but worth reading
Lean und Kanban: Kanban and Understanding - 0 views
-
What a read to start the week - brilliant RT @arneroock: New Blog Post "Kanban and Understanding" http://t.co/mwjYnrFbwX / cc @asplake
James Shore: The Art of Agile Development: Spike Solutions - 0 views
-
-
Performing the Experiment The best way to implement a spike is usually to create a small program or test that demonstrates the feature in question. You can read as many books and tutorials as you like, but it's my experience that nothing helps me understand a problem more than writing working code. It's important to work from a practical point of view, not just a theoretical one.
-
Writing code, however, often takes longer than reading a tutorial. Reduce that time by writing small, standalone programs.
- ...2 more annotations...
Invitation-based SAFe implementation - Scaled Agile Framework - 0 views
daily standup wheel – AgileSparks - 0 views
Tip of the Daily Cards – How to Make Daily Meetings Work Better – AgileSparks - 0 views