Answer»
Sprint Zero: The Sprint Zero is the initial sprint of a team, which occurs before the formal start of the project, before official documentation, and/or before the team's inception. Sprints are intended for the Development Team to develop a minimum number of User Stories, story mapping, a project skeleton, and develop a full-fledged product. As part of sprint zero, the team answers the following questions:
- What is the duration of sprints?
- When is a sprint considered completed?
- What tools do we use, and how should they be used?
- How should we work? Would it be best to formalize our agreement in writing?
Spike: This shorthand term refers to "spike solutions". It represents the initial investigation or research of a software solution (which could be a feature, a bug fix, a migration task, etc.). Instead of documenting what needs to be done, try to construct a quick, throwaway solution to get a better sense of the scope of work (by validating the technical assumptions). Ideally, spikes should be scheduled along with all other features (bugs, fixes, etc.) during sprints. If a team is unable to agree on an estimate, it may realize the need for a spike.
|
