ron salaj's List: human-centered design & agile methods

• User Stories are a simple way of capturing user requirements throughout a project – an alternative to writing lengthy requirements specifications all up-front.
• A User Story is a simple statement about what a user wants to do with a feature of the software, written from a user’s perspective.
• User Stories should be written in business language that is understandable to all.
• A User Story should focus on the who, what and why of a feature, not how.
• As a [user role], I want to [goal], so I can [reason].
• Product Backlog.
• users will often tell stories about the failings of their current system or process.
• Try capturing these stories as User Stories. On cards. While you’re in the meeting. As they are told.
• In traditional development projects, these stories often aren’t captured as they are told, they’re captured in a lengthy analysis process and captured in a lengthy document; a format that isn’t particularly user friendly.

7 more annotations...

• Welcome changing requirements, even late in
   development.
• The most efficient and effective method of
   conveying information to and within a development
   team is face-to-face conversation.
• Working software is the primary measure of progress.
• Simplicity--the art of maximizing the amount
   of work not done--is essential.
• The best architectures, requirements, and designs
   emerge from self-organizing teams.

3 more annotations...

• That is, while there is value in the items on
   the right, we value the items on the left more.

• provides an introduction to a range of tools and techniques for both idea generation (Creativity) and converting those ideas into reality (Innovation)