Udemy
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
Subscribe
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
Mastering Agile Technical User Stories and Spikes
Rating: 4.2 out of 5(64 ratings)
255 students

Mastering Agile Technical User Stories and Spikes

Learn everything you need to know to discover and write Technical User stories and Spikes.
Created bySanjeet Biswas
Last updated 6/2019
English

What you'll learn

  • Learn what differentiates a technical user story
  • Learn how to write clear, concise & effective technical user stories.
  • Learn how to determine the “user” or the "who" in a technical user story.
  • Learn what is a spike and when to use spikes
  • Learn how to write a clear and meaningful spike
  • Learn how to prioritize technical user stories & spikes in a product backlog.
  • Learn about anti-patterns w.r.t technical user stories.
  • Learn about anti-patterns w.r.t spikes.

Course content

1 section • 14 lectures • 1h 9m total length

  • Course Introduction1:42

    Introduction to course instructor and course outline.

  • Course Pre-requisite Refresher4:52

    Lecture provides a quick refresher on some of the course prerequisite.

  • What is a Technical User Story?2:02

    Lecture discusses the source and reason why one needs technical user stories.

  • Format of a Technical User Story4:01

    Lecture discusses the format that is most common to use to write a technical user story.

  • How to determine the USER or the "Who" for Technical user stories?4:15

    Lecture provides guidance on how one goes about determining the "who" or user for a given technical user story.

  • Examples of Technical User Stories13:37

    Lecture walks you through examples of technical user stories.

  • More examples of Technical User Stories9:28

    Lecture walks you through more examples of technical user stories.

  • Anti-pattern w.r.t Technical User Stories3:29

    Lecture walks you through technical user story related anti-pattern.

  • What is a Spike?4:09

    Lecture introduces the concept and definition of a spike.

  • Format of a Spike3:39

    Lecture discussed the way you write a spike.

  • Examples of Spikes7:19

    Lecture walks through spike examples.

  • Spike Anti-patterns3:31

    Lecture discusses common spike related anti-patterns.

  • Prioritizing Technical User Stories and Spikes5:23

    Lecture provides guidance on the factors to use to prioritize technical user stories and spikes.

  • Course Wrap Up!1:58

    It's time to wrap up.

Requirements

  • In order to get the most out of this course, you MUST take the prerequisite course titled, “Authoring Elegant and Meaningful Agile User Stories.” This course is available on Udemy.
  • Must have some basic familiarity with activities involved in developing an application in a software development company or a corporate environment.
  • Must be familiar with the difference between functional and non-functional requirement.
  • Optional course on Udemy you may take prior to taking this course, “Building a Smart Agile Product Backlog with User Stories”.

Description

A healthy and comprehensive product backlog also comprises of two additional elements - Technical User Story and Spike - in addition to user stories. A Technical User Story may sound like it is almost, somewhat the same as a User Story and yes it has many similarities to a User Story but a Technical User Story also has some key differentiators. In other words, even if you may how to write effective User Stories does not automatically mean that you will also be able to write appropriate Technical User Stories. Plus, you also need to know when a given work item needs to be captured as a Technical User Story. This course will teach you how to discover when a Technical User Story is needed and then how to quickly conceptualize and write an effective and correct Technical User Story.

What about Spikes? Most people do seem to know that a Spike is for research activity. But how can you be positively certain that a given work item is a research activity and NOT a technical task and hence needs to be captured as a Spike? Many times a technical task get's incorrectly documented as a Spike. Therefore you need to know about the nuance between a research activity and a technical task so that you can write a Spike only to document the research activity and not the technical task.

This course is designed to teach you the essence of Technical User stories & Spikes, how to discover & write them and also how to avoid anti-patterns among other things.

In short, this course will help you to master these 2 topics by providing an in-depth review.

Plus, as with all my other courses, there will be lots of real life examples of Technical User Stories and Spikes to help you quickly connect with and learn the course material.

Who this course is for:

  • Product Owners (or Business Analyts') who may NOT be very technical or who are new to their role
  • Scrum Masters
  • Application Developers, Testers & Software Architects
  • Functional Managers in the domain of development, testing and business analysis or Manager of Product Owners

Report abuse