Transcripts
1. Course Introduction: Welcome to the best
course online, which will help you learn how to write great user stories. I am phi, so I've
created this course to share the experience I have
gained in my career with you. I've been an entrepreneur and a product manager for
the last ten years. I have built softwares
that have been used by millions of
people around the globe. Why should you learn
about user stories? If you're building a product, whether it's
physical or digital, then your products need to
prove themselves useful by solving a particular
problem for the target users. If a product is solving
problems for its users, able to add value and make
users use them even more. This would eventually
lead to your product making profits and
emerging successful. Hence, understanding the
problem is very important since every product should
solve the problem for its users to prove
itself valuable. This is where user
stories commit. User stories are part of an agile approach that helps
teams focus on users and help them understand the
problems that users are facing so that they can
build the right problems. Why should you take this course? This course is designed
keeping beginners in mind. We have made sure that
each and every concept is clearly explained in an
easy to understand manner. So if you are a
beginner, don't worry, I am 100% committed
to help you succeed. So what are you waiting for? Let's take the first step and I will see you and
inside the class.
2. Products and Problems: Hello guys, welcome back. So in this lecture
we are going to talk about products
and problems. And by the end of
this lecture you are going to have a
complete daddy. All. What is a product? What are the problems around
us that we usually face and how everyday products
help us solve them. We're also going to discuss how different products have
different goals, right? And by the end of this lecture, you are going to have a complete clarity
of these concepts. So let's get started. So what is a product? A
product is anything that satisfies or fulfills
the need of the market. Every product you see
around you or you use, has a goal and tries to
solve a particular problem. For example, if I
have to give you an example of a
food ordering app, the goal of this
app is to make it easy for its users
to order food, explore food, and understand what all foods they can order and get
delivered around them. But what is the problem then
this app is trying to solve? So essentially, if this
app does not exist, uses does not have an
easy way to order food. Yes, there might be ways to order directly from restaurants, but those are not as easy as ordering
directly from the app. You have to look up
for restaurants, phone number, call them up, and then place your order. Having a food
ordering app right on your phone would be the
most easy v and takes away all the hassles and density problem that this
product is aiming to solve. Now, the product you are using, like the food ordering
app in our case, is owned by a business, right? So there's a business
behind this particular app, which is running
this particular app. And the goal of the business yo, is to make profits by solving the right
problem for its user. It's very important for business and solve the
problem in a right way, because that's all we'll make
the business successful. If problems are
solved correctly, users will love to
use the product because the product that's buried is solving
problem for them. And saving that i. And if users use the product, businesses would eventually
mix profit and be successful. So this is about businesses that exist behind the
products, right? And this is about
their goals and how they strive to
meet their goals. So there are lots of
products that you would notice around you and
which you use every day. And you will also observe
that these products solve a particular problem for you
and have a bowl with them. So here are the products that
you use in your daily life. Whatsapp, for
example, it's solved communication for you. Oboe. It solves short distance
traveled for you. Then you have Shopify. So if you are a
small business who is looking to get online, Shopify can help you set up
your online store quickly. And it can do it with very less hazards and then
you have more products. I would request you all to
keep looking for more products around you and absorbed the
problem that they're solving. So let's summarize. This
lecture will be understood. What is a product? What are the problems
that uses fees and how products around
us addresses them? We also understood how different products
have different goals. And we understood
this with the help of an example like the
full ordering app, which had a goal who
make food or drink easy. And this is essentially
the problem which uses fees and all of the
product is to solve it. I hope you guys
enjoyed this class and foundries glass valuable, I shall see you soon. Thank you.
3. What are user stories: Hello guys, welcome back. So in this lecture
we are going to talk about what our users stories. And by the end of this lecture, you're going to have a complete clarity on
what our user stories, how can you write them? And we are willing to understand this with the help
of an example. So let's get started. So we know that what
our product is, and in order to be successful, products need to
prove themselves useful by solving a
particular problem. If a product is solving
problems for its use of, it would add value and
make users use them, which would eventually
lead businesses making and emerging
as successful. So this is about product and we know like they have goals and they have a
problem to solve. Now what our user stories. User stories are short, simple descriptions of
a feature pole from the perspective of the person who designs the new capability. This person is usually a user or a customer who is
going to use the system. So user story identifies
who is the user, what he needs and
why does he need. And it is written
in this format. So your, if you see, we are talking about
who is the user. We are also talking
about what he needs. And we also talking
about why he needs. So we are saying as a role, I want some action so that
these are the benefits. So we are talking about who, what, and why, essentially. So this is nothing but the format in which user
stories are written. For example, if you're building an app that helps you
book movie ticket online and you
want your users to see the list of all
the upcoming releases. You can define a user story
for this requirement as, as a busy movie level, I want to have the list of
all the movies releasing on my smartphone so that I can
watch them whenever I want. So this is an example
of a user story. And you would notice
that we have a user. So he's a busy movie level
and dispose regular describes our user base or
the target audience for this particular feature
that we are building. Well then we have the action. So I want to have a list of all the movies releasing
on my smartphone. So this is the what part. So we had Wu part, then we have the board part, and now we have the benefit, which is the y part, so that I can watch
them whenever I want. Alright? So you can notice
the above example of user story reflect on the old
problem that is to be sold. Why does supposed to be sold? Alright? And it also reflects
on who is your user. And you will also
notice that this particular uses 2D is
written in the user's voice. So it is like users docking and asking you this
particular feature. Now, there are few
things that you're supposed to know
about user stories. So the number one thing is, user stories are an
important part of your user research and are
part of a GI approach. And this helps shift focus from writing about the requirements
to talking about them. So user stories form an
important part of user research. And the helper beam
shift focus from writing about the requirements to start talking about them. So user stories are also the smallest unit of work
in the GI framework. And it isn't a form of goal, and it is not in the
form of feature. So this is something that
you're supposed to remember. Then user stories helps the team understand the problem from
the user's perspective. Since they are written
in the form of goals, it keeps users in the
center and enables the team to understand and
think what the Oberlin, why they are building
and what value would it add to the
user or the customer. So essentially uses stories, help beams understand users, my keeping users and
descender of the problem. So that's about user stories, guys, let's summarize
this lecture. In this lecture
we'll be understood what our user stories. We also understood how do
we write user stories. And we also took a look
at one of the examples. Then we understood
the different things that you should know
about user stories. So I hope you guys enjoyed this class and found
this class valuable. I shall see you guys soon. Thank you.
4. How to write great user stories: Hello guys, welcome back. So in this lecture we
are going to talk about how can you write
great user stories. By the end of this lecture, you are going to have
a complete gladly on the steps involved in
writing great user stories. And we also going to talk
about the invest criteria. It's like a framework and it is been put forth by Bill Wake. So there is a person called
Bill Wake who has designed this criteria which would help you write best user stories. So we're going to
understand this with the help of examples in
this particular lecture. So let's get started. So before writing
great user stories, you're supposed to ask
yourself three questions. So you're supposed to
ask, Who is it for? What does it expects
from the system? Why is it important? And you also need to remember the format that we discussed. So we discussed as a role, I want a particular action so
that I get these benefits. And if you ask these questions and form a user story in
this particular format, automatically, you will have the best uses DO RE out there. Alright, so you should ask, Who's it for, which is
nothing but the earlier. Then you should ask, what does
it expect from the system, which would be the action of 30? And then you should ask, why is it important, which would be the benefits over your greed user stories follow the invest criteria by Bill Wake and in West
stands for independent, negotiable, valuable,
estimatable, small, and testable. So this is the full form
of this word in West. Let us now understand
what each one means. So the first one, independent. So independent means that this user story can
be developed in any sequence and changes to one uses 2D does
not impact others. So this is what
independent means. Then we have negotiable, which means that it
is up for the team to decide on how to implement
these user stories. There is no rigidly fixed flow. So this is the negotiable part. Then we have valuable, which means that each user story delivers or detached unit
of value to the end-user. And this is something
relatable to the number 1,
independent, alright? So it has to be valuable
as well as independent. The next point says estimable. And it means that it
should be quite easy to guess how much time that development of the
user story will take. The next point is small. So small means it should go
through the whole cycle, like designing, coding, testing, et cetera, in one sprint. So this entire cycle, it should complete the entire
cycle in one single sprint. And this is what small means. Then we have testable, which means that be clear
acceptance criteria, book check whether
the user story is implemented
appropriately, right? So this is nothing but the
invest criteria by Bill Wake. So you can see Einstein
for independent, negotiable, valuable,
estimatable, small, and testable. And it forms invest, right, for this is nothing but
the criteria that you can use to make sure that the users stories you write
are good user stories. Now, this is an example
of a user story. Like as a student, I wanted to purchase
or paperless pass so that I can
drive to the school. Now this is a story. It clearly mentions that, oh, this user story is 4. And in this example, it is for students, which is what defines the target audience
for your product. And then we have actions that says that
students should be able to book paperless tickets in the digital format, right? And that is nothing
but the action here. And it also tells the
benefit which sees that the students should be
able to drive to the school. Okay, So we have what, why, and who defined clearly
a wheel, right? And if you also take a look at this particular user story, it follows the invest
criteria, will you? Right? And you can see it's clearly being
independent, negotiable, valuable, estimatable, small,
and it's also testable. So there's an example uses
2D that meets this criteria. So let's summarize. So in this lecture we understood how you can write
great user stories. We spoke about the invest
criteria by Bill week and we understood this criteria with the help of an example. So I hope you guys enjoyed this class and found
this class valuable. I shall see why soon. Thank you.
5. Benefits of user stories1: Hello guys, welcome back. So in this lecture
we are going to talk about the benefits
of user stories. And by the end of this lecture, you are going to have a
complete clarity on what are the different benefits that user two stories bring onto the team. So let's get started. So let's talk about every
benefit one by one. So the pause benefit is it
gives a sense of achievement. So since stories
defined the end goal, and once the product launched, it gives a sense of achievement
to the entire team. Now, when the traditional
product development process, product teams might spend months working on a
single feature, doors, significant amount
of work without delivering any thing
valuable to the users. However, a giant development
turns this approach upside down and breaks down the user
needs into user stories, which emphasizes on
these small feature which add value to
the users like. So. This is how user stories give a sense of achievement
to the team. The next benefit would be helps team focused on the users. So since uses stories define
the goal that the user is supposed to achieve
or with the help of the product in user's voice. It helps teams keep
focus on its users. As the team defines
who, what, and why. For the feature which
they want to ship, there will be compelled to
talk and connect to the users. And this might lead that they might want to understand
the user's perspective, how to solve the problem today and what are the pain
points, et cetera. So you just story brings all of this and keeps the user at the center and helps the
team focus on users. The next benefit would be
it enables collaboration. So since user stories
are written in user's voice that are easily
understandable by the team. They don't have to depend on documentation and guidance
on what needs to be done to solve a particular uses two themes within themselves and collaborate and
willing themselves, they can figure out
the best way to execute a particular user story. So this is another benefit around collaboration
of user stories. The next benefit would
be iterative building. So user stories help with the iterative and incremental improvements to the products. So with every release, you can make sure that you ship user stories that add value. This can enable you to improve the product in an
iterative way and make sure that you are taking use of feedback after
shipping every user. So this approach can
help the product leaders have the culture of
experimentation within a team, ships or product in
incremental way, measures feedback to learn and then rehydrate
over the feedback. With each iteration,
the lawns mowed about the USO and shapes the product in
the red direction. So these are the Pope
benefits of user stories and how user stories helps team build the right
product for its users. So I hope you guys enjoyed this class and found
this class valuable. I shall see you guys soon. Thank you.
6. Epics and User Stories: Hello guys, welcome back. In this lecture we
are going to talk about ethics and user stories. And by the end of this lecture, you are going to have
a complete clarity on what are ethics. We are going to
understand epochs with the help of examples. And you will also have a PO, understanding of how epics
default from user stories. So let's get started. So whatnot it begs. An epic, is a big
chunk of work that can be broken down
into smaller pieces. It is basically a
high-level description of what users want to
achieve with the product. Epochs help teams organize, walk, and create and hierarchy. Teams breakdown, walk and continue walking towards
a particular goal. For example, if we are building an e-commerce app and epic
gamete as a customer, I wanted to have wishlist. So this is nothing but
an example of an epic. And you can see this. You can observe that this
is a very high level, like it's not in the
user story format. Now, epochs can be
broken down into smaller chunks of work
which bean can pick it up. And epics are always broken
down into user stories. And these uses booties on
nothing but smaller chunks of work with which
beams can pick it up. These smaller chunks
are communicated to the team in the
form of user stories. Since uses foodies
helps the team visualize the requirement
from the user perspective. So if we're coming
back to the example, oldest wishlist, you can see that this is the epic
that we have, are right? And weekend. This is already high level view that we have. It's
very high-level. It's not in the
form of user story. And now you want to give
this as a task to your team. So you will have to break
this down into user stories. So you would have something
like this. So uses 31. As a customer. I wanted to be able to see if
products into my business. As a product, I want to be able to purchase products
from my wishlist. As a customer, I wanted to be able to beat product
from my wish. Alright, two or
three user stories. And epic is divided on, broken down into three
smaller user stories. And as you can see, bigger chunk of work
is broken down into smaller chunks in the
form of user stories. When you are doing
this breakdown, you should make sure
that it uses two is not dependent on each
other for execution. They have to be small
and quick to execute. Usually, piece of work
that you're doing, things really big,
several weeks to deliver can be termed as epic. And it needs to be broken down. And this task is broken
down to a level where your team thinks it can be executed in less
than a week's time. This is all about epoch. Now let's talk about
some of the things that you're supposed to keep
in mind about ethics. Ethics are for stakeholders, users and customers, uses
booties, our folder team. Alright, so this is one
important point about epic. Epic, large user stories that cannot be completed
in a single sprint. Hence, it picks up, broken down into user stories that can be completed
in a single sprint. If you want to recording
your team's progress, you may talk in terms of epochs. And if you're talking
to a developer, you will talk in bones of users. Louise doesn't won't be things that you're supposed
to give in mind about epochs. Let's summarize in this lecture, we understood what our epics, and we also discussed how the
default from user stories. And we understood
this with the help of an example when we actually took a wishlist example
and we made an a big, and we've broken it down
into themes, this duties. And then we understood
what are the things that you're supposed to keep
in mind about ethics? I hope you guys
enjoyed this class and found slots available. I shall see you guys
soon. Thank you.
7. Organising user stories with the help of Story mapping: Hello guys, welcome back. In this lecture we are going
to talk about how can you organize user studies with
the help of story mapping. By the end of this lecture, you are going to have
a complete clarity on what is floating
mapping and what are the different steps involved
in doing spotting mapping? Then we're going to take an
example and we're going to actually do the mapping by
organizing uses two weeks. So let's get started. What is story mapping? So
let's putting mapping is nothing but a way
to organize uses, foodies based on walkthroughs
of users and have them aligned towards
the end goal that uses wanted to achieve. Splitting mapping is
an activity that has done with the help
of entire team, including designers, developers, stakeholders
in a meeting. Soledad, everyone is
on the same beach. Phosphonium mapping. All you need is the entire team, some sticky notes, mockers, and a plain wall to stick nodes store the mapping is done in
five steps, as you can see. So the first step is to
discover your project code. Then the next step is
to map the journey. Then you have to come
up with the solutions. Then we organize tasks
according to the priority. The next step would be to
slice out a release structure. Let's take an example to
understand this better. Now suppose you're
building a product using which users will be able to
buy healthy products online. How are you going to go
through all these five steps? So let's understand
that the first step would be discovering
your project goal. So this is an example like
suppose you're building a product using which users will be able to buy healthy
products online. The first step is discover
your project goal. The project goal is users
should be able to find the products and choose a product and also
make apologies. So these are
different goals that users want to achieve to transact successfully on the black foam that
you are creating. The number one goal would
be finally, products. You should be able to look
up to healthy products. Then you need to choose a product and then
make approaches. To step number one, we have
discovered our project goal for this particular project of building online health tool. Now, let's talk about
the second step. The second step would
be Samantha Jony. So after you have
your goals handy, you can now map the
journey of the user on the steps that he needs to
achieve his or her goals. These were the goals
that were discussed. Now, what would be the Joanie? Joanie for finding
healthy products would be the users should be
able to visit main page, then search on the main
page, then apply filters. Then I have a few uses, 300, wherein as a user, that user should be
such hilly products. Then as a user, I should be able to filter products
on the switch beach. Then as a user, I should
be Mach 11 products to me. And as a user, I should be able
to add products to the wishlist so that you
can purchase it later. And then as a user, I should be able to
save my search as well. So finding products,
this is the Joanie, typically a user would have. Now let's talk about
choosing a product. Once you have searched for the products and you
have found products, the next step would be to choose a product and choosing
a product morning more, reading the product, it is
comparing two products. So the users vote. It would be as a user, I should be able to read the product description
and benefits. Then I should be able to
compare two products. Then I should be able to see the best offers on the product. And then I should be able to
read reviews on the product. This will help me
choose my product. And if these steps
are taken care of, I meet my goal of
choosing a product. Now the next goal that we
have is makeup approaches, and this is what the
DNA would look like. So you will have to provide the shipping information,
delivery date, micro-payment. So if you convert this story, it would be, I should be able to enter my
shipping address. I should be able to see my shipping address
for future checkouts. And I should be able to make an online payment
using the credit card. This is nothing but the goal and the
journey mapping that we have done for this
particular product that we're building over here. Now, the next step after
mapping the journey would be to come up with
solutions for this journey. Now, what are we going
to do is these were the goals and every
journey that we defined. So for example, visit
the main beach. As I use up, I
should be able to. Visit a basic main page. I should be able to use
the main page on mobile. And then I should be able to see the promotions
on the main beach. Then for searching, I should be able to search for
healthy products. I should be able to mark
products, irrelevant to me. I should be able to add products to wishlist so that I
can purchase it later. I should be able to
also save my search. Then you also have a Blackberry, those wherein you
should be able to apply for those on
the search page. This is faulty finding part. Then you have for
choosing part wherein you can read the product medius
and under product names, you should be able to read product description in benefits. You should be able to see the best office and read
the reviews on the product. Then you should be able
to compare two products. I shouldn't be able to
see which product is the best and put them
into comparison card. Then I don't want
to making proteins. I should be able to provide
my shipping address and I should be able to see my shipping address
for future checkouts. Later on, I should be able to choose a delivery date as well. And making payments. I shouldn't be able to
make online payment using my credit card and
I should be able to make payment using PayPal. But what do we have done is for every journey that we created, it did the corresponding
user studies and we have categorized
and over you. Alright, so in reading
the productive data's, you have few points
that you need to take care of for
making payments. You also need to make sure
you have credit card as well as the people information setup. So this is about coming
up with the solution. Now the next part would be to organize tasks according
to the priority. So we have these three goods, novel, fine, healthy products. I have prioritise the
task in this order. I have this is the
number one priority. This is the next level priority and this is the lowest priority. The number one priority is
it was it a basic main page? This is beta minimum that I
need to have for my product. Then I should be able to
search for healthy products. This is also bare minimum, like if you're building
an e-commerce store. So it is the basic
functionality, then you should be able to
add filters on the beach. And this is also like
version 1, phi2. Then you should be able to see promotions on the main beach. This is we improve
conversions on the beach. Then you have the next Friday, I don't wet in wishlist. And you have the
mobile-based optimization in a little lower priority. Mobile-based optimization
I think you can do in at a lower priority. That is why we have
taken it down. As a user, I should be
able to save my search. So savings and mocking
product 11 to me, I have kept it only
Lewis priority. This would be the outcome. This would be a team effort. So as of now, I have
done this according to myself and I am presenting
to you on how you can do it. But eventually
when you are doing this activity with the team, it would be a team report in
organizing things this way, like based on the
priority support team decides on what is a
priority for each item. Now for choosing the products, you should be able to read the broad description
and benefits. This is bare minimum. You should also be able
to read customer reviews. Reviews should also
appear prominently. Then as a user, I should be able to
see best offers. So there's something I have taken on a little
bit lower priority and then I have added competitors on even
more lower priority. Then regarding
making approaches, I have added like shipping address as one
of the crucial parts. If you're building a product, shipping address is
very, very important. And you should also be
letting users should be also able to save that
shipping information for future checkouts. And then you have the online
payment information also, if you're launching a store, you should have at least have on anybody who credit card
payment information. And then you have this
PayPal integration as well, which you can add later on. So I've kept that on a
slightly lower priority. Then I will divide it one more feature on even
more lower priority, which is like user
should be able to choose a delivery date that is not important for the post-release, but I have the prioritized. You're going to add that
feature lead among. It's not an unlinked
Omega big the product. So this is how I have
organized my tasks according to the priority for building this
particular feature. Now, moving on to the next part. The next part is slicing out a release structure where you, how would you slice out
or at least structure? So we already discussed goals. We already discussed, this is how we have
prioritized the items. Now, you can categorize
these into releases so you can slice out or at least structure you like
release number one, release number two, and then you have release number three. You can chop out three releases. To release number one
has the bare minimum. You would have items
which are very important for products
like for example, such. You're going to imagine
an online store without having a
search function. Also users should be able
to, if you're adding search, you should be able
to filter products like shipping address
and collecting payments. These are all bare minimum essential P2's that
your production would have in version 1.01
can be called as MVP, or the initial release that is put out there for your users. This is how you can do
release structuring. Now let's summarize.
In this lecture, we understood what a
story mapping and how can you lose 2D mapping of each row that
you are launching. We also understood
the different steps that are involved in
doing Story Mapping. Be alternative. How you
can organize users, students with the head
bolts do the mapping. And in the end of the book, an example of health store. And we understood the entire
concept of story mapping by mapping the end that features and all the use cases
of Health Tool. I hope you guys
enjoyed this class and found this class valuable. I shall see you guys
soon. Thank you.
Faisal Memon, Product | Engineer | Entrepreneur
