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.