Engagement/MDN Durable Team/Agile glossary: Difference between revisions

Engagement/MDN Durable Team/Agile glossary (view source)

178 bytes added , 30 June 2016

canmove, Confirmed users

1,953

edits

Revision as of 23:59, 29 June 2016 (view source) Jswisher (talk \| contribs) (→‎Product Owner: Retrospective) ← Older edit		Revision as of 16:15, 30 June 2016 (view source) Jswisher (talk \| contribs) (→‎User Story) Newer edit →
Line 69:		Line 69:
	: As a (role), I want to (activity), so I can (goal).		: As a (role), I want to (activity), so I can (goal).

	One exception is when the team does not have enough information to formulate a user story in this format. These are designated by "[Research]" in the description, and should have Acceptance Criteria that will enable creating future user stories in the canonical format.		One exception is when the team does not have enough information to formulate or estimate a user story in this format. These are designated by "[Research]" in the description, and should have Acceptance Criteria that will enable creating future user stories in the canonical format. (In the Extreme Programming methodology, such an item is limited to a task, not a user story, and is referred to as a [http://agiledictionary.com/209/spike/ Spike].)