Scrum

Software development methodology.

http://scrumtrainingseries.com/Intro_to_Scrum/Intro_to_Scrum.htm

http://scrumreferencecard.com/scrum-reference-card/

Roles

Product backlog

Sprint backlog

Sprint tasks

User story

Agile modeling

http://www.agilemodeling.com/artifacts/userStory.htm

User stories are very slim and high-level requirements artifacts.

http://scrummethodology.com/scrum-user-stories/

User stories document requirements with particular attention to the end user’s point of view.

Because user stories are oriented to reflect the desires of the end user, they help developers remain focused on the customer.

As a (role) I want (something) so that (benefit).

Extreme programming

Deliver the software you need as you need it.

Extreme Programmers constantly communicate with their customers and fellow programmers.

http://www.extremeprogramming.org/rules.html

http://www.extremeprogramming.org/rules/userstories.html

User stories should only provide enough detail to make a reasonably low risk estimate of how long the story will take to implement.

When the time comes to implement the story developers will go to the customer and receive a detailed description of the requirements face to face.

You should try to keep stories focused on user needs and benefits.

Scrum (last edited 2015-01-21 23:17:21 by 23)