E6S-179 Agile Requirement Gathering - User Stories Part 2

E6S-Methods Lean Six Sigma Performance Podcast with Aaron Spearin & Jacob Kurian

Like / Dislike **We'd Appreciate Your Opinion**

Email me: [e-mail]

Leave a Review! http://bit.ly/E6S-iTunes;

Donations: http://bit.ly/E6S-Donate

Intro: Welcome to the E6S-Methods podcast with Jacob and Aaron, your weekly dose of tips and tricks to achieve excellent performance in your business and career. Join us as we explore deeper into the practical worlds of Lean, Six Sigma, Project Management and Design Thinking. In this episode number 179, we continue with part 2 of our "Agile Requirements Gathering - User Stories" series. If you're just tuning in for the first time, find all our back episodes on our podcast table of contents at e6s-methods.com. If you like this episode, be sure to click the "like" link in the show notes. It's easy. Just tap our logo, click and you're done. Tap-click-done! Here we go. http://bit.ly/E6S-179 Leave a Review! http://bit.ly/E6S-iTunes

***Purchase Detailed 2000-2016 Salary Trend Analysis***

II What is a User Story?

a. Describes the functionality or feature a product will deliver to a user

b. Helps to create a simplified description of a requirement

c. States the requirements from the viewpoints of different stakeholders

d. More ‘Human’ than standard functional requirements

i. Should require the team to have a conversation

ii. Stories should evolve with scrum team discussion and technical feedback

e. A common template used for user stories is:

i. “As a < role >, I want to < do what > so I can < benefit how > .”

f. How does someone gather the requirements for a User Story?

i. Understanding the needs of the Customer / Client

1. Jobs to be Done

2. Features or Functionality that clients are looking for

3. Feedback from the clients/users

4. Usage Analytics

g. New Research available

h. Hypothesis that the team would like to prove

III Different people could be providing information in different formats. What becomes critical is the ability to synthesize them and present them in a way of what is the problem that the user/customer is facing.

Outro: Thanks for listening to episode 179 of the E6S-Methods podcast. Don't forget to click "like" or "dislike" for this episode in the show notes. Tap-click-done! If you have a question, comment or advice, leave a note in the comments section or contact us directly. Feel free to email me "Aaron," [e-mail], or on our website, we reply to all messages. If you heard something you like, then share us with a friend or leave a review. Didn't like what you heard? Join our LinkedIn Group, and tell us why. Don't forget you can find notes and graphics for all shows and more at www.E6S-Methods.com. "Journey Through Success. If you're not climbing up, you're falling down." Leave a Review! http://bit.ly/E6S-iTunes

Like / Dislike **We'd Appreciate Your Opinion**