In software engineering, the elicitation of information is a crucial phase where the requirements analysis must be free of ambiguities in order to define the customer’s needs to build a quality product, service or technological solution.
That is why user stories become an important part of the identification of functionalities, since they are a general and informal explanation of a software function written from the end user’s perspective. Its purpose is to articulate how it will provide value to the customer.

 

The topics you will learn are:

Knowledge in agility

• Agile
• Waterfall model vs Agile
• Manifesto for agile software development
• Agile Manifesto Principles

User Stories

• What is a User Story?
• Origin of User Stories
• User Story Components
• Why Use User Stories?
• Benefits of User Stories
• User Stories and Agile Mechanisms

Creating User Stories

• User Stories Structure
• Example of a User Story
• Key Points in US

Agile Mechanisms and Techniques for Building User Stories
INVEST and How It Works

• INVEST Method
• Independent
• Negotiable
• Valuable
• Estimable
• Small
• Testable

SPIDR Technique and How It Works

• SPIDR – Technique for splitting User Stories
• Spikes (Proof of Concept)
• Path
• Interfaces
• Data
• Rules

Estimation and Value in User Stories

• Estimation and Value
• Assigning Value to a User Story
• Prioritizing User Stories
• How to Prioritize US

MoSCoW Technique

• What is the MoSCoW Technique?
• MoSCoW Characteristics
• Must have
• Should have (Should include)
• Could have (Could include)
• Won’t have (Won’t have)
• How to Apply MoSCoW
• MoSCoW Estimation Example

Defining User Stories

Acceptance Criteria

• What are the Acceptance Criteria?
• Acceptance Criteria
• Acceptance Criteria Structure

Slicing Practice

• What is Slicing?
• Slicing and Uncertainty
• Why Slicing?
• Benefits of Slicing

Writing User Stories

• How to Write US
• Conjunctions and Connectors
• Example of Connectors

Example of a User Story

Story Points

• Story Points
• Team Speed
• Factors for determining Story Points

Size of User Stories

• How small should a User Story be?
• Topics
• Epics
• Initiatives/ Features/ Characteristic
• Tasks
• User Story Sizes
• Unit of Measurement by Conversation Type
• Example of Estimation with MoSCoW

Minimum Viable Product MVP

• What is MVP(Minimum Viable Product)?
• What Does an MVP Enable?
• How to Build an MVP

User Story Mapping

• What is User Story Mapping?
• User Story Mapping
• How Story Maps Work
• Key Factors of User Story Mapping
• Benefits of User Story Mapping
• Who participates in User Story Mapping?
• When to Apply User Story Mapping

How to Turn User Story Mapping into a Development Strategy

• Development Strategy

How to Create the User Story Map in 7 Steps?

• Step 1.
• Step 2.
• Step 3.
• Step 4.
• Step 5.
• Step 6.
• Step 7.

Example of User Story Mapping

• In Conclusion “User Story Mapping

Agile User Stories Overview

• Limits of User Stories
• Generalities

• 24/7 e-learning platform
• Web Simulator
• Exercises
• Examen name: Agile User Stories Certified
• Examination Format: Multiple Choice Questions
• Duration of the exam: Once the exam begins, candidates have 1 hour (60 minutes) to complete the exam.
• Number of questions: 40
• Percentage of approval: 65%.
• Languages available: Spanish

On demand

This certification is focused on the following profiles:

• People familiar with agile frameworks
• Scrum Master
• Product Owner
• Scrum Advanced
• Agile Coach
• Managers
• Developers
• Team leaders

Price: USD‎‏‏‎ ‎100.00

Payment Methods:

– If you are located in Argentina, choose the currency “ARS” on the web and then pay by bank transfer or Mercado Pago (ask for other means of payment).

– If you are outside of Argentina, choose the currency “USD” and then pay by PayPal (ask for other means of payment).

 

Paypal is available for all countries!