<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>user experience | Scrum Agile Project Management Expert</title>
	<atom:link href="https://www.scrumexpert.com/tag/user-experience/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.scrumexpert.com</link>
	<description></description>
	<lastBuildDate>Tue, 07 Jun 2022 14:04:56 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://www.scrumexpert.com/wp-content/uploads/favicon.png</url>
	<title>user experience | Scrum Agile Project Management Expert</title>
	<link>https://www.scrumexpert.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>Lessons Learned from Building a Design System</title>
		<link>https://www.scrumexpert.com/knowledge/lessons-learned-from-building-a-design-system/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 13 Apr 2022 08:46:21 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[scrum team]]></category>
		<category><![CDATA[user experience]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=7010</guid>

					<description><![CDATA[Although it has been among the trending topics for a few years, the Design System subject doesn&#8217;t seem it’s vanishing from discussions between designers and developers anytime soon. And there is a reason for that. Author: Rhanna Andrade, Labcodes, https://labcodes.com.br/ Building a Design System involves much more than just creating a library of UI elements. It&#8217;s a process that must consider many other factors, such as the purpose, the tools and the people who will use that library. It&#8217;s like being able to reflect all the values of the company, whose Design System will serve, in a documentation that must be intelligible to whom it&#8217;s intended. Knowing that there is the possibility of making products and experiences more cohesive, and more consistent flows is one of the main reasons why this is still a hot topic and with many referenced cases out there. Here at Labcodes we believe that, to achieve successful results, we need to master the process. We use agile methodology on a daily basis, as well as design and development best practices, so this project was no different. We cherish that both the Design and Development teams, who would be involved with this task, participated in all the stages and were 100% aware of each decision. As the designers also participated in the implementation of the UI, the need for communication between the two teams was irrefutable. When we started our own DS, we thought about what steps we would follow to ensure that our result was <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/lessons-learned-from-building-a-design-system/" title="Lessons Learned from Building a Design System">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Connect Design Sprints and Agile Sprints</title>
		<link>https://www.scrumexpert.com/videos/connect-design-sprints-and-agile-sprints/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 10 Feb 2020 10:27:10 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[sprint]]></category>
		<category><![CDATA[user experience]]></category>
		<guid isPermaLink="false">https://www.scrumexpert.com/?p=6149</guid>

					<description><![CDATA[Design Sprints have changed the way businesses create new products and services. But how do they relate to Agile development sprints? And how can the two be connected so that Scrum teams deliver higher quality products in less time? Video producer: https://www.agileonthebeach.co.uk/]]></description>
		
		
		
			</item>
		<item>
		<title>Google Design Sprint Kit</title>
		<link>https://www.scrumexpert.com/resources/google-design-sprint-kit/</link>
					<comments>https://www.scrumexpert.com/resources/google-design-sprint-kit/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 30 Jan 2018 17:57:57 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Resources]]></category>
		<category><![CDATA[sprint]]></category>
		<category><![CDATA[user experience]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=4860</guid>

					<description><![CDATA[The Google design sprint framework is a five-phase framework developed by Google that helps answer critical business questions through rapid prototyping and user testing. The design sprints let teams reach clearly defined goals and deliverables and gain key learnings. According to Google, this process helps spark innovation, encourage user-centered thinking, align teams under a shared vision, and get faster to product launch. Created in 2010, the Google design sprint framework is the result of the study and test of 300 different business strategy, design thinking, and user research methods from places like IDEO and Stanford d.school. Google took the most effective ones and evolved them, arranging them into a framework that supports both divergent thinking (creative brainstorming that results in multiple possible solutions) and convergent thinking (using defined, logical steps to arrive at one solution). The methodology has evolved over time and continues to be refined and tested. The Google design sprint framework website provides different case studies, a step by step guide to planning the design sprint, tools and templates tools to help you run design sprints and a FAQ. In the context of Scrum, this approach could be interesting to explore before you actually launch you project in a process that is often labeled as &#8220;iteration zero&#8221;. Read all the documentation about the Google Design Sprint Kit on https://designsprintkit.withgoogle.com/]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/resources/google-design-sprint-kit/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Using Personas to Support User-centered Design</title>
		<link>https://www.scrumexpert.com/knowledge/using-personas-to-support-user-centered-design/</link>
					<comments>https://www.scrumexpert.com/knowledge/using-personas-to-support-user-centered-design/#comments</comments>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Mon, 26 Jun 2017 15:18:23 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[product management]]></category>
		<category><![CDATA[product owner]]></category>
		<category><![CDATA[user experience]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=4499</guid>

					<description><![CDATA[If some consider Scrum as an Agile project management framework, many people consider that is is more a product management approach. Anyway, Scrum is about understanding the need of the customers to deliver value. In this context, the concept of &#8220;personas&#8221; can be used to support user-centered design throughout a product development cycle by focusing on the characteristics of key user segments. The article of Aurora Harley starts with a definition of the concept of persona: &#8220;A persona is a fictional, yet realistic, description of a typical or target user of the product. A persona is an archetype instead of an actual living human, but personas should be described as if they were real people. The description should be thorough, including details about the persona’s needs, concerns, and goals, as well as background information such as age, gender, behaviors, and occupation.&#8221; The article provides an example of such description. The article explains that personas should be created as soon as possible and that they should be created by the team. The involvement of the team in the creation process allows to make them aware of user research data and to have a better confidence of the persona with the contribution of their own input. Each piece of information of the persona should affect the final design or help make decisions easier. The conclusion is that &#8220;The main benefit of using personas is that they create a common, more precise vocabulary for describing a certain type of user and thus focus <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/using-personas-to-support-user-centered-design/" title="Using Personas to Support User-centered Design">[...]</a>]]></description>
		
					<wfw:commentRss>https://www.scrumexpert.com/knowledge/using-personas-to-support-user-centered-design/feed/</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>User-Centered Agility Assessment and Benchmark</title>
		<link>https://www.scrumexpert.com/resources/user-centered-agility-assessment-and-benchmark/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 26 Apr 2016 16:04:19 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Resources]]></category>
		<category><![CDATA[user experience]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=3386</guid>

					<description><![CDATA[DUCAT is a free assessment and benchmarking online tool that aims at creating awareness for user-centered agility and enable companies to easily assess the status of their projects. The tool provides a 360 degrees assessment to investigate the team&#8217;s perspective and process. These results are completed with the users&#8217; evaluation of of the product. When you start to assess a new project, you go through a first screen where you can define it and provide additional information on your team and development approach (Scrum, Kanban, etc.). You can then invite the team members by e-mail to fill the survey. It takes less than 20 minutes per team member to complete the survey. They will answer questions like &#8220;We frequently develop working software that is tested, integrated and executable as a partial system&#8221; or &#8220;Developers communicate and collaborate with business people continuously to incorporate their evolving requirements&#8221;. You can also send a link to the users so they can fill a 3 (web) pages easy survey on how they feel about the product. Take this assessment on http://www.user-centered-agility.org/]]></description>
		
		
		
			</item>
		<item>
		<title>UX in Agile Product Management</title>
		<link>https://www.scrumexpert.com/videos/ux-in-agile-product-management/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 08 Mar 2016 12:52:12 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Videos]]></category>
		<category><![CDATA[product management]]></category>
		<category><![CDATA[product owner]]></category>
		<category><![CDATA[user experience]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=3276</guid>

					<description><![CDATA[Agile has become the de-facto standard for innovating new products in software development. But an Agile project needs good product management and good UX design to succeed. Fitting UX in with product management and Agile can be uncomfortable for UX designers. Once you get it, though, you’ll never want to work any other way. This presentations covers: * Why Agile works well for innovation and for software delivery * What product management is and why your software product can’t succeed without it * The different product phases: Discover, expand and exploit * The role of UX in each phase * Setting up hypotheses and metrics to keep Agile teams on track * How to get the time to do your design * How to make sure the users get a voice too Video producer: http://uxsouthafrica.com/ Further reading: The UX Runway &#8211; Integrating UX, Lean and Scrum Cohesively]]></description>
		
		
		
			</item>
		<item>
		<title>Impact-Driven Scrum</title>
		<link>https://www.scrumexpert.com/knowledge/impact-driven-scrum/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 05 May 2015 13:30:57 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[product owner]]></category>
		<category><![CDATA[scrum team]]></category>
		<category><![CDATA[user experience]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=2516</guid>

					<description><![CDATA[One of the important concept around Agile and Scrum is that it is more important to build the right product than to build the product right. Impact Management is a framework that helps managers to focus on impact of an idea and a product. In her article &#8220;Impact-Driven Scrum Delivery&#8221;, Ingrid Domingues explains how to brings together Scrum and Impact Management in software development projects where design is important. Impact Management is based on Impact Mapping that provides the ability to define expected impact for business and users in a model, in such a way that it can be evaluated and measured at any specified time. This approach takes care of the business side of a project. Scrum provides a perfect communication platform where the business perspectives can meet the software development aspect that needs to deliver. Thus Impact-Driven Scrum Delivery marries the two, and helps both perspectives perform better with autonomy and purpose. Impact-Driven Scrum helps also to solve the problem of the Product Owner who lack the skills to manage the design aspects of a product. This is achieved with the support of a a User Experience (UX) Lead that work as a proxy of the Product Owner in the design area. The article describes what are the responsibilities and the tasks of this UX Lead during the &#8220;minus 1&#8221; and &#8220;zero&#8221; sprints. The conclusion of Ingrid Domingues is that &#8220;Our experience of this way of working is extremely promising. It gives the team the potential to deliver <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/impact-driven-scrum/" title="Impact-Driven Scrum">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Adapting Scrum to UX</title>
		<link>https://www.scrumexpert.com/knowledge/adapting-scrum-to-ux/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Tue, 02 Sep 2014 19:54:43 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[user experience]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=2094</guid>

					<description><![CDATA[User eXperience (UX) includes the practical, affective and valuable aspects of human-computer interaction and product ownership. This article from Anindya Sengupta tries to answer common questions about UX and Scrum. It explores the challenges faced by a team working with a separate UX team in Scrum. It also gives recommendations for UX teams that are part of a Scrum team. The article is based on a scenario where a development team and a UX team work together on a Scrum project from two different locations. The article provides some tips on how UX professionals can succeed in a Scrum project: * Plan in a fluid manner and onboard the UX team to Scrum. * Involve a developer in the review of UX deliverables. . * Use the second sprint to revise design deliverables and get stakeholder approvals. * Allow time for planning. * Facilitate communication between the UX team and the developer team. * Use collaboration tools to facilitate the Scrum team’s work. * Communicate face to face whenever possible. * Include the UX team in feature demos and reviews. The conclusion of this article is &#8220;on a Scrum project, a UX team that does not follow Scrum as part of its delivery model presents a serious challenge to realizing the benefits of Scrum. To solve this problem, someone from the Development team must serve as a point of contact and work closely with the UX team on a regular basis to align the two teams’ timelines, as well as <a class="mh-excerpt-more" href="https://www.scrumexpert.com/knowledge/adapting-scrum-to-ux/" title="Adapting Scrum to UX">[...]</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Working as a UX Professional in a Scrum Teams</title>
		<link>https://www.scrumexpert.com/knowledge/working-as-a-ux-professional-in-a-scrum-teams/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Wed, 18 Sep 2013 15:41:29 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Blogs]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[definition of done]]></category>
		<category><![CDATA[scrum team]]></category>
		<category><![CDATA[user experience]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1640</guid>

					<description><![CDATA[The Scrum approach recommends to deliver software incrementally in small iterations. This seems to be always an issue with activities that require a global view on the developed application like the software architecture or the user interface. In this blog post, Aviva Rosenstein, who manages user research for Salesforce, shares here experience about integrating user experience (UX) design into the Scrum development process. UX often suffer from a lack of consideration from other roles in the Scrum team. Here are some of her recommendations for UX professionals: * Be transparent about the UX process to create trust in the Scrum team * Participate actively in the Scrum meeting, even if your time is share across multiple teams * Add meetings specifically devoted to the coordination of UX activities * Clarify the definition of Done to include UX criteria * Include UX goals and needs in sprint retrospectives Her conclusion is that &#8220;for Scrum and Agile to live up to its full potential, it must address the needs of all team contributors, not just software developers. Giving support and trust to UX contributors will help motivate them to do their best work and leverage more of their skills in the pursuit of excellence.&#8221; Read the complete blog post on http://boxesandarrows.com/the-ux-professionals-guide-to-working-with-agile-scrum-teams/]]></description>
		
		
		
			</item>
		<item>
		<title>Usability Investigations and Agile User-Centered Design</title>
		<link>https://www.scrumexpert.com/knowledge/usability-investigations-and-agile-user-centered-design/</link>
		
		<dc:creator><![CDATA[scrumexpert]]></dc:creator>
		<pubDate>Fri, 25 Jan 2013 13:56:34 +0000</pubDate>
				<category><![CDATA[Agile & Scrum Articles]]></category>
		<category><![CDATA[Knowledge]]></category>
		<category><![CDATA[user experience]]></category>
		<guid isPermaLink="false">http://www.scrumexpert.com/?p=1366</guid>

					<description><![CDATA[User interface (UI) design is often a neglected aspect of Agile software development and there are not a lot of article talking about the integration of UI experts in Scrum team. In this article, Desirée Sy provides the real life lessons on how user-centered design (UCD) practices were adapted to an Agile development process. Their interface design work was based on data gathered from contextual investigations to guide rapid iterations of prototypes, validated by formative usability testing. Going Agile, they needed to find a way to conduct usability tests, interviews, etc within iterations. To achieve this, they adjusted the timing and granularity of these investigations and the way that they reported our usability findings. The user interface experts preferred Agile user- centered design for the following reasons: * More of the product is designed than before. * Usability investigations are conducted throughout the entire product release life cycle, rather just at the beginning of a release. * The most important designs are worked on first and there is no effort wasted writing unused designs. * Product changes suggested by usability testing of current product can be implemented in the current release.]]></description>
		
		
		
			</item>
	</channel>
</rss>
