Writing Effective User Stories: Helping Stakeholders Discover and Define IT Requirements

User Stories Defined -Express Stakeholder Requirements in User Story format 2 lectures 10:44 Welcome to the Course preview Learn the content of this course and assess its value to you. Introduction to User Stories preview User Stories are a great method for expressing stakeholder requirements for an IT solution. The first lecture is a general overview of User Stories.Learning Objectives

• Understand Business, Stakeholder, Solution and Transition Requirements as identified by the IIBA(TM).
• List the components of a User Story
• Express Stakeholder Requirements in User Story format
• Realize who should be writing User Stories
• Recognize when to write use User Stories in the Software Development Life Cycle
• Discuss User Story Elaboration to identify functional and non-functional requirements

User Stories Defined -Express Stakeholder Requirements in User Story format 2 lectures 10:44 Welcome to the Course preview Learn the content of this course and assess its value to you. Introduction to User Stories preview User Stories are a great method for expressing stakeholder requirements for an IT solution. The first lecture is a general overview of User Stories.Learning Objectives

• Understand Business, Stakeholder, Solution and Transition Requirements as identified by the IIBA(TM).
• List the components of a User Story
• Express Stakeholder Requirements in User Story format
• Realize who should be writing User Stories
• Recognize when to write use User Stories in the Software Development Life Cycle
• Discuss User Story Elaboration to identify functional and non-functional requirements

Welcome to the Course preview Learn the content of this course and assess its value to you. Welcome to the Course preview Learn the content of this course and assess its value to you. Welcome to the Course preview Learn the content of this course and assess its value to you. Welcome to the Course preview Learn the content of this course and assess its value to you. Learn the content of this course and assess its value to you. Learn the content of this course and assess its value to you. Introduction to User Stories preview User Stories are a great method for expressing stakeholder requirements for an IT solution. The first lecture is a general overview of User Stories.Learning Objectives

• Understand Business, Stakeholder, Solution and Transition Requirements as identified by the IIBA(TM).
• List the components of a User Story
• Express Stakeholder Requirements in User Story format
• Realize who should be writing User Stories
• Recognize when to write use User Stories in the Software Development Life Cycle
• Discuss User Story Elaboration to identify functional and non-functional requirements

Introduction to User Stories preview User Stories are a great method for expressing stakeholder requirements for an IT solution. The first lecture is a general overview of User Stories.Learning Objectives

• Understand Business, Stakeholder, Solution and Transition Requirements as identified by the IIBA(TM).
• List the components of a User Story
• Express Stakeholder Requirements in User Story format
• Realize who should be writing User Stories
• Recognize when to write use User Stories in the Software Development Life Cycle
• Discuss User Story Elaboration to identify functional and non-functional requirements

Introduction to User Stories preview User Stories are a great method for expressing stakeholder requirements for an IT solution. The first lecture is a general overview of User Stories.Learning Objectives

• Understand Business, Stakeholder, Solution and Transition Requirements as identified by the IIBA(TM).
• List the components of a User Story
• Express Stakeholder Requirements in User Story format
• Realize who should be writing User Stories
• Recognize when to write use User Stories in the Software Development Life Cycle
• Discuss User Story Elaboration to identify functional and non-functional requirements

Introduction to User Stories preview User Stories are a great method for expressing stakeholder requirements for an IT solution. The first lecture is a general overview of User Stories.Learning Objectives

• Understand Business, Stakeholder, Solution and Transition Requirements as identified by the IIBA(TM).
• List the components of a User Story
• Express Stakeholder Requirements in User Story format
• Realize who should be writing User Stories
• Recognize when to write use User Stories in the Software Development Life Cycle
• Discuss User Story Elaboration to identify functional and non-functional requirements

User Stories are a great method for expressing stakeholder requirements for an IT solution. The first lecture is a general overview of User Stories.Learning Objectives

• Understand Business, Stakeholder, Solution and Transition Requirements as identified by the IIBA(TM).
• List the components of a User Story
• Express Stakeholder Requirements in User Story format
• Realize who should be writing User Stories
• Recognize when to write use User Stories in the Software Development Life Cycle
• Discuss User Story Elaboration to identify functional and non-functional requirements

User Stories are a great method for expressing stakeholder requirements for an IT solution. The first lecture is a general overview of User Stories.Learning Objectives

• Understand Business, Stakeholder, Solution and Transition Requirements as identified by the IIBA(TM).
• List the components of a User Story
• Express Stakeholder Requirements in User Story format
• Realize who should be writing User Stories
• Recognize when to write use User Stories in the Software Development Life Cycle
• Discuss User Story Elaboration to identify functional and non-functional requirements

Apply 5 Rules for Writing Effective User Stories 5 lectures 40:58 Rule 1: Keep Your User Story Simple The next 5 lectures unveil a series of five rules that will make your user stories more effective. If you apply these rules to your writing, over time they will become automatic allowing you to become more agile in producing them.Given that, let's talk rules. Rule number 1, the focus of this lecture, addresses the sentence structure of a User Story. Well-structured User Stories express a single action to achieve a specific goal from the perspective of a single role. Trying to express too much in a User Story adds confusion and increases the amount of discussion needed for developers to understand what the story really means. Rule 2: Express the What, Not the How When writing user stories, stakeholders knowledgeable about the role should focus on the business result that the IT solution will enable while leaving technology decisions up to the developers. What can you as the author do to make your life and your developers’ lives easier? In a word, lots. Rule 2 in the series states, “An effective user story emphasizes ‘what’ should be done, not ‘how’ to do it.” Questions answered in this chapter:

• How can you make sure that your user story expresses the what and not the how?
• Why is it important that you distinguish between what and how?

Rule 3: Write Relevant User Stories Good user stories are relevant to the project, unambiguous, and understandable to knowledge peers. As the author of User Stories, you need to focus on writing stories that the delivered solution will provide. Ensuring that your User Stories are relevant reduces the time wasted writing and elaborating unneeded User Stories. Questions answered in this chapter:

• How can you decide whether a potential user story is relevant?
• Why is relevance important?

Rule 4: Avoid Ambiguity in Your User Story Ambiguity is communication's biggest threat. If your User Story contains ambiguous words or phrases, the solution may not be what you desire. Questions answered in this chapter:

• How can you ensure that your audience understands your user story as you intend it?
• How does ambiguity affect the quality of the solution?

Rule 5: Develop Measurable Non-Functional Requirements Non-functional requirements are your best weapon in the war against unsatisfactory performance in IT solutions. Whether you use User Stories or conventional requirements, non-functional requirements are king. Questions answered in this chapter:

• How do you express non-functional (quality) requirements?
• What value do non-functional requirements add to your user stories?

Apply 5 Rules for Writing Effective User Stories. 5 lectures 40:58 Rule 1: Keep Your User Story Simple The next 5 lectures unveil a series of five rules that will make your user stories more effective. If you apply these rules to your writing, over time they will become automatic allowing you to become more agile in producing them.Given that, let's talk rules. Rule number 1, the focus of this lecture, addresses the sentence structure of a User Story. Well-structured User Stories express a single action to achieve a specific goal from the perspective of a single role. Trying to express too much in a User Story adds confusion and increases the amount of discussion needed for developers to understand what the story really means. Rule 2: Express the What, Not the How When writing user stories, stakeholders knowledgeable about the role should focus on the business result that the IT solution will enable while leaving technology decisions up to the developers. What can you as the author do to make your life and your developers’ lives easier? In a word, lots. Rule 2 in the series states, “An effective user story emphasizes ‘what’ should be done, not ‘how’ to do it.” Questions answered in this chapter:

• How can you make sure that your user story expresses the what and not the how?
• Why is it important that you distinguish between what and how?

Rule 3: Write Relevant User Stories Good user stories are relevant to the project, unambiguous, and understandable to knowledge peers. As the author of User Stories, you need to focus on writing stories that the delivered solution will provide. Ensuring that your User Stories are relevant reduces the time wasted writing and elaborating unneeded User Stories. Questions answered in this chapter:

• How can you decide whether a potential user story is relevant?
• Why is relevance important?

Rule 4: Avoid Ambiguity in Your User Story Ambiguity is communication's biggest threat. If your User Story contains ambiguous words or phrases, the solution may not be what you desire. Questions answered in this chapter:

• How can you ensure that your audience understands your user story as you intend it?
• How does ambiguity affect the quality of the solution?

Rule 5: Develop Measurable Non-Functional Requirements Non-functional requirements are your best weapon in the war against unsatisfactory performance in IT solutions. Whether you use User Stories or conventional requirements, non-functional requirements are king. Questions answered in this chapter:

• How do you express non-functional (quality) requirements?
• What value do non-functional requirements add to your user stories?

Rule 1: Keep Your User Story Simple The next 5 lectures unveil a series of five rules that will make your user stories more effective. If you apply these rules to your writing, over time they will become automatic allowing you to become more agile in producing them.Given that, let's talk rules. Rule number 1, the focus of this lecture, addresses the sentence structure of a User Story. Well-structured User Stories express a single action to achieve a specific goal from the perspective of a single role. Trying to express too much in a User Story adds confusion and increases the amount of discussion needed for developers to understand what the story really means. Rule 1: Keep Your User Story Simple The next 5 lectures unveil a series of five rules that will make your user stories more effective. If you apply these rules to your writing, over time they will become automatic allowing you to become more agile in producing them.Given that, let's talk rules. Rule number 1, the focus of this lecture, addresses the sentence structure of a User Story. Well-structured User Stories express a single action to achieve a specific goal from the perspective of a single role. Trying to express too much in a User Story adds confusion and increases the amount of discussion needed for developers to understand what the story really means. Rule 1: Keep Your User Story Simple The next 5 lectures unveil a series of five rules that will make your user stories more effective. If you apply these rules to your writing, over time they will become automatic allowing you to become more agile in producing them.Given that, let's talk rules. Rule number 1, the focus of this lecture, addresses the sentence structure of a User Story. Well-structured User Stories express a single action to achieve a specific goal from the perspective of a single role. Trying to express too much in a User Story adds confusion and increases the amount of discussion needed for developers to understand what the story really means. Rule 1: Keep Your User Story Simple The next 5 lectures unveil a series of five rules that will make your user stories more effective. If you apply these rules to your writing, over time they will become automatic allowing you to become more agile in producing them.Given that, let's talk rules. Rule number 1, the focus of this lecture, addresses the sentence structure of a User Story. Well-structured User Stories express a single action to achieve a specific goal from the perspective of a single role. Trying to express too much in a User Story adds confusion and increases the amount of discussion needed for developers to understand what the story really means. The next 5 lectures unveil a series of five rules that will make your user stories more effective. If you apply these rules to your writing, over time they will become automatic allowing you to become more agile in producing them.Given that, let's talk rules. Rule number 1, the focus of this lecture, addresses the sentence structure of a User Story. Well-structured User Stories express a single action to achieve a specific goal from the perspective of a single role. Trying to express too much in a User Story adds confusion and increases the amount of discussion needed for developers to understand what the story really means. The next 5 lectures unveil a series of five rules that will make your user stories more effective. If you apply these rules to your writing, over time they will become automatic allowing you to become more agile in producing them.Given that, let's talk rules. Rule number 1, the focus of this lecture, addresses the sentence structure of a User Story...