User eXperience Design with Scrum – Overcome identified challenges of UX designers | Will Jeffrey | Skillshare

User eXperience Design with Scrum – Overcome identified challenges of UX designers

Will Jeffrey, Professional Agile Trainer

User eXperience Design with Scrum – Overcome identified challenges of UX designers

Will Jeffrey, Professional Agile Trainer

Play Speed
  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x
19 Lessons (51m)
    • 1. Course Overview

      1:23
    • 2. A Challenge for UX

      2:01
    • 3. What is UX Design?

      3:53
    • 4. Agile Rarely Trains on UX...

      3:00
    • 5. What Is a Scrum Team?

      2:23
    • 6. UX Designer Within Scrum Team

      1:47
    • 7. UX Design & Scrum Process

      1:29
    • 8. How to Fit Design Into the Scrum Process?

      3:26
    • 9. Zoom on 3 Practices (Design Sprint, Design Studio & MVP)

      0:33
    • 10. Design Sprints

      2:14
    • 11. > Design Sprint Methodology

      3:50
    • 12. > Design Sprint Week

      5:02
    • 13. > Design Sprint & Scrum

      3:37
    • 14. Design Studio

      3:45
    • 15. MVP (Minimum Viable Product)

      3:35
    • 16. Role of UX Designer in Scrum Team

      1:27
    • 17. Problems Faced by UX Designers

      3:25
    • 18. How to Meet These Challenges

      3:27
    • 19. Conclusion

      0:45
  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels
  • Beg/Int level
  • Int/Adv level

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.

110

Students

--

Projects

About This Class

UPDATE (01/2020): revamped the course based on feedback (audio, video & content)

Integrating UX design within Agile is a real challenge, and several approaches are available:

  • Some of them state that it is better to run a separate design sprint along with development sprint. And this design sprint should go ahead of development sprint.
  • Few are in opinion of running a design sprint parallel with development sprint.
  • Few others are in favor of an integrated sprint where UX designers, developers and testers work together as a scrum team.

This course mainly focuses on the last approach, integrated sprints, that works really well in many aspects.

Shifting from traditional product-development processes like Waterfall to modern Agile frameworks such as Scrum can be a challenge for UX. We must learn a whole new set of nomenclature, adapt to new timeframes in which to complete our research or design work, and step outside of our comfort zones to collaborate with cross-functional partners, many of whom we’ve never worked with before. Once we start making these changes, we quickly realize there’s a lot more to Agile than simply working in time-boxed sprints. Unlike Waterfall, Scrum has many recurring meetings that are typically referred to as ceremonies, including daily standups (also known as daily Scrum), backlog refinement (also known as backlog grooming), sprint planning, demos, and retrospectives. As UX people move to Agile, they may wonder whether they need to attend each ceremony and what they should do to adequately prepare and participate.

“Being part of a scrum team, developers, testers, and UX designers can better contribute to complete their tasks in a sprint, and hence produce a quality product.”

However, there are few challenges a UX designer face while working in an integrated scrum team. This course lists these challenges along with few recommendations that can help to overcome these challenges. What you will learn:

  • How to include UX into Scrum?
  • What is the UX designer role within a Scrum team?
  • How to maintain open communication?
  • How to influence product success?
  • How to productively contribute to the team?

NB: Much of the discussion in this course will focus on the Scrum framework for Agile, but many of the concepts can be applied to other Agile approaches as well.

Learning Paths

Meet Your Teacher

Teacher Profile Image

Will Jeffrey

Professional Agile Trainer

Teacher

 

Will has over 20 years of Software Development experience with his last 15 years in the role as Project Manager, Scrum Master and Agile Coach Master.

He managed or facilitated projects of different scale, project size from dozen man-days to hundred man-years.

He has trained & coached hundreds of professionals, including senior leaders in Fortune 500, startups, and entrepreneurial companies, to accelerate their impact and influence, and grow into their next-level of authentic and inspired leadership.

He now splits his time coaching executives, managers, as well as building up Scrum Masters, Product Owners, and Agile Coaches internally.

 

What Are Will's Core Skills

• Certified Scrum Master (10+ years running Web, Desktop &... See full profile

Class Ratings

Expectations Met?
  • Exceeded!
    0%
  • Yes
    0%
  • Somewhat
    0%
  • Not really
    0%
Reviews Archive

In October 2018, we updated our review system to improve the way we collect feedback. Below are the reviews written before that update.

Your creative journey starts here.

  • Unlimited access to every class
  • Supportive online creative community
  • Learn offline with Skillshare’s app

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.

phone

Transcripts

1. Course Overview: Hi everyone. My name is Will Jeffrey and welcome to my course. I'm an Agile coach, helping teams to get better and doing what they love. Scrum has been the buzz for the past decade and user experienced. Ux wasn't far behind. There is much confusion about UX integration. We no longer desire to have the entire system design completed before the coding starts as waterfall practices have prescribed. However, not all design Canada or should be thought about only during the development spread. Rapidly changing requirements and priorities these projects Welcome, can be detrimental if UX is not incorporated in a timely and correct way. How do we integrate UX with Scrum? You will learn how to maintain open communication, influence product success, and productively contribute to the team. Much of the discussion in this course we'll focus on the Scrum Framework for agile, but many of the concepts can be applied to other Agile approaches as well. We start this course on explaining the different challenges related to UX and Scrum. Then we explore some solutions to fit design into the Scrum process. Lastly, we focus on the UX designer role within a Scrum team. We hope you will enjoy this course. 2. A Challenge for UX: Shifting from traditional product development processes like waterfall, pre-modern Agile frameworks such as scrum, can be a challenge for UX. We must learn a whole new set of nomenclature, adapt to new timeframes in which to complete our research or design work and step outside of our comfort zones to collaborate with cross-functional partners, many of whom we've never worked with before. Once we start making these changes, we quickly realized there's a lot more to agile than simply working in time-boxed sprints. Unlike waterfall, Scrum has many recurring meetings that are typically referred to as events, including daily standups, also known as daily Scrum backlog refinement, also known as backlog grooming, sprint planning, sprint review, where the product is demoed and retrospectives where the team process is reviewed. As UX people moved to agile, they may wonder whether they need to attend each ceremony and what they should do to adequately prepare and participate. Integrating UX design within Agile is a real challenge and several approaches are available. Some of them state that it is better to run a separate design sprint along with development sprint. And this design sprint should go ahead of development sprint. You are in opinion of running a design sprint parallel with development sprint. And a few others are in favor of an integrated sprint where UX designers, developers, and testers work together as a Scrum team. This course mainly focuses on the last approach that works really well in many aspects. Being part of a Scrum team and developers, testers and UX designers can better contribute to complete their tasks in a sprint and hence produce a quality product. However, there are few challenges a UX designer face while working in an integrated Scrum team. Before exploring them, let's define what do we mean by UX design. 3. What is UX Design?: User experience design is the process design teams used to create products that provide meaningful and relevant experiences to users. This involves the design of the entire process of acquiring and integrating the product, including aspects of branding, design, usability, and function. What UX designers do goes beyond user interface design. User experience design is often used interchangeably with terms such as user interface design and usability. However, while usability and user interface design are important aspects of UX design, they are subsets of it. Ux design covers a vast array of other areas. Well, a UX designer is concerned with the entire process of acquiring and integrating a product, including aspects of branding, design, usability, and function is a story that begins before the devices, even in the user's hands. It says Don Norman, the inventor of the term user experience. No product is an island. A product is more than the product. A cohesive, integrated set of experiences. Think through all of the stages of a product or service. From initial intentions for a final reflections, from first usage to help service and maintenance make them all work together seamlessly. Products that provide great user experience. For example, the iPhone are thus designed with not only the products consumption or use in mind, but also the entire process of acquiring, owning, and even troubleshooting it. Similarly, UX designers don't just focus on creating products that are usable. We concentrate on other aspects of the user experience, such as pleasure, efficiency, and fun. To. Consequently, there is no single definition of a good user experience. Instead, a good user experience is one that meets a particular user's needs in the specific context where he or she uses the product. As a UX designer, you should consider the why, what, and how of product use. The Y involves the user's motivations for adopting a product, whether they relate to a task they wish to perform with it, or to values and views which users associate with the ownership and use of the product. But what addresses the things people can do with a product, its functionality. Finally, the how relates to the design of functionality in an accessible and aesthetically pleasant way. Ux designers start with the why before determining the what and then, and finally, the how in order to create products that users can form meaningful experiences with in software designs, you will need to ensure the product substance comes through an existing device and offers a seamless fluid experience. Since UX design encompasses the entire user journey is a multidisciplinary field. Ux designers come from a variety of backgrounds, such as visual design, Programming, Psychology, and interaction design. A UX designers typical tasks vary, but often include user research, creating personas, designing wireframes, and interactive prototypes, as well as testing designs. These tasks can vary greatly from one organization to the next. That they always demand designers to be the user's advocate and keep the user's needs at the center of all design and development efforts. To design for human users also means you have to work with a heightened scope regarding accessibility and accommodating many potential users physical limitations such as reading small text. That's also why most UX designers work in some form of user-centered work process and keep channeling their best informed efforts until they address all of the relevant issues and user needs optimally. 4. Agile Rarely Trains on UX...: Agile is not easy for UX. Here are three reasons why agile methodologies are focused on developers. They grew at a programmer's attempts to solve common pain points experienced during big software development projects. Notoriously, the Agile Manifesto did not include UX people, nor did it account for the time, resources and research that UX professionals need in order to create excellent designs. Under an agile paradigm, the entire team works on the same elements of a project simultaneously in order to avoid throwing it over the wall and other words handed off from one team to another waterfall style. The work is done in sprints, commonly two-week periods when the team focuses on certain features and then moves on. As a result, designers are under enormous pressure to create, test, refine, and deliver their output unrealistically fast. And with little of the context and big picture thinking that since consistent user-centered designs, the two week sprints can force tunnel vision on the design team who may be so focused on a particular feature or the user story at hand that they may ignore the large-scale product and design implications, such as integration or user interface architecture. The absence of explaining UX and their processes from Agile training and books as lead teams around the world to exclude or minimize the involvement of specialists, product designers. When you incorrectly imagine that UX just draws boxes on pages, it's easy to assume I can do that job. Like so many American Idol auditions are sure they are the best singer on the planet. Most product managers and engineers self-assess as being great at UX. This normally means they believe they are great at laying out screens. But in fact, the UX specialist would not see a developer who makes wireframes as someone who should be given UX tasks. Books on Scrum suggests that if it UX specialists becomes a bottleneck, she should train non UX roles to do her job. This type of decision is rarely suggested about other roles in software development. Nobody would want an untrained or an experienced developer to do the coding, even after a bootcamp or reading a book about programming, we would never suggest that if a developer becomes a bottleneck, she should train the project manager to do some coding. Hiring managers who incorrectly believe that UX is an artistic job, hire artists to do UX work. There is no educational overlap between a degree in UX and UI. Natural talents often don't overlap. Somewhat graded UX might be a poor artist and vice versa. Hiring for UX UI often delivers you a great artist with minimal UX experience, expertise, process, or education. Those looking only at the bottom line would love to slash the budget by giving you access to individuals who might lack UX education, experience, expertise, skill, or natural talent. But this is shortsighted and can lead to poor productivity, efficiency, culture, product, and customer satisfaction. 5. What Is a Scrum Team?: Scrum teams are cross-functional, meaning the members have all the skills necessary to create value each split. The entire scrum team is accountable for creating a valuable, useful increment. Every sprint Scrum defines three specific accountabilities within the scrum team, the developers, the product owner, and the Scrum Master. The scrum team is small enough to remain nimble and large enough to complete significant work within a sprint. Typically ten or fewer people. Usually a Scrum team has one tester, one UX designer, and multiple developers. A Scrum team is a self-organized team and is responsible for completing the task they've picked up in a sprint. Was Product Owner accountable for? The Product Owner is accountable for maximizing the value of the product resulting from the work of the Scrum Team. Among all his responsibilities, the product owner develops and explicitly communicates the product goal. For product owners to succeed, the entire organization must respect their decisions. These decisions are visible in the content and ordering of the product backlog. And through the inspector will increment at the sprint review. The product owner is one person, not a committee. The product owner may represent the needs of many stakeholders in the product backlog that was wanting to change the product backlog can do so by trying to convince the product owner. Now, let's talk about the scrum master. The Scrum Master is accountable for establishing Scrum as defined in the Scrum guide. They do this by helping everyone understand Scrum theory and practice, both within the scrum team and the organization. The Scrum Master is accountable for the scrum team's effectiveness. They do this by enabling the scrum team to improve its practices within the Scrum Framework. Scrum Masters are true leaders who served the scrum team and the larger organization. Scrum has certain events that need to follow, including product backlog, grooming Sessions, planning meetings, daily scrums, or daily standups, Sprint Reviews, and retrospectives. All team members, including product owner, participate in these events. 6. UX Designer Within Scrum Team: Being part of a Scrum team, developers, testers and UX designers work together. It is important to keep UX work ahead of developments so that things do not get delayed in a sprint. This makes the role of UX designer very critical. He has to provide required UI artifacts to team before they start implementing the UI. Within team, developers can easily approach UX member and ask him about any missing part of design. If a developer needs clarification on a design for a user story they're working on. And the designer should stop their work on the next sprint and focus on the current sprint. In this way, the designer is both looking ahead and staying focused on the present. Likewise, it's a good rule of thumb to have a developer in the meeting when UX deliverables are being discussed so that they can review and give their insight. Ux member can review the implemented work at runtime and any suggested changes are easier to incorporate in implementation. Tester can communicate UX designer about the design UI and write effective test cases by referring the design work. He can test the implementation and conveyed his concerns to developers and UX designer at the same time. Hence, a Scrum team sitting at one place works to improve product quality with better communication between UX member, tester and developers. A technique for better collaboration in Scrum model is community of practice, COP, which is a platform to share knowledge and defined guidelines related to a common interest. Ux COP helps all UX designers to maintain a consistent design standards among all teams. 7. UX Design & Scrum Process: Since a sprint, we'll focus on the creation and implementation of a product which requires extensive coding. You might be wondering how can design and development work hand in hand using Scrum. Wouldn't they need to have all the UI assets and information before they can code? The product owner will have created user stories for the developers on the team. If one of those user stories is create login page, developers will need to have all the requirements and assets like mockups and prototypes needed for those particular user stories. Since the UX design work has to be completed before the sprint begins, UI and UX designers should work ahead of any sprint cycle. Before a developer begins to work on a user story. That user story has to be designed, tested, and research weeks, if not months in advance. If the developer doesn't have all of this information at their disposal, it's unlikely that they'll be able to complete the work in a two-week or four week sprint. Ux and UI designers have their own workflow which is made up of gathering requirements, brainstorming and ideation, research, wireframing and prototyping, testing. The spirit relies on these elements being done in advance and as a result, they can't be done concurrently with development. 8. How to Fit Design Into the Scrum Process?: It can be tricky to find out where design fits into the Scrum process. The debate rages on as to whether or not designed should even be incorporated into agile sprints. In the following diagram, we explore an overlay of UX and design activities on top of this well-founded model of Scrum, this proposal has been made by Jeff got Delft, author of The Lean UX book. As you review it, please note the following caveats. This is by no means a comprehensive listing design activity. There aren't enough post-its in the world to cover that. The word design, often with a capital D serves as an umbrella term for all activities that designers of all kinds normally do or take part in. Each grouping of UX activities is numbered from one to five. Let's review each of them. Won. The Product Backlog contains the pieces of the broader vision and are not going to be worked on in the current sprint. High-level items, vision, and many assumptions live here to inform the Product Backlog activities like design sprints, research, qualitative, all types, and hypothesis writing help inject both reality and a customer-centric focus to these items. To sprint planning is the day-to-day level planning effort for the team. Questions like, what will it look like? How will the product flow from screen to screen? What are the exceptions we'll need to deal with? Can be answered with design tools like collaborative sketching, aka design studios, shots, et cetera, and other group brainstorming activities that UX designers are particularly good at facilitating. Free. The tactical design work has to go into the tactical backlog, the sprint backlog, and is then executed by designers primarily, but also in collaboration with the rest of the Scrum Team. The key is to prioritize this work in a way that allows all team members to work in parallel. For critically missing from the core Scrum Team and necessary for the integration of UX Design is a full-time designer on the team. The only way the tactics and number three can happen in parallel collaboration with developers, product managers, and Scrum Masters is if there is a full time designer on the team. Five, Sprint Review is an opportunity to take a look together as a team at the output the team generated during the Sprint. This is also an opportunity to review what we've learned during the sprint. Aka the outcomes. Activities like design reviews, discussion, and debate of research synthesis and quantitative analysis and form the work we're considering, pushing live and help us focus our next round of both product and sprint backlog prioritization. It's critical to point out that none of this can happen without a dedicated designer assigned to the scrum team. Hits their presence that ensures the relevant activities are proposed, are prioritized and executed. If the design work is outsourced to a designer outside of the team, regardless if that designer is in house or not, then the team finds itself back in the big design up front style of working, also known as waterfall or the sprint ahead method. All of which reduced collaboration, shared understanding, and trust between team members. 9. Zoom on 3 Practices (Design Sprint, Design Studio & MVP): Back to our diagram, we're going to explore three practices in particular. Designs sprint Design Studio, also called collaborative sketching and MVP, or minimum viable product. Let's start off with design sprint. 10. Design Sprints: The design sprint methodology was developed at Google from a vision to grow UX culture and the practice of design leadership across the organization. Multiple teams within Google experimented with different methods from traditional UX practice, IDEO, the Stanford D School, Business Strategy, and even psychology, applying them to support divergent and convergent thinking with teams. The resulting framework and set of methods is flexible and teams are continuing to adapt it based on different goals and organizational cultures. The design sprint is a proven methodology for solving problems through designing, prototyping and testing ideas with users. Designs, sprints quickly aligned teams under a shared vision with clearly defined goals and deliverables. Ultimately, it is a tool for developing a hypothesis, prototyping an idea, and testing it rapidly with as little investment as possible in as real and environment as possible. How does a design sprint work? In order to run a successful design sprint, you need three basic ingredients. A successful design sprint cannot start without a clearly defined challenge. A challenge determines the scope and the goal of the design sprint. Let's say you have a SaaS product where you offer a free trial period, but you struggled to convert trials into real customers. In this case, your challenge could be this. How might we improve the experience during our 30 day trial period to successfully convert more leads into paying customers. You need a cross-functional team of Ideally six to eight max ten participants that are motivated and bring all necessary skills to tackle the challenge. If you take the challenge from above, a good team should certainly include the product owner and people from marketing and sales, but also a designer and people from the development and customer support team. Because the design sprint process is super PAC with fast-moving exercises, the success of a design spread greatly depends on a skilled facilitator. They will do the preparations, lead the team through all tasks, and guide discussions and team decisions. The facilitator should therefore be someone who not only has experienced with the design sprint, but also great communication and team management skills. 11. > Design Sprint Methodology: The design sprint follows six phases. Understand defined, sketch, Decide, Prototype, and Validate. Let's explore each one of them. In the understand phase, you will create a shared knowledge base across all participants using the Lightning Talk method, knowledge experts across the business are invited to articulate the problem space from business user, competitor and technological angles. Lightning talks are a core design sprint method and a powerful opportunity to build ownership in the design sprint challenge, plan and set up lightning talks before your design sprint begins. Depending on your goal or deliverables. You may spend up to half a day on these talks. After all the Lightning Talks are finished, hold. Hm. W, how might we sharing session to capture and share all the opportunities your team has come up with. Each lightning talks should last ten to 15 minutes. Topics should cover the business goals, Research, and a technology review of relevant and as well as anything else that may be pertinent to your challenge, such as legal considerations, material reviews, or a competitive analysis. Subjects vary depending on your industry or field. In the Define phase, the team evaluates everything they learned in the understand phase to establish focus. This is done by defining specific contexts and desired outcomes of potential solutions. The phase concludes by choosing a specific focus for your sprint, as well as goals, success metrics, and signals. In the sketch phase, the design sprint team generates and shares a broad range of ideas as individuals. You will start by looking for inspiration such as solutions in alternative spaces. Then each design sprint participant will individually generate ideas for consideration from their team will narrow down ideas as group to a single well articulated solution sketch per person. In the Decide phase, the design sprint team finalizes the direction or concept to be prototyped. Each participant will share their solution sketch and the team will find consensus on a single idea through decision-making exercises. The final direction will aim to address the design sprint focus. In the prototype phase, the design sprint team will work together to create a prototype of your concept. This is when many decisions are made around what exactly the concept is and includes. You will aim to create a prototype that is just real enough to validate and you will do it really fast. What do we mean by prototype? You can think of your prototype as an experiment in order to test out a hypothesis. This means you have to think critically about what you will build in order to get that feedback, you need to validate or invalidate your hypothesis. Anything can be prototyped in a day if it is clearly mapped out. In the validate phase, the design sprint team will put your concept in front of users. This is your moment of truth. You will gather feedback from users who interact with your prototype. And if relevant, you will conduct stakeholder and technical feasibility reviews. You lend your sprint with a validated concept or an invalidated concept to improve on. Either way, you've made progress. Depending on the feedback of the users. There are different outcomes and ways to proceed after the spread. If the feedback was great, the team can often use the prototype to get down to the details, defining requirements, and preparing the implementation. If you get mixed feedback, you can run a second design sprint to iterate on your designs and conduct some more user tests. Sometimes the design sprint can reveal that you are on the absolutely wrong track. In that case, be happy that you didn't invest more than one week and move on. 12. > Design Sprint Week: In this section, we're going to see how a design sprint week would be like. On Monday, we tackle the understand and define phases. The first day of the design sprint is all about understanding the challenge and exploring the problem. This involves mapping out the customer journey and conducting expert interviews. On Tuesday, we'll move to the sketch phase. Once the team understands the problem, it's time to generate solutions. Through a series of creative exercises. Each participant will first create a bunch of potential ideas and finally come up with their own concepts sketched on paper. Then on Wednesday it's time to make a call during the Decide phase, the team votes and decides which concept will get prototyped. This can be one solution, but more often than not, it's a combination of the best parts of multiple ideas. On Thursday, we turn to the prototype phase. The team will create a high fidelity prototype from the final concept and prepare the user tests for the next day. Finally, on Friday, it's the validate phase. On the last day of the design sprint, the team will present the prototype to five users together, their feedback and ideas. At the end, the team knows exactly how to move forward. Go to this address if you want to know more about design sprint. How do you incorporate a design sprint in Scrum? Scrum Master will be able to get their head around the concepts of the design sprint in no time. Basically, the process works like this. First, set your challenge, gather the team and run a design sprint. After completing the design sprint, use the prototype and feedback to systematically derive User Stories from it. There is no real best practice for this. But we find User Story Mapping by Jeff Patton, the perfect way to bridge the outcome of a design sprint. Take the derived user stories and plan your sprint backlog as usual. During the Scrum sprint, the team can then use the prototype created during the design sprint to iterate and create detailed interfaces for the various user stories. This requires the development and design team to work closely together. To give you a better picture. Here are four major situations where design sprints becomes super handy for Scrum teams. When starting new projects, when adding or changing big features. When the product vision, roadmap or Backlog are out of focus. And when you face big challenges or on specific requirements. When starting new projects is the most obvious time to run a design sprint and can change the course of your product development. Defining what your product or business model is a huge and hard task, usually requires a lot of research, time, and money to get it right. Before you make any big investments, you want to know if everything is going to work in almost have a snapshot of the future if you could. Unlike numbers and data projections, a design sprint is a fast way to get qualitative customer feedback and can be used in an agile iterative way to develop products and business ideas with more certainty and less upfront development commitment. When adding or changing big features, usually companies or teams need to take a huge bet on a product or strategy. This could be to be a groundbreaking idea, bringing something new to the market or to beat a competitor with more innovative ideas. Vague ideas usually require a big budget as an initial investment to execute and go to market. Design sprints help by taking away the uncertainties if a product will be a success or not. It answers if the product slash service is going to work as intended and if customers are going to want to use slash buy the product or service. When product design teams, developers and stake holders do not align on an idea or a way forward on a project back and forth. Meetings without outcomes can become a common practice and a true waste of time. This is a great time to run a design sprint because it places the different stakeholders in one room that creates a level playing field for everyone to be heard by defining what the problem is, focusing on it alone but together helps teams to line on what they are trying to solve. This allows teams to identify and focus on the big problem for the period of the Design Sprint. The outcomes of the Design Sprint will guide which direction the products slash project is going to go and what the next Bible steps bar. When you face big challenges or on specific requirements. In any project, there are many things that derail us from archiving our goal and stay aligned as product teams. As could be technical issues, a decision that is not being made because of office politics or stakeholder misalignment. All these are practical everyday challenges we find as product teams. Design sprints, assist in creating a focused, time-boxed and political less environment to be able to move faster with making product decisions and test ideas officially. 13. > Design Sprint & Scrum: How do you incorporate a design sprint in Scrum? Scrum Master will be able to get their head around the concepts of the design sprint in no time. Basically, the process works like this. First, set your challenge, gather the team and run a design sprint. After completing the design sprint, use the prototype and feedback to systematically derive User Stories from it. There is no real best practice for this. But we find User Story Mapping by Jeff Patton, the perfect way to bridge the outcome of a design sprint. Take the derived user stories and plan your sprint backlog as usual. During the Scrum sprint, the team can then use the prototype created during the design sprint to iterate and create detailed interfaces for the various user stories. This requires the development and design team to work closely together. To give you a better picture. Here are four major situations where design sprints becomes super handy for Scrum teams. When starting new projects, when adding or changing big features. When the product vision, roadmap or Backlog are out-of-focus. And when you face big challenges or on specific requirements. When starting new projects is the most obvious time to run a design sprint and can change the course of your product development. Defining what your product or business model is a huge and hard task, usually requires a lot of research, time, and money to get it right. Before you make any big investments, you want to know if everything is going to work in almost have a snapshot of the future if you could. Unlike numbers and data projections, a design sprint is a fast way to get qualitative customer feedback and can be used in an agile, iterative way to develop products and business ideas with more certainty and less upfront development commitment. When adding or changing big features, usually companies or teams need to take a huge bet on a product or strategy. This could be to be a groundbreaking idea, bringing something new to the market or to beat a competitor with more innovative ideas. Vague ideas usually require a big budget as an initial investment to execute and go to market. Design sprints help by taking away the uncertainties if a product will be successful or not. It answers if the product slash service is going to work as intended and if customers are going to want to use slash buy the product or service. When product design teams, developers and stake holders do not align on an idea or a way forward on a project back and forth. Meetings without outcomes can become a common practice and a true waste of time. This is a great time to run a design sprint because it places the different stakeholders in one room that creates a level playing field for everyone to be heard by defining what the problem is, focusing on it alone, but together helps teams aligned on what they are trying to solve. This allows teams to identify and focus on the big problem for the period of the Design Sprint. The outcomes of the design sprint will guide which direction the product slash project is going to go and what the next Bible steps bar. When you face big challenges or on specific requirements. In any project, there are many things that derail us from archiving our goal and stay aligned as product teams. This could be technical issues, a decision that is not being made because of office politics or stakeholder misalignment. All these are practical everyday challenges we find as product teams, designs, sprints assist in creating a focused, time boxed and political lesson environment to be able to move faster with making product decisions and test ideas officially. 14. Design Studio: Design studio is a way to being a cross-functional team together to visualize potential solutions to a design problem. Design studio sessions worked by putting designers, developers, subject matter experts, product managers, business analysts, and other competencies together in the same space and focusing them all on the same challenge. Design studio creates an outcome far greater than working in silos allows. What are the benefits of design studio? It breaks down organizational silos. Inquiry is a forum for fellow teammates. It starts to build the trust. The team would need to move from formal sessions to more frequent and informal collaborations. Design Studio can be conducted using the following steps. The first step is problem definition constraints. It should last between 1545 minutes. The goal is ensuring that everyone is aware of the problem which is being solved. Assumptions are declared to the entire teams personas that are fictional character created to represent a user type that might use a product in a similar way or known to the entire team. Hypothesis. And the constraints within which we're working on are known by the entire team. The step can be anything from a formal presentation with slides to a group discussion based on the team's level of comfort. Step two involves individual idea generation for ten minutes, each member of the team can be given a six up template. Everyone should spend five minutes to generate six low-fidelity sketches of solutions for each persona slash pain point pair on their six, each box should have a different solution. This should be visual articulations, UI, sketches, workflows, diagrams, et cetera, not written words. During step three, it's time to present and critique the ideas going around the table. Each participant should be given three minutes to hold up his or her sketches and present them to the team. Presenter should explicitly state for whom they were solving a problem, the persona, which pain point they were addressing, the hypothesis. Explain the sketch. Each member of the team should provide critique and feedback to the presenter. Critique should focus on clarifying the presenters intentions. Then between 510 minutes, the step four will be on iterate and refine. Each participant should be asked to take his or her original six ideas and using the critique they received to refine their thinking into one big idea on a single sheet. The last and fifth step is team idea generation. At last 45 minutes max. Once everyone on the team as feedback on his or her individual idea, the team must converge on one idea. Emerged idea will serve as the basis for the next step in the Lean UX process. Creating an MVP and running experiments. There would be a lot of compromise and wrangling at this stage to get consensus, the team would need to prioritize and pare back features. That teams should be encouraged to create a parking lot for good ideas that don't make the cut, which will make it easier to let go of ideas. The artifacts created in the Design Studio can be used to create refined wireframes, prototypes, and early code that will drive the team forward and proving their hypothesis. How do you incorporate a design studio in Scrum? After about an hour, mockups discussed at the Design Studio are fleshed out. The product owner and the UX designer work on these mockups to refine it and design the user stories that will be discussed at a sprint planning once they're ready. 15. MVP (Minimum Viable Product): A Minimum Viable Product. Mvp is a concept from lean startup that stresses the impact of learning and new product development. Eric Reese, define an MVP is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort. This validated learning comes in the form of whether your customer will actually purchase your product. A key premise behind the idea of MVP is to produce a product that the team can offer to customers and observe their actual behavior with a product or service. This product may be no more than a landing page or a service with an appearance of automation, but which is fully manual behind the scenes. Seeing what people actually do with respect to a product is much more reliable than asking people what they would do. When the team creates an MVP. The first thing they have to do is consider what they are trying to learn. It's useful to think about these three basics questions. Is there a need for the solution I'm designing? Is there value in the solution and features I'm offering? Is my solution usable? One of the most effective ways to create MVPs is by prototyping. While prototyping there is not need to prototype the entire product experience. Instead, the most important part of the experience for the customer and business should be simulated. Team should focus on the core workflows that illustrate the MVP. While each of the MVP should be purpose-built to test a given hypothesis. With a little upfront planning, one can design an MVP that let's simultaneously test multiple closely related hypotheses. For example, in this image, you can see hypothesis one and hypothesis two each mapped to a corresponding MVP. However, hypothesis three and hypothesis for our presumably so closely related that they can be validated using only a single MVP. It's important to remember that the concept of an MVP comes in two distinct flavors. To validate riskiest assumptions by understanding what the market wants to deliver limited functionality for fast customer value and business benefit. In the UX world, each design is a proposed business solution hypothesis. The goal is to validate the proposed solution as efficiently as possible by using customer feedback. Teams build minimum viable product and ship them quickly to begin the process of learning as early as possible. Remember, the basic concept of MVP is pretty simple. What's the smallest thing that we can build to confirm if our core assumption is correct. How and when do you incorporate a minimum viable product in Scrum? Mvp is neither a Scrum Event nor a strum artifact, but a mindset. It means that the entire team should have the MVP mindset. When should they have it? During initial discussions with the stakeholder, during the design workshop and initial requirements phase, during sprint planning, before actually committing to the work. This is a great opportunity to evaluate whether a story is chunked in an appropriate size. Before committing, we make sure we calculate the costs during the sprint or at Sprint Review. When stake holders give feedback and when considering user feedback, either from bug reports or from usability testing. 16. Role of UX Designer in Scrum Team: Let's talk about the role of a UX design in a Scrum team. First, we need to answer this question. What does a UX designer do? A UX designer defines use cases and starts design work by involving required stakeholders, including product owner and members of his Scrum Team. It is important to empower the role of UX designers so that he can make sure the desired and the limitation of the design features. Ux designer should also take ownership of design work and provide all required artifacts and specs to development by following the defined standards. Ux member is part of UX community of practices COP, which works likes a Virtual Group where all UX designers collaborate regularly and share information, improve their skills, define and review standards and guidelines and ensure consistent design work among all Scrum teams. Is the responsibility of UX member to consult with UX COP for necessary coordination and help embed your UX designer in the Agile team. She should attend release planning daily stand up retrospective. At every meeting where UX might be discussed. Allow us to estimate their time during release planning so that there are no surprises about the timing UX tasks will require. Don't make decisions without them. 17. Problems Faced by UX Designers: Being a single member from UX group, UX designer and a Scrum team sometimes starts getting influenced by other team members. And if the UX designer is a junior member of the team, then it makes it difficult for him to stand for his design opinions. Let's discuss what challenges at UX designer has to meet. First, the UX member is under influence of senior members. A Scrum team mostly contains developers and most of the time scrum master is also from development team. The senior developers sometimes try to influence the design created by UX member. They are in majority and can enforce their developer oriented approach in design work. Okay, so now let's discuss the second challenge. When the UX member is lacking of technical knowledge. Ux designers lacks technical knowledge of the product. He's not much aware of the technology being used to implement the product. A developer can easily state that the design layout is not supported due to technical limitations. The UX member starts looking for other options to design the same feature. And this can sometimes result in a compromise on the user experience. Let's talk about the third challenge, how to maintain good relationship in team. The UX member is part of Scrum Team. He sits, works, eats along with team members is a challenge for him to build good relations within team as well as forced them to implement the defined experience. A good relationship sometimes makes his job easier and sometimes it makes difficult for him to convince other members. Let's take a look at the fourth challenge when there's a lack of ownership by the team. Since Scrum Team mostly contains developers, they don't have much understanding of user experience and its importance in a product life cycle. That's the reason that they don't own UX member and his work. If you xt member is working for more than one team, then this problem becomes even more severe. That leads us to the fifth challenge. When the UX member is shared. Though sharing of a member among multiple teams is highly discouraged in Scrum model, but still this practice is being followed at various places. If a UX member is shared among multiple teams, it is difficult for each team to own his responsibility. Also, UX member does not fully participate in events of each team. This can increase the distance between UX member and his teams, which results in delayed work and lack of trust. The last M6 challenges a quick delivery of UX work in sprint. If design work and its implementation is done in the same Sprint, then UX member needs to provide required UI artifacts to development early in the sprint so that they can work on its implementation and testing for new features. It is not possible for UX member to understand requirement, create, design, get feedback, finalize options, prepare specs, and coordinate with developers in the same spirit. Here are the six challenges that a UX designer face in a Scrum. Do you remember them? Let's quickly list them again. Influence of senior members, lack of technical knowledge, maintain good relationship in team. Lack of ownership by team, shared UX member, and quick delivery of UX work in sprint. In the next section, few recommendations are provided to overcome these challenges. 18. How to Meet These Challenges: Ux designer is a role that should have extensive knowledge of product he is working on. He should be aware of all features and their need in the product. It needs to get clear understanding of product, its use cases and user flows. Only this way he can confidently present design work to his team and other stakeholders. Ux members should learn all standards, guidelines and friends being followed within the organization. The training of a UX member is responsibility of other members of the UX group. Sometimes there are managers or lead roles in Scrum model whose responsibility is to train people in a certain domain. For example, a UX lead takes care of UX members nourishment and growth. Ux member requires to learn UX skills that helped him to produce good quality work. Ux members should actively participate in COP meetings. This will help them to grow and stand out in UX Field and make effective communication within their Scrum teams. All UX members are part of UX COP. This is a Virtual Group where UX members meet and decide about standards and trends they follow in design tasks. They review the UI work being done within Scrum teams and suggest possible improvements. Training of team members is also part of COP. Shared ownership and responsibility as desired among team members of a Scrum team. What does it involve? Ux member and developers need to have a good relationship. Us member should not be given the direction of UX work by developers. Neither UX members should ask developers to implement anything without doing proper user research. The whole team needs to work together to improve the user experience of the product. If there are problems that UX member is facing while working on his tasks than they should be resolved within team. It is responsibility of UX member to take part in teams activities and do not stay away since he has no idea of development. This will help them to know about technical limitations that a developer may encounter while implementing the UI. The purpose of sitting the whole team together is to learn from each other. Avoid sharing of resources. Sharing a resource across multiple teams can affect productivity of the resource. Also may impact transparency, which is a key rule of Scrum. If there is no other way than all assign tasks and responsibilities of shared resource should be clearly visible to all related teams. Developing a user experience to the level of customer satisfaction is not a single person or team's responsibility. Instead, it is accompanies vision. From CEO to management, product owners, Scrum Masters and team members, all should learn the importance of user experience in a product's lifecycle and how it impacts their customers. This will help us activities and members to attain a strong support from senior members in the organization. Okay, that was the last item. Let's do a quick review of the six ways to meet UX design challenge. First, have a strong knowledge of product, then provide proper UX training. Being part of an effective UX COP is the third way. Also foster team ownership and support. Avoid sharing of resources. Lastly, develop a UX vision accompanies level. 19. Conclusion: Scrum is a methodology that has proven itself best for software development. Different Scrum leading names in industry have provided detailed rules in training for inspiration and guidance of organizations that helped them to follow scrum model and build successful customer products. Ux designer is an important role in Scrum that should be empowered and facilitate to an extent where he can perform his best to provide intuitive user experiences to their products. I hope you enjoyed this course and it will help you overcome challenges of UX designers.