Transcripts
1. Use story mapping - Introduction: e Did you realize how difficult is to visualize the product as a whole one? Working with a typical flood backlog, a user story map is a simple idea. It's about arranging stories into a healthful shape. User story. Ma pins are used by top companies off any industries to visualize goals with activities and agree fast on how to achieve them With a minimum version of the product, this workshop will guide you step by step with a realistic example that you can replicate unfollowed with your own project. If you are a product owner, project manager, scrum master designer or a leader, thesis the tools that you must know and understand. Hi, my name is Ignacio Boss. I lead coached and managed actual projects and scrum teams for customers like MTV Rider eHarmony Supply Special one, which is one of the top agile project management tools and many other since 2005. All over the world. During my career, off intensive learning and practice, I got many certifications, including certified scram professionals from Master Professional problem owner and certified much our leadership, which are very difficult to achieve. Ellsworth, 15 years professor for ultimate apologies, consistent signs I love to teach agile and scrum and I designed a lot off hours of training that I'm bringing a line I prefer to teach with games and activities that can stimulate the rial world. Teaching what I learned in my 20 years of experience allows the students to gain practical and realistic learning that they can apply at work. This class can always be improved. So if you have any topic that you would like to know more, please let me know so I can include it in this class. Only future courses. What are you waiting? Start the scores now E.
2. How to get the most of this course?: Welcome to my Skillshare curves. I'm so excited that you are
here and ready to learn. By taking this course. You've already shown that
you are dedicated to improving your skills and taking your creativity to
the next level. Now, let's take your enthusiasm. Untarnished interaction,
check the project and resources section
for this project, I challenge you to put your
new knowledge in practice. Take what you've learned and
create something amazing. Don't be afraid to experiment
and boost your boundaries. Remember, the only
way to grow is to step outside of
your comfort zone. I encourage you to leave a question in the
discussion section. This is a great opportunity
to connect with other learners on me and
get feedback on your work. Don't hesitate to ask
for help if you need it. We're all here to learn
unshared together. Finally, I will be honored if you could leave a
review for this course. Your feedback is
essential to helping me improve and make future
courses even better. Let me know what you love. What do you find challenging? And any suggestions
you may have. I value your opinion and
appreciate your time. Now, let's get started on this
exciting project together.
3. Persona: This is an example of persona. Personas are fictional
but realistic characters which you can create based upon your research in
order to represent the different user types
that might use your product, application, service, or brand. That persona is an
effective technique for characterizing your
target customer. Alan Cooper advocated the use of personas in his goal-oriented
design process. He defines personas us, a precise definition of our user and what he
wishes to accomplish. In his book, The
inmates are running the asylum persona's,
according to Cooper, our hypothetical prototypes of actual users rather
than real persons. Persona's have grown in
popularity and are utilized by many UX designers
and product teams who will live in user
centered design. While personas are extensively used during the design phase, it is highly
recommended to use them earlier in your product
definition phase because they are a great
approach to discover your hypothesis about
your target customers. Creating personas will have the product team to
understand your users needs, Jobs, Rawls, experiences,
behaviors and goals. You can build
solutions to help them to meet their goals and
covered their needs, considering their
habits and skills, it can help you
to recognize that different people have different
needs and expectations. And it can also help you to identify with the user
you are designing for. Researching, and
user persona can be time-consuming
and exhausting. It requires getting your hands
dirty with empirical data, interviews with
customers and surveys. However, the problem
of investing too much time or creating
personas are having a third-party vendor
to create them for us is that we tend to see
them as untouchable. It is probably a better approach
to create new persona as frequently as a team
brainstorming game with the data we already have with
the purpose of discovering assumptions of new problems
that we may need to resolve. The product team can
treat these problems as hypothesis and validate them or reject them with
quick experiments. There are many
templates that you can use to build a persona profile. I encourage you to use a template to create a
persona for your product and see if that changes your perspective or
gives you new ideas. Please read the
example provided on imagine how a person am
I look for your product.
4. Product Vision: Description and Activity: The new Scrum Guide requires to define a product goal and says, and increment is a concrete
stepping stone doorway, the product goal. There are many techniques
to define the project goal, but one that is very popular and effective is to start
with a product vision. The question is,
where are we going? When we are building a product? We are going to get
into a journey. Where is this road taken us? But we need to understand
that question as a team. We need to be all on the
same page and agree. What is that that we
will be working for? We cannot leave that in place. It's, we sold, make it explicit. So everybody knows it. For Agile teams is usually a good practice to define a
shared vision of the product. The vision is something
that tells you if you are given steps in the
right direction or not. Imagine that you have to
go to the lighthouse. The light is your vision. It guides you to
your destination. It doesn't matter if it's dark
or the path is not clear. For every step you
take, you know, if you are closer or not
DR. Destination and you can always think how to give the next step in the
right direction. Division is the light that
keeps the motivation alive. What we can use to
define the vision with the stakeholders is a
product vision template. The vision is, what is the purpose of
creating your product? Which positive change
Surely it bring about. But first you need to define
what is your target group, which market or market segment. Thus the product address, who are the target
customers and users? And those are
difficult questions. We also need to understand
what are their needs. This is very important to not fall in love with the solution, but to fall in love
with the problem. Some people with a creative
mindset tend to have good ideas to build something and they fall in
love with the idea. But the question is, which problem are
you trying to solve? That somewhere? Really
have that problem? And do they need a solution? Will they pay for a solution? Thinking about the
problem allow us to think of multiple solutions. It will be good to have
a talk with real people. Maybe build a persona profile or an empathy map
about the product. We need to define
what product is it? What makes it stand up? Is it feasible to
develop the product, basically a product that offers solutions for the problems or
needs that were discovered. And regarding business goals, we want to define how is the product going to
benefit the company? What are the business goals? Now we will define
a product that we will work in the
rest of the course. So in our case, we have a target group are
demanding shoes customers, and their problem is that they don't want
popular products, they want unique products
that nobody else has. Our product is a customizable
shoes online shop. The company is a shoemaker. They know how to do this on Diigo light to go on
scale and sell online. The business goal is
to sell worldwide, but not to make a big
investment in the beginning, just in best progressively
as the market grows. For example, our product mission is to build a website that allows customers to customize shoes and by unique
pairs of shoes. If you have an idea or you are working in any kind
of project right now, use the template and take a moment to write the
vision of your product.
5. Elevator pitch: Description and Activity: something we can do. In addition to the vision, is the elevator pidge an elevator pitch? It's a short description of the product that displaying the concept in a way such that a listener can understand it in a short period of time. It can be used to explain the idea to an investor or executed in a company. The name reflects the idea that it should be possible to deliver the summary to someone in the timespan often elevator ride between 30 seconds to two minutes for the elevator peach. We can use the following template for a target customer who has a customer need The product . Name is a market category that has one key benefit. And unlike my competitors, the product has a unique differentiator, So the elevator pitch for a product is for a demanding customer who wants exclusive shoes. Unique use is high quality issues Web shop that allows customers to customize their shoes as they like. Unlike popular shoes, the product alos customers toe own shoes that nobody else has. If you have a known project or if you are working in any project right now, take a moment to ride the elevator pitch for your project,
6. User Story Mapping: User study mapping. This is a flat product backlog, which is a typical product
backlog with a list of all the known items
desired for the product. This is very difficult to
manage, prioritize, and refine. It is a big bag of
epics, stories and task. What is very difficult to visualize the big
picture of the product, identify what is missing, what can be seen,
blur or smaller. Only the product owner
knows what is inside. If you've worked with one, you may know how tedious it is. Release planning with a flat
backlog is not easy either. You cannot see which
started, she'll go together. User Story Map is a simple idea. It's about arranging
user stories into helpful shape like this. Where you see users under goals, activities that they need to
do to achieve those goals. User stories for
each activity and releases with user stories
that should go together. Building a User Story Map help us to focus on the big picture, the product as a whole, the sequence of the activities.
7. User Story Mapping - Session and Tools: For a session to create or update a user story mapping, we will prefer to set their worship with people that can work stand in, in more meant actively and together, the participants of the session must be a multi-disciplinary and small group with stakeholders, users, customers, product owners, designers and developers. We want to encourage business people and developers to work together. We want face to face communication into value more individuals and interactions over processes and tools. It is also important to designate a facilitator that could be the scrum master. The tools for a user story map in session be as simple as possible. The tools that we need are a room with walls or flip charts, especially a lot of sticky notes and markers, but not with a fine point. The sticky notes should be simple and easy to read from anywhere. We want short and symbol words that describe actions. We don't want sticky notes that looked like a document and hard to read. Use markers with a chisel tip instead of fine tip will help to fill the space of a sticky note fast and avoid a lot of writing if you need more detail, split the stories and write more smaller stories. However, meeting is not always possible. We need to collaborate remote, or just want to keep a digital copy to improve and maintain. This is just a sample of some popular tools that you can use for user story mappings. I personally prefer tools that are designed specifically for user study mapping during the workshop, you can use any of these tools, registering with a free trial to create your map, complete the steps of the workshop and assignment. Just remember that tools can change at anytime. The important is to master the technique and encouraged collaboration between individuals.
8. Workshop Part 1: Create a Flat Product Backlog: when facilitating a user starting up in session. It is good to start with a brainstorming after that is good to let all the attendees write stories for the product and put them in a wall. Always one story or concept for sticky note. Do not ride multiple items in one sticky note. This activity will give us a wall with a flat back look. So please, based on our vision, write stories in sticky notes off. What do you think these products shall be able to do and put them in a wall? If you can't do that, just use a document in your computer. I'll give you some examples. For instance, Search product. We want simple actions that are easy to read from anywhere. We don't want a document in a sticky note. Those ideas or details can be captured in smaller stories. Not is that we are not using the classic Yusor story template here. We are not getting into that detail yet. We can do that later. For instance, we can continue with BJU product least view product details at the shopping cart customized product. If we get stuck, we can take a look at some of the user stories and think of related stories. Foreign stands for you provoke details. I can think off Beaupre. Put a reality. Suggest similar products, view user reviews and for such products. I can also think off advanced search products. If you have your own product, you can do this with your vision as well. So please stop the video in continue when you have all these stories for your problem aglow .
9. Workshop Part 2: Create account in StoriesOnBoard: for the workshop on examples. You can just use sticky notes in a wall or the table that it's actually recommended. But if you would like to follow them with the same tool I will use, usually go to stories on board dot com. This website could change and be updated often, but basically what you have to do is very simple. Just go to try it. Free un. Create an account.
10. Workshop Part 3: Start User Story Mapping: Now that we have some sticky notes written by the stakeholders, we can ask them to put them on the board. We can also ask them to group studies that are related into one activity. We can start by creating some empty cards in the top, like this and start in R. Then the cards right below the cards title. Suppose that the stakeholders came up with all the stories. You can compare them to your board. In stories on board, maybe you have many more studies done here. And that's great. Maybe you came at a very low level, details of stories, or maybe you work at a higher level, what things are possible? Now we want the stakeholders to work on grouping stories that I related into activities. For instance, the stories in the first columns are related to search, so we can group them in a search activity. The second column is mainly related to view in a product so we can create an activity for bu product. The third column is actually a mix of user shipment, payment. So maybe we can create three activities. One for user sign-in and sign up, another one for shipment. And I think payment is an activity itself. The fourth column can also be divided into two activities. One gallery for post-sale activities, maybe like four, return product and cancel the order. And another one for maintaining the product catalog. Maintain products and add a new product to the catalog. As soon as we create activities, we shall order them in the sequence that they should occur from left to right. So now we can read the activities from left to right to see if this makes sense, what we need is to tell the user journey as a story that anyone can understand. So a user will search for a product. Then we'll view their product. He will identify as the user, then make a payment, decide the shipment method, and if there is any problem, he will contact both sale and someone will take care of the product catalog. Did you like it? So I think that was horrible. First, we are mixing two types of users, the customer and someone that is maintaining the products. On the other side, the story has many holes and that is exactly what we need to find. Let's start by improving a little the world in the activities instead of user1, maybe I would like to call it identify user. Instead of payment, I would like to call it payment method and instead of shipment, I would like to call it Shipman method regarding the sequence of the activities. So it looks like they use search. You'll see the search results before BU in a product. So you search results and sort results should be part of a new activity called Bu search results. I think the payment method should go after selecting the Shipman method. The Checkout is missing and customize the product seems to be very important to not be an activity. And what do we mean with customized product is customize the size, the color, the laces, the shape. See their product in 3D. What is customize the product? Now we need to group these activities into goals for certain users. We have two different goals for two different users here. The customer wants to buy shoes and the administrator wants to maintain the webshop. We can also add more details to the card or Checkout. User studies like remove, item, change quantity, C, subtotal and total apply coupons. And whatever you can think of. So far, we started from this flat Product Backlog and now we have this partial user story map in wisdom need to work on it. As you can see, we have applied a bottom-up approach. We started with many details of stories and we group them into activities, goals, end users. Some people prefer a top-down approach. You can apply the divide and conquer technique in top-down. You can start with users, their goals, identify activities for such goals, validate the user journey. And lastly, create stories for each activity, you decide which approach works better for you. In my opinion, one can start with any approach, but we need to alternate between bored while creating them up. For instance, when we detected that customize the product was an activity, we apply the top-down approach to create some potential stories for it. Please go ahead and update your user story mapping with these techniques.
11. Workshop Part 4: Adding Personas to the User Story Map: Studies on board, let's you define persona profiles. If we go here we can see a deet and create personas that represent user archetypes. Personas can be created during division to identify potential needs. In that case, you can review them before starting the user story mapping session. Many times, you might need to start a User Story Mapping without having personas defined. Some facilitators like to spend some minutes defining some user profiles. The good news is that when working with User Story Mapping, many users that you have not thought about will emerge on be discovered. I personally like to start with no boundaries to let imagination flow on include persona's after collecting the first set of cards. So you can try different approaches and decide what works best for you on your context. In this case, I'm including personas now so you can see the change and how they help to clarify the goals, unhidden details of the cards. Let's take a look at the personas that are defined here. Andrew is an administrator of the site. Basically, he needs to update the contents of the website, generate traffic, and monitor KPIs. So from here, we can see that we are not covering all his needs. We can add more goals, activities on stories. For now, let's just add him to the maintain webshop goal. Rafael is the shoemaker. Once an order is placed, he needs to receive the information to assemble the shoes. Stock is a problem for him. So maybe we should consider the stock when customers are ordering or trigger some requests to order supplies according to the demand. For now, we will keep it simple and just create a goal called assemble shoe with an activity called receive orders. Martin is a dispatcher. He's the guy that takes the assembles shoe, annexed the shipment. For now, let's just create a goal call Meg shipment and assigned him to it. Jane is a customer that loves buying shoes, but with good deals. So we see that we can add store these so she can receive offers on deals through the site notifications or other way. Let's create a new persona. He is David. He will prefer elegant shoes from a company like us. Looking at the reviews is amassed for him. He hates register as a user, although with Google account is acceptable. He wants to know when he we received the order before buying and he go like real-time tracking of the shipment. Let's ask Jane and David to devise shoe goal. For the upcoming lessons, we will only focus on the customers who are the most important users I'm up at that covers all the persona's with older goals can be really big. So it is recommendable to start only with the critical goals for the most important persona's and the find arrest, us. Epics assumed that the rest of the goals are low priority and you can investigate them in the future. If you would like. You can create a new persona to see how it influenced you in the next steps, please take your time to add more cards according to their needs and goals.
12. How's it going? Any questions?: Hey, I would like to take a small break with an imaginary tea or coffee with you to say thank you. Thank you for taking this class. If you're here, it means that you are doing a really good progress so far. So congratulations for that. Do you have any questions so far? Please let me know in the questions or this cash on Sexual. If you like the car so far, please lever of you. I hope you continue enjoying the cars.
13. Workshop Part 5: Add Cards for Personas' needs: Now that we are considering personas to refine our board, let's think off new cards considered in their needs and what we see in the board to narrow the scope. We will only focus on the customers on the by experience. This is not the time to limit creativity. It is not allowed to say that is too complicated or that is not possible. Any card is welcome. We will refine and filter out later for every item in the board. Just asked. Just ask yourself how this can be simpler. What? It's not visible in the board and just create a new car. David is interested in reviews so we can add the sea product review. Score food, thereby score. User speak chairs you, sir. Videos search by score. This could actually be an activity that uses my perform. So we cannot reviews us an activity. David. Good light to signing with Google. So why not signing with Facebook, too? We can also are the calculate expected delivery date, real time shipment tracking map. Actually, that can be part of a new goal called follow up order that includes council order and return product. Let's add the customers to these new goal to for Jane. We could add search by deals, highlight products that are on sale. Show strength through prices. US offers UN Received news about promotions. Let's validate how we can tell the story from the activities. In order to buy issue, David will search for a product beauty search results, select one product, see the reviews, customized the product added to the cart and check out He will identify us a user so like a sheep method and pay. After that, he will follow the order with boasts a activities, and finally, he will receive the product. It's a bit better. I think the world shoe will make more sense instead of the generic world product. And so I think someone like David would like to write a review when receiving the product.
14. MoSCoW Prioritization: The Moscow method is prioritization technique used in project management to reach a common understanding
with stakeholders on the importance they place on the delivery of
each requirement. The term Moscow isn't a cranium derived from their
first letter of each of four prioritization
categories must have requirements that
are critical to the upcoming
increments or timebox, their success or failure
of the product in the short term may depend
on including or not. These features should have requirements that are important, but they are not
critical right now, while she'll have
requirements can be as important as math hub. They can wait a little more, or there may be another way or a shorter version
to satisfy them. Cooled have requirements
that they are decidable and cooling
improve the user experience, but they are not
really necessary. They will typically be included if time and resources permit, they are nice to have, but they use theirs, can live without them, want, have requirements that have been agreed to by stakeholders
as the least critical or not appropriate at this time for the upcoming
increments of the product. 1.5 requirements are typically not considered for
release planning. However, they can
be erected on C, they're in a later
time box or just dropped as they may
be out of scope. A typical product backlog
is an ordered list of everything that is known to
be needed in the product. Product owner can divide the product backlog
into four categories. Moshav, she'll Hub, cool hub, and won't have discussed with the stakeholders which
items are critical, which items are important
but can't wait. Which items are in ice
to hub and which items can be postponed and will
not be considered for now. Now the product owner can focus their refinement on the items
in the Mastaba category, get more details,
discuss the value, apply more specific prioritization
techniques on them. Estimate their value or ask the developers to
estimate the airport. The product owner will probably try to deliver these items first and not spend time discussing items of
the other categories. Periodically, she will evaluate which items of the other
categories may become a mosque Hub whenever there are new product backlog items or
user stories such as ideas, changes, or new requirements. She will evaluate
their priorities as one of these categories. If they are amassed. The new requirement we likely
we're verifying the soon. Otherwise, this is
a nice way to say. That's a great idea, but we will not
discuss it for now. We will just keep
this short note here as a reminder
for the future.
15. Workshop Part 6: Prioritize - Must, Should, Later: For the priorities of the stories, you could start by assigning an explicit business value to each card. But many times that is difficult and not easy to agree with user story maps, it is easier to find an implicit value in a more intuitive way when working as a group. Let's order discards by priority. The Moscow method is a prioritisation technique to reach a common understanding with stakeholders on the importance they place on the delivery of each requirement. The term Moscow itself is an acronym derived from the first letter of each of four prioritization categories must have requirements that are critical for success. She will have requirements that are important, but not for the next deliveries. Cool hub requirements that will be nice to have, but they are not critical and want to have which are the requirements that may be out of scope at this time, I will use a simplified variation of the Moscow method by replacing cooled on warned by later. We will divide the board into three sections, mast choose a later. We can create this sections as releases. We can discuss with the stakeholders which items must be done now, which ones should be done soon, and which ones can be left for later. During the session, we let the participants out organized to rearrange the board and they may come up with a solution like the follow N1. Ok.
16. Workshop Part 7: Make cards simpler: Now let's play too. Can we make it simple? And we will focus only
on the Mask section. For instance, what
is canceled order? Someone might say, Well, I imagine an order
management section where you can see
all your orders, the status of each one, and you can cancel. So I ask, can we
make it simpler? Well, we can make just a list of orders with a cancel button. Can we make it simpler than
that? Simpler than that? What about if customers
send an email to cancel? That is simple. Can we make it even simpler? Maybe they just can't
counsel at all. Okay. Which of these are unmasked? Which ones are and
which ones are a later. Well, NO cancel and
cancel with email. Unmasked. Symbol list could be cooled
and the rest are for later. What about shopping cart? Can that be simpler? Well, maybe you don't
have a shopping cart. They only came by one product. We can start with that and
other shopping cart later. What about payment? Well, you can pay with credit
card, debit guard, PayPal. You can pay when you
receive the product. You can pay on store, you can pay with cash when
you pick up at the store. But I think for now, paying with credit
card will be enough. What about search products? Can that be simpler? Know, it cannot be
simpler than that. You have to search
for the product. What if we started
with just a list of the 20 best products? Can be simpler than that. Maybe we can start
with one product for men and one for
the, for women. The key feature is
to customize so we can just select our best
product for each of them. What is customized scholar? Well, you have animal prints. We can do the basic
colors, black, white, red, blue, yellow ring. You have a color
gradients and you can combine up to four colors. What about the register
user and signing? Well, people must
register, right? Can we do it simpler than that? What if they don't
register and we just take their shipment details? What about ride review? Well, they can write the title. Some comments and stars from one-to-five can be
simpler than that. Well, maybe just say how much did you like it
from one-to-five. What about BYU in
their shoes reviews? We can just display
the average score. What about shipments? Well, I was thinking
she meant by post, Shipman, by DHL
and local library. But I think for now we can just go with shipment bypassed. And we can continue
slides in the cards into smaller and more
detailed user stories while moving the less
important user stories to the shield and later
sections, this is cell. So a good time to apply the spider technique that we reviewed in the
user story lessons.
17. Workshop Part 8: MVP and releases: When you are building a product, you can imagine
that you can have a super complete product, which usually is a waste
and takes a lot of time. You could have a product
with a minimum features, but that is a raw products that nobody wants to use or need. Or you could have
a viable product, which are the features
that you really want. Now, a minimum viable product
is somewhere in the middle. Is a product developed with sufficient features to
satisfy early adopters, start the business
and learn from it. The next set of features
is designed after considering the feedback from the initial users
of the product, sometimes stakeholders
feel that they need to define everything before
starting the project, but we need to teach
them that we can modify and improve the
product all the time. The truth is that
stakeholders want a product that they can be proud of
and that is understandable, but that will take months
and there is no guarantee. So the idea is to start
with small experiments of low-risk and learn
with this technique. They understand that
they can start with a tiny version for certain
users and learn from them, or just start a small
part of the business, setting small business
goals to get some revenue. We will think of our MVP by creating a release called MVP. And MVP or any release
must have a goal. So the goal of the stakeholders
for this release or MVP, is to start selling for one type of user and
learn from them. So the question is, from the mast section, what is the minimum set of
cards that we shall include in the MVP that we can sell is
useful for one type of user. And we can learn,
we can start by selling one type
of shoe for women. We don't need search results
or view product details. We can just go directly
to customize shoes. From customize shoe, we can
include the size uncombined, up to four colors that will
make it unique enough. Weekend skip reviews,
just collect the name, e-mail and Shipment
Details, shipment, my boss, pay with credit card and
considered in a user like Jane, it could be good to show a special limited price
for opening the shop. Let's validate the
MBB by telling a study just from the MVP cards, Jane chooses to buy
a woman's shoe. She feels excited because it's on a special limited price. She customize it by selecting the size and combining colors. She confirms the
order by providing her details to receive
the sheep by my past. Finally, shape-based with
credit card, the next release, it could be good to hear the thoughts and
feedback from the users, but we can make a draft
or how it could look. We will think of every
new release with the same mindset that
we applied for the MVP. Furthermore, we should say that every release
isn't new MVP, but with a new small
business goal. For the next business goal, we want to sell one
type of shoes for men. So maybe we can add one Manchu, show the average score and a low rating from one
to 51. Making a review. Customer like David, good, like to know the delivery date and track the shipment
in real-time. Those cards require
a lot of efforts, but we could just simply display that the
delivery time is between three days and just send him the tracking
code by email. Let's validate their release
two by telling a story. David chooses to buy a
man's pair of shoes. He takes a look at
the review score, customize the shoes by selecting the size and combining colors. He checks the delivery
time and configure the order by providing his details to
receive the shipment, my post, and he pays with credit card to
follow the shipment. Who receives the tracking code when he received
the pair of shoes, he will write the product. Do not plan. Many realists this,
they are just draft and never let customers think
that this is a contract. It does not make
sense to think of many releases as the
future is uncertain. One release is not
equal to one sprint. A release is a business
goal composed by many cards and it can take less than one
sprints to complete. Several sprints to be completed. There is no rule. But if your releases
take too many sprints, you might need to
learn to think of smaller business goals and
hop shorter feedback loops. Think of smaller
business increments that you can measure
their impact. To maintain the user story
map in the long term, when you add a new story
or card to your mob, evaluate if it should
go in Moscow shoe or later sections only if
you add it to mask, then apply the technique
to make it simpler. Please complete your
board to create an MVP on a second release, if you have a project, you can repeat the workshop, applying all these steps and
activities to your project. When you finish your
user story map, please share it by
taking a screenshot. Or you can use the
share option to make it public or create a private
link and share the URL. I will also share the
final version with you. Hope you'll find this
workshop useful for your job or potential
projects if you like it, please follow me to
receive updates on. Please write a review so you
can recommend to others.
18. Final Thoughts: My main goal is to help you with new knowledge that you can apply at work un become a successful, unprofessional leader. If you have any questions or if you think that something was Mason, please let me know so I can guide you in the right direction or include the topic in this cars or future curses. I hope that you enjoy this curse on. You can recommend it to others. If you like this course, place some forgets to lever of you. You will help me to spread my word. Support me to bring more courses. You will have other people to take the position off Joining this class to thank you.
Ignacio Paz, Agile Coach and trainer, Professor
