Agile teams use the term spike to refer to a time-boxed research activity.
TOOLS TRAINING LIVE WEBINARS USER-GENERATED
|Books Events Links White Papers Wikis|
|Language:||All English Arabic French Japanese Korean Portuguese Romanian Russian Spanish|
|Access:||All Free Premium|
|All A B C D E F G H I J K L M N O P Q R S T U V W X Y Z|
98 items found
The Sprint is an iteration of work, typically 1 month or less in duration, where a potentially releasable product increment is produced. Sprints have consistent durations throughout a development effort. A new Sprint starts immediately after the conclusion of the previous Sprint. The Sprint contains several other events such as Sprint Planning, Daily Scrums, the Sprint Review and the Sprint Retrospective, in addition to the development work.
Rather than focus on the concept of Sprint 0 for initiation, it is better to focus on the underlying principles of Lean and Agile.
Are you familiar with the most important event in Scrum?
The retrospective meeting serves as a way for the team to analyze itself and, as a result, make up a plan of improvements for its benefit. Here are some tips and tricks--and an easy strategy--to have an effective retrospective meeting.
Let one expert tell you why a Sprint Zero makes little to no sense at all.
A technique used to examine the different forces affecting the various external and internal players that an organization is required to deal with. It also allows for formulation of strategies in dealing with the stakeholders, based on the cultural, structural, and resource limitations and potentials of the enterprise. A stakeholder is anyone (individual or organization) with a "stake" in the outcome of an enterprise change effort and/or is affected by the resulting change.
Stakeholder Engagement|Stakeholder Engagement