E6S-178 Agile Requirement Gathering - User Stories Part 1

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 178, Jacob reviews the process of gathering design requirements within the agile framework in part 1 of this "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-178 Leave a Review! http://bit.ly/E6S-iTunes

                                                                                                                                                                                   

I            Requirements Gathering

a.       Here’s a set of requirements usually provided to a team that they are expected to build a product off of.

i.      Product should have a steel body

ii.      Product should have 4 wheels

iii.      Product should have rubber attached to wheel

iv.      Product should have multi speed transmission

What is the product that you would build?

b.      Now, if the requirements were given in a slightly different way such as:

i.      As a user, I want to mow my lawn quickly and easily

ii.      As a user, I want to be comfortable while mowing my lawn

What would you build now??

c.       What is the difference between the two scenario’s?

i.      Scenario 1 spend more time giving the “how” I am expecting you to build or gave in detail what needed to be done without giving any context to “what” needs to be build and “why” its needs to be build.

ii.      Scenario 2 only explained the issue or the experience that the customer is looking for and why it is necessary for them.

d.      The method of representing the what and the why vs the how is what’s usually referred as User Story.

 

Outro: Thanks for listening to episode 178 of the E6S-Methods podcast.  Stay tuned for episode 179, "Agile Requirements Gathering - User Stories Part 2."  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," aaron@e6s-methods.com, 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**

 

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