Software development methodologies lack the details of how UX fits into organizations, teams, and projects. Some suggest that a Product Manager describing features is enough, UX should train others to do their work, or excluding UX solves them being "too siloed." This happens with no other role in software development. It's hurting culture, efficiency, and productivity, and creating poor products for customers.Your customer only sees your UX, not your 1000 developers or if you were Agile or Lean. Companies are figuring out that UX specialists and the User-Centered Design process are high-ROI and irreplaceable. Recent highly-publicized UX failures remind us that skimping on UX can alienate customers, create negative media attention, and burn millions of dollars.Learn how the UX process fits into Agile and Lean; augments DevOps goals; increases customer satisfaction; and saves time, money, and sanity... all before developers write a line of code.--------------------------------------------------Across companies of all sizes, there is a clear pattern: People don't understand UX and they're not sure how it works into their organizations.You've probably had conflicts with UX practitioners. They don't seem Lean or Agile. In fact, they're throwing off your Agile train so badly you want to throw them under it They're killing ideas, timelines, and budgets. Their work looks easy, why can't you just do it yourselves? UX seems like a black box disappearing for weeks or months and then just telling us what to build. Where are the communication and collaboration?UX practitioners are keenly aware of these conflicts and how they are seen as the problem. Non-UX roles have many misunderstandings and myths about UX including these issues: -Agile methodologies often don't mention UX at all, as if the people designing what Engineering will build are not important or necessary.-Everybody thinks UX is just wireframes and "anybody can draw boxes on a page," but it's far from that. -UX isn't formalized and doesn't have defined processes or approaches; it's whatever the designer "feels like." False -Companies select the wrong people for a job that HR and hiring managers don't understand. They think these roles require artists, but UX is not an art job.-Teams are sure they don't need UX or can't afford it, often without knowing what UX work and tools actually cost.-Product managers often want to "do UX work" before or during a project. However, they don't realize that what they are doing isn't really UX.-Developers often aren't sure what UX is or believe those are the workers who A/B test things after release. That's too late for user testing. Wouldn't engineers like to know before they code that what they're working on has been validated as being a good product or feature for customers? Yes, they often think that idea sounds great You'll learn to dispel these UX myths, misunderstandings, and more in this book. Let's get your DevOps out of the ICU. Learning goals include:1) The correct integration of UX saves time, money, increases efficiency, keeps engineering's changes to a minimum, & creates the best product for users.2) UX specialists conduct research, design the entire product, learn from testing, iterate to fix flaws, & deliver vetted blueprints so engineers build once.3) How User-Centered Design fits into project timelines and development methodologies including Agile and Lean.4) The benefits of bringing UX specialists in early during portfolio planning and management.--------------------------------------------------"If you're a member of an Agile team and you're struggling to understand how best to partner with UX, DevOps ICU is the book for you. Debbie's real-life stories and experiences will light your path. And the book is pretty funny, too." - Travis Bjorklund, Senior Manager, Product Management and Agile Transformation
