ModevUX AgileUX

Jul 19, 2012Download as KEY, PDF0 likes442 views

The document discusses Agile UX and emphasizes collaboration between designers and developers. It recommends starting with hypotheses rather than requirements and using techniques like design studios, sketching, and prototyping to iteratively validate concepts with users. Designers and developers should work together through practices like pair designing, sharing code literacy, and maintaining a pattern library.

MICHAEL JOVEL

• UI Developer at startapps

• My mother tells people I am
an international lawyer

•Istopped correcting her
because it is easier
twitter: @mjovel
• Worked with US Navy, email: mjovel@gmail.com
Progressive, University of
Chicago & University of MD

HISTORICALLY DESIGN HAS
BEEN BASED ON THE
WATERFALL METHOD

CREATIVE BRIEF > DESIGN > APPROVAL > PRINTER > DELIVERY

http://uxmag.com/articles/change-on-a-dime-agile-design

“Eric Reis
4 thstate of agile: A
story does not end at acceptance
but rather must be validated for
value

WORK IS MEANINGLESS
UNLESS YOU CREATE VALUE

HYPOTHESIS

• a tentative assumption made in order to draw out and test its
logical or empirical consequences - merriam-webster

WHY HYPOTHESIS?

• Rather
than make assertions it puts forth a questions which
must be then validated

• Engages team creativity

WHAT ASSUMPTIONS DO
YOU HAVE THAT IF PROVEN
FALSE WILL CAUSE YOUR
SOLUTION TO FAIL?

WE BELIEVE ___________
AND
IF THIS IS TRUE WE SHOULD
SEE __________

DESIGN STUDIO

• Butcherpaper, painters tape, sharpies and stop watch, grid
template sheets

• Build
small 3-4 person teams composed of designer,
developers and business team.

• Give each team a persona to focus on

SKETCH

•5 minutes to create 6-8 sketches individually

CRITIQUE

• two ways it accomplished goals

• two ways it failed to accomplish goals

TEAM SKETCHING

•5 minutes to iterate on best of individual sketches

TEAM PITCH

•3 minute pitch to entire group

PAIR DESIGNING

• Make sure designers and developers spend time working
together

• saves time on implementation

• promotes ownership

PATTERN LIBRARY

• Library of UI Patterns that developers can use (i.e. buttons,
ﬁelds, etc.

• Library of UI Components composed of multiple patterns
(i.e. forms, video player, etc.)

WHAT IS THE SMALLEST
AMOUNT OF WORK WE CAN
DO TO VALIDATE OUR
CONCEPT?

PROTOTYPE

• Paper

• Keynote / Powerpoint

• Axure, iRise, etc.

• Cordova (a.k.a Phonegap)

The document discusses the process of building games from start to finish, including developing an idea, designing the game, assembling a team, managing the project, dealing with delays, playtesting, submission, approval, and working with marketing. It provides tips for creating documents like a game concept, design document, and proposal. It also covers legal issues, keeping projects on track, and reaching the finish line.

Game Producer - How hard can that be?Ed Magnin

Game production requires an idea, design plan, art assets, programming, audio, project management, and persistence. A good game allows players to do things not possible in real life, make a difference, and is easy to learn but hard to master. Most games are late due to unrealistic deadlines, underestimating problems, and feature creep. Managing expectations, avoiding crunch time, reviewing features, and starting play testing early can help finish on schedule.

Couples Counseling for Software Development by Joe StageGROWtalks

This document provides advice for software development teams on improving their product development process through better collaboration between different roles. It recommends that engineers be involved early in the design process to address technical constraints. It also advocates for an iterative process of building minimal prototypes and getting early user feedback, rather than long development cycles. Teams are advised to focus on solving user problems rather than getting attached to specific technical solutions. Overall, the document emphasizes shortening feedback loops through practices like continuous deployment and automated testing.

Grassroots Innovation in the EnterpriseAtlassian

Perhaps the most under-utilized assets in most companies are the ideas in employees’ heads. For that reason, this session aims to help attendees learn three key things: How to tap into employees' passions to drive growth A useful model for assessing whether your innovation programs are effective How to use our “recipe book” to build a cohesive innovation program that drives growth This session is meant to cover the case for employee-driven innovation – including success stories and data points. We'll also provide access to the tools, playbooks, and templates that can accelerate innovation programs in your company.

Building immersive experiences: Usability you can really useX.commerce

Maintaining Continuous Learning Under Pressure Slides from Lean Agile Scotlan...Simon Phillips

Lean Product Development is predicated on validating assumptions that we make about the product we want to build in lightweight ways; user research, contextual studies, paper prototypes, simple clickable prototypes. A few short weeks of these activities can massively reduce the risk of building the wrong thing, and in a world where developing the wrong software can cost millions or sink a company, the investment can be well-worth the time. So how do you structure a project so that Product and Design have an opportunity to answer necessary questions, while making sure you're not wasting developer resources or boring the crud out of your team? This joint presentation by Pivotal Labs Product Manager Rosemary King, and UX Designer Simon Phillips will explore why up front investment in Discovery and Framing set up a project on solid foundation, how to involve development teams in the exploration and synthesis process, and how to set a cadence for your UX design work so that a comfortable buffer exists to allow for continual evolution of the product based on user feedback and changing understanding. Baked into the presentation will be case studies, challenges and lessons learned on recent lean/agile projects.

Garbage In, Garbage Out: Optimizing Design Inputs for Successful PrototypesKamaria Campbell

We’ve all heard the phrase “Garbage in, Garbage out”. The quality of a product or service is often linked to the quality of the underlying components. When it comes to prototypes, the truth is that much of the important work happens before we ever create a prototype artifact. This may include brainstorm sessions, creating requirements documents, analyzing an existing system, etc. More often than not, the effectiveness of the prototype is linked to how effectively these different aspects are managed in the pre-design process. Whether you are a designer, business representative, project manager or developer, this session will provide you with effective techniques for managing design inputs to create better prototypes.

Mythical Powers Of OssIwein Fuld

The document discusses both the pros and cons of open source software (OSS) compared to closed source software. It notes potential issues with closed source software like lengthy discussions over bugs and unclear ownership of extensions. Advantages of OSS mentioned include accountability, choice, and empowering technical people to fix problems directly. However, some downsides brought up are lack of guarantees, no warranty, questions over who profits from contributions, and whether investing personal time is worthwhile.

Design thinking & scrum v 3.0Sebastian Schürmann

Scrum and Design Thinking are two ends to the means of product development. Where Scrum stops to provide ideas on how to develop a product from a "minimum viable product" stage to a upgraded result, design(ers) thinking kicks in. Both love cross-functional teams, both consider doing more than talking/planning and both methods heavily resonate with the generation Y. All in all: There is more, that these two methods share than what devides them. Yeli Tong (UX/Design at XING) and Sebastian Schürmann (Founder of Dissident Trainings) give an insight in the real-life combination of these two methods and the challenges that arise when you put a scrum team, a product developer and a designer into a cage.

A Startup Story - Geekcamp PresentationArun Thampi

This document summarizes the development timeline and approach of Gameplan, a startup building a sports tournament platform. It describes key milestones from April to September including the first public demo, free preview launch, and beta launches. It then discusses the company's working philosophy of top-down development, just-in-time building, and feedback loops. Pair programming is used when possible. The document emphasizes common sense over buzzwords and having user traction, profits, and happiness over great code alone. It advocates testing assumptions through failure and success and provides tips on dry testing a product and not taking advice too literally.

Motivation, company phylosophy and how to squeeze the juiceKostetska Galyna

Vgf bglr 14_devAficionado Mac

The document discusses best practices for porting development processes to game development. It recommends focusing on story, atmosphere, characters, and unique flavor to create an epic gaming experience with rewards. Key stages include concept, pre-production, production, launch, and post-launch. Prototyping early and playtesting frequently are emphasized to incorporate feedback and iterate. Community involvement and mentorship are also suggested.

5 Tips for Great Product DesignAtlassian

The Design Graduate's ToolkitZachary Bedell

This document provides career advice for design graduates in 7 points: 1. Focus on an area of design you enjoy to stay motivated and find interesting work. 2. Look for opportunities and take them, using university resources to find openings and weighing the pros and cons of opportunities. 3. Build a strong portfolio by creating high quality, carefully designed work and presenting it well to showcase your skills to potential employers. 4. Establish patterns for continuous learning by observing others, contributing to projects, and reflecting on your learning process. 5. Show value beyond your job duties by helping coworkers, taking initiative on projects, and taking an ambitious approach in your work. 6. Have

MAKE DAY 2016 Build WorkshopCassandra Wilcox

I led a workshop recently on product development at an event in Orlando, FL called Make Day. The purpose of the event was to bring the community together to learn techniques in designing and building with a team, while working toward the common purpose of making Orlando the best city for women in tech. My workshop was one of two that day, following the Design Ideation Workshop. So, I focused primarily on the prototyping stage of product development and how to move from idea to building something you can use to test your idea with real users.

Rapid Prototyping - a good idea for Startups - battling the human conditionBBC News Labs

This presentation was prepared for a free international startup conference at Ravensbourne College, London. This is not an extensive "How To" guide for rapid prototyping, it is more a quick guide to outline why we do it, and to give a quick overview of the process. Mainly: Rapid Prototyping is a great way to battle the human condition: our natural tendencies to spend too much time perfecting an idea or product before launching it; to refine ideas FOREVER, and not test them early enough.

Collaboration is More Than Communication – JIRA Agile - Xavier MoreraAtlassian

The Psychology of Computer ProgrammingDan Stewart

The document summarizes key points from the 1971 book "The Psychology of Computer Programming" by Gerald M. Weinberg. It discusses how egoless programming increases productivity by not allowing programmers to "own" programs. It also advocates for an agile approach, noting requirements often change during development. Finally, it outlines traits of successful programmers, like adaptability and humility, and emphasizes the importance of being willing to learn from mistakes.

Lean Scaling – From Lean Startup to Lean Enterprise - Itamar GoldminzAtlassian

Design for Life: How to Survive a Career in Design (Arthur Irving)Future Insights

Taken from the Future of Web Design, London 2015 Conference. http://futureofwebdesign.com/london-2015 Whether you work at home or in a studio, your work environment and approach to work is so important. Your desk, your kit, your eating habits…they matter more than you think. Arthur will share how a decade of physical pain led him to focus on how he works as much as on his output – and the difference it made. He’ll also share how running a marathon has helped him run a studio and why, in our hectic digital lives, toasting marshmallows, climbing trees and swimming in lakes are not just fun but essential!

Go #SCRUM Yourself!Aye Know

This document discusses Scrum, including both myths and best practices. It begins by questioning whether Scrum is a "holy grail" or "holy s#!?". It then debunks the myth that Scrum means rapid development and clarifies that agility is about flexibility, not speed. The document also outlines what Scrum focuses on and provides examples of pitfalls seen in Scrum teams, such as when the Product Owner acts as a developer or the definition of done is changed at the end of a sprint. It shares tips for running effective Scrums through retrospective meetings, reasonable 'sprints, and keeping things simple. In the end, it emphasizes self-learning, agility and control, and continual improvement

How to talk to your Product OwnerLieke van der Poel

Time Management for #EventprofsAlex Vail

003 inspired training_leadership 03Abir Hossain

Effective Remote DesignJim Kalbach

Scrum in the Enterprise - Making It Work With Distributed Teams - Liz HeierAtlassian

Liz Heier discusses how to implement Scrum successfully with distributed teams across multiple locations. She emphasizes that it requires having the right process, the right people, and the right tools. For the process, she recommends estimating backlogs, identifying minimum viable products, and using burn-up charts to monitor scope. For people, key roles include the Scrum Master, Product Owner, and development team. Effective communication across all teams is also important. For tools, she suggests using project management software for documentation, collaboration, code reviews, and ensuring transparency. With the right approach in these three areas, Scrum can be implemented effectively even with remote and distributed teams.

Become Efficient or Die: The Story of BackTypenathanmarz

BackType helps businesses understand social media data through analytics tools and APIs. With a small team of 3 employees and funding of $1.4 million, they are able to process 100 million social media messages per day from over 30 terabytes of data using a 100-200 machine computing cluster. The company focuses on developing efficiently using agile and lean startup methodologies like testing hypotheses with fake features before building them out fully, avoiding overengineering, and paying down technical debt regularly through "BackSweeps".

Lean UX in an Agency EnvironmentJef Bekes

More Related Content

What's hot (20)

Garbage In, Garbage Out: Optimizing Design Inputs for Successful PrototypesKamaria Campbell

Mythical Powers Of OssIwein Fuld

Design thinking & scrum v 3.0Sebastian Schürmann

A Startup Story - Geekcamp PresentationArun Thampi

Motivation, company phylosophy and how to squeeze the juiceKostetska Galyna

Vgf bglr 14_devAficionado Mac

5 Tips for Great Product DesignAtlassian

The Design Graduate's ToolkitZachary Bedell

MAKE DAY 2016 Build WorkshopCassandra Wilcox

Rapid Prototyping - a good idea for Startups - battling the human conditionBBC News Labs

Collaboration is More Than Communication – JIRA Agile - Xavier MoreraAtlassian

The Psychology of Computer ProgrammingDan Stewart

Lean Scaling – From Lean Startup to Lean Enterprise - Itamar GoldminzAtlassian

Design for Life: How to Survive a Career in Design (Arthur Irving)Future Insights

Go #SCRUM Yourself!Aye Know

How to talk to your Product OwnerLieke van der Poel

Time Management for #EventprofsAlex Vail

003 inspired training_leadership 03Abir Hossain

Effective Remote DesignJim Kalbach

Scrum in the Enterprise - Making It Work With Distributed Teams - Liz HeierAtlassian

Garbage In, Garbage Out: Optimizing Design Inputs for Successful PrototypesKamaria Campbell

Mythical Powers Of OssIwein Fuld

Design thinking & scrum v 3.0Sebastian Schürmann

A Startup Story - Geekcamp PresentationArun Thampi

Motivation, company phylosophy and how to squeeze the juiceKostetska Galyna

Vgf bglr 14_devAficionado Mac

5 Tips for Great Product DesignAtlassian

The Design Graduate's ToolkitZachary Bedell

MAKE DAY 2016 Build WorkshopCassandra Wilcox

Rapid Prototyping - a good idea for Startups - battling the human conditionBBC News Labs

Collaboration is More Than Communication – JIRA Agile - Xavier MoreraAtlassian

The Psychology of Computer ProgrammingDan Stewart

Lean Scaling – From Lean Startup to Lean Enterprise - Itamar GoldminzAtlassian

Design for Life: How to Survive a Career in Design (Arthur Irving)Future Insights

Go #SCRUM Yourself!Aye Know

How to talk to your Product OwnerLieke van der Poel

Time Management for #EventprofsAlex Vail

003 inspired training_leadership 03Abir Hossain

Effective Remote DesignJim Kalbach

Scrum in the Enterprise - Making It Work With Distributed Teams - Liz HeierAtlassian

Similar to ModevUX AgileUX (20)

Become Efficient or Die: The Story of BackTypenathanmarz

Lean UX in an Agency EnvironmentJef Bekes

It's XP Stupid (2019)Mike Harris

We’re all doing Agile nowadays, aren’t we? We’ll all delivering software in an Agile way. But what does that mean? Does it mean sprints and stand-ups? Kanban even? But what about Extreme Programming? If as a development team we’re not using pair programming, test driven development, continuous integration, and other XP practices, then we’re not really doing Agile software development and we may be on a march to frustration, or even failure. I’m going to look at why the current trend of companies and projects adopting Scrum, calling themselves Agile, but not transitioning their development to XP, is a recipe for disaster. I’d like to cover the main practices of XP as well as other good practices that can really help a team deliver quality software, whether they’re doing two-week sprints, Kanban, or even Waterfall. https://www.youtube.com/watch?v=aZgnY9fAHOA

Agile ux fullday-uxpa2016UXPA International

In this tutorial for experienced practitioners you will learn how to manage work and make great experiences one sprint at a time. We'll look at common Agile methodologies such as Scrum and Kanban and what opportunities and risks are inherent for UX teams. We will look at team makeup, balancing longer-term research with production needs and strategies for making the most of design spikes. We'll also go through the pros and cons of a Sprint Zero and alternatives. We'll look at how Lean Startup practices are changing business development, and how your UX skills can be a key part in making that successful. Participants will come away with the tools they need to be successful in their Agile/Lean environment

It's XP, StupidMike Harris

The document outlines Mike Harris's presentation on eXtreme Programming (XP). It begins by introducing the structure of the presentation, which will explain why XP is important and outline some of its key development practices. It then provides two case studies of projects, one that was underperforming and one that appeared high performing but had similar underlying issues. The document dives into what XP is, outlining its values, principles and practices. It concludes by discussing outcomes the speaker found when applying XP practices.

People Over Process: Turning Assumptions into Shared Understandingmjovel

Every project is based on a number of assumptions. Assumptions about our users and assumptions that our team has a shared vision of what we are building and why we are building it. The longer we hold onto these assumptions, the greater we increase the risk of not meeting our users needs and ultimately, our project fails. This talk will be about how we ensure we are meeting our users needs. In addition to learning project workflow, we will cover specific techniques that you can use to ensure that the user is at the center of our design and that you create a shared understanding among your team.

More Than UsabilityRazan Sadeq

This document discusses 7 methods for conducting user research: field studies, desirability studies, surveys and polls, usability studies, remote testing, A/B testing, and researching without users. It provides an overview of when each method should be used, how to implement it, and tips/tools for each. The document emphasizes that user research is important because designers are not users, and it should be conducted at different stages of the product development process to inform, optimize, and assess the user experience.

05 DIGI CREATIVE people&processSheSaysCREATIVE

The document discusses the process of creating digital work. It covers the key players involved, including agencies, clients, strategists, digital producers, production companies, coders, and UX/UI designers. It emphasizes collaboration between these groups. The document also outlines the project process, including phases like discovery, define, design, build, and testing. Key documents in the process are mentioned like functional requirements, technical requirements, site maps, wireframes, and design comps. Tips are provided for going live with the work and managing it after launch. Various online resources for inspiration and tools are also listed.

Just UX it upKhal Weir

Extreme Programming (XP): RevistedMike Harris

In his recent book, Clean Agile, Robert C "Uncle Bob" Martin chooses Extreme Programming (XP) for the basis of his explanation of Agile because "of all the Agile processes, XP is the best defined, the most complete, and the least muddled." So why is it that in my professional life I only hear us speaking about Agile in terms of Scrum, Sprints, and possibly Kanban? Often I mention XP and people are not sure what I mean. Am I sure myself? Coined in 1999 by Kent Beck and Ward Cunningham, XP has been with us for twenty years, but may of its practices have been with us for much longer. Many of them will be familar to you, but did you know they came from XP? This talk aims to take us back to what XP is, how it fits in the Agile world, how it sits alongside other methodologies, and why, like Uncle Bob, I believe it is the best defined methodology, and what we should all be talking about. The talk is based on a heavily refactored talk that Mike gave previously at Agile on the Beach conference, updated for 2020. Given at Ox:Agile Meetup on February 11th 2020: https://www.meetup.com/OXAGILE/events/nxrdmrybcdbpb/

UX in Action: IBM WatsonUserTesting

Secrets of ScrumJames Coplien

Scrum and Patterns share a heritage that goes back centuries. The common foundations of the two — local adaptation, incremental growth, focus on "value," and the central human element — make patterns a particularly viable vehicle for rolling out Scrum. These notes give a short definitive summary of patterns (by example) and pattern languages. Next, they introduce basic Scrum patterns that the Scrum PLoP® effort has gathered over the past five years. After that we look at the "Scrum secrets" — Scrum fundamentals that most practitioners either aren't aware of or which usually go unheeded. Patterns help tease out the tradeoffs ("forces") for these forms in a way that makes them memorable. Last, we give a glimpse of how to use these patterns as a powerful way to evolve your own Scrum implementation to excellence.

UX as a Team SportShawn Pucknell

presented live at FITC's Spotlight UX event on Sept 17th, 2016 in Toronto Canada. Presenter: Maya Bruck Senior Product Designer, Etsy Brooklyn, USA More info at http://fitc.ca/presentation/ux-team-sport/ Save 10% on any FITC event with discount code 'slideshare'. Overview As a UX designer, you are the de facto champion of the people who use your product — heck, the word “user” is part of your title. And to create the best product experience for your users, you need to get everyone on your team thinking like UX designers too. Because the more people on your team who understand UX principles and empathize with the user’s needs, the more effective your product will be. And the more you understand the other disciplines you work with and bring them into your process, the smarter and faster you’ll be able to design. Objective We’ll cover collaborative techniques to involve your team (from stakeholders to developers) in the UX process, and learn how collaboration can build a culture of ownership, trust, and empathy on your team. Target Audience UI/UX designers, product designers, front-end developers Things Audience Members Will Learn Why collaboration is da bomb How to reduce the burden of documentation so you can work faster and more efficiently How to empower stakeholders and developers to make informed product decisions Techniques to better understand strategic/technical limitations and opportunities

Jeff Lopez - To Affinity and BeyondAgile Impact

Jeff Lopez - To Affinity and BeyondAgile Impact Conference

The document describes a workshop that demonstrates affinity mapping techniques for agile planning. It will show how to quickly generate, estimate, prioritize and evaluate a product backlog through affinity consensus. Attendees will learn techniques like dot voting, grouping and relative sizing. Exercises will guide participants in creating user stories, estimating effort and determining value through affinity facilitation. The goal is to reduce waste and allow for fast decision making through these visual and collaborative techniques.

StoryboardingChandan Sah

The document discusses storyboarding as a technique for presenting information in a visual, sequential manner. Key points include: 1) Storyboards can be used to identify players, events, and how events unfold in a simple, visual format. 2) They act as a blueprint showing individual elements and their sequence to effectively communicate a topic. 3) When used interactively, storyboards can facilitate in-depth discussion between presenters and audiences.

UX, Agile and product managementPhil Barrett

This document discusses user experience (UX), agile product management, and delivering software that meets user needs. It advocates for an iterative development process that incorporates UX research and testing. Product managers are advised to work closely with UX designers to validate assumptions through usability testing, measure outcomes, and prioritize addressing UX issues. An agile, lean approach that rapidly builds and learns from user feedback is presented as the best way to deliver innovative products that customers want and provide a competitive advantage.

User Experience Design: 5 Techniques for Creating Better Websites and Applica...nForm User Experience

The document discusses five techniques for improving user experience in website and application design: 1. Design early by incorporating user experience design into requirements gathering to better understand user needs. 2. Test early and often through prototyping, usability testing, and engaging users to iterate on designs before development is complete. 3. Make prototypes like sketches, flows, and mockups to generate ideas, get stakeholder buy-in, and test designs at low cost before implementing. 4. Focus on user behavior by asking open-ended questions about what users actually do rather than what they say they want. 5. Make "good mistakes" through exploratory prototyping to learn about problems and

Customer Development Fast ProtypingSerdar Temiz

- The document discusses various business development processes including subtraction, multiplication, division, task unification, and attribute dependency change as ways to modify a product. It then discusses prototyping and getting customer feedback as important parts of the development process. Specifically, it recommends creating minimum viable products and landing pages to test assumptions with customers before fully developing ideas. The key messages are that business plans should evolve based on customer feedback, prototyping allows early testing of ideas, and pivoting a business model based on learning is normal.

Intellectual Property Rights, encompassing legal protections for creations of...RINUSATHYAN

Become Efficient or Die: The Story of BackTypenathanmarz

Lean UX in an Agency EnvironmentJef Bekes

It's XP Stupid (2019)Mike Harris

Agile ux fullday-uxpa2016UXPA International

It's XP, StupidMike Harris

People Over Process: Turning Assumptions into Shared Understandingmjovel

More Than UsabilityRazan Sadeq

05 DIGI CREATIVE people&processSheSaysCREATIVE

Just UX it upKhal Weir

Extreme Programming (XP): RevistedMike Harris

UX in Action: IBM WatsonUserTesting

Secrets of ScrumJames Coplien

UX as a Team SportShawn Pucknell

Jeff Lopez - To Affinity and BeyondAgile Impact

Jeff Lopez - To Affinity and BeyondAgile Impact Conference

StoryboardingChandan Sah

UX, Agile and product managementPhil Barrett

User Experience Design: 5 Techniques for Creating Better Websites and Applica...nForm User Experience

Customer Development Fast ProtypingSerdar Temiz

Intellectual Property Rights, encompassing legal protections for creations of...RINUSATHYAN

Recently uploaded (20)

masterddedeeeeeeeeedded seminar (1).pptxtgavel7869

Baby panda 400.pdf de ciencias naturalesdebbie loaiza

Minimalist Business Slides XL by Slidesgo.pptxkarenalavamoran

COTTER and KNUCKleeeeeeeeeeeeeeeeeee.pptxayushjadon04

Minimalist Pitch Deck by slide Slidesgo.pptxESTEFANOANDREYGARCIA

Presentation mockup using lots of animalsChunChihChenPhD

dFdDVWeb_Design_Basics_Presentation.pptxAKSHAYKAMBLE806728

Lori Vanzant's portfolio. Please take a look!vanzan01

Download Chimera Tool Setup V42.47.0924 [Latest Version]Designer

Steam-Education-PowerPoint-Templates.pptxandripapa1

Halstead’s_Software_Science_&_Putnam’s_Model[1].pptxprachiikumarii1

PayPros-Journey-Overcoming-Challenges-Through-Governance.pptxrayyansiddiqui034

Designing Interactive and Engaging Museum ExhibitsPeach Prime Consultancy

Museums today are moving away from just showing objects to creating fun, hands-on experiences where visitors can touch, play, and learn. They design exhibits based on who will visit, use stories to make people feel connected, and add technology like virtual reality to make things even more exciting. Museums also make sure everyone, including people with disabilities, can enjoy the exhibits. They use games, teamwork, and regular feedback to keep improving, so visiting a museum becomes a fun and memorable adventure for everyone. Visit our website for more info.:https://www.peachprime.in/services/museum-exhibit-design/

EEE178-PPT-Theme iasodhajsdkjashdlaskdjbaksdkashdlkasdlkja;dj;kdada.pptx.pdfCastroAngeloReoD

2nd taxonomy, nomen microorganisms-.pptxayeleasefa2

19 Best B,u,y Verified Cash App Accountshttps://sellsusa.com/product/buy-verified-cash-app-accounts/

Take this ppt refference and give content on mahindra commitment to sustainab...kochars428

PPT UNTUK ISU STRATEGIS (1).pptx PPT UNTUK ISU STRATEGIS (1).pptxrachmatunnisa29

mid-term all revisions g11 s1.pmdzs,zxptxomar164646

Lori Vanzant Portfolio. Please take a look !vanzan01

masterddedeeeeeeeeedded seminar (1).pptxtgavel7869

Baby panda 400.pdf de ciencias naturalesdebbie loaiza

Minimalist Business Slides XL by Slidesgo.pptxkarenalavamoran

COTTER and KNUCKleeeeeeeeeeeeeeeeeee.pptxayushjadon04

Minimalist Pitch Deck by slide Slidesgo.pptxESTEFANOANDREYGARCIA

Presentation mockup using lots of animalsChunChihChenPhD

dFdDVWeb_Design_Basics_Presentation.pptxAKSHAYKAMBLE806728

Lori Vanzant's portfolio. Please take a look!vanzan01

Download Chimera Tool Setup V42.47.0924 [Latest Version]Designer

Steam-Education-PowerPoint-Templates.pptxandripapa1

Halstead’s_Software_Science_&_Putnam’s_Model[1].pptxprachiikumarii1

PayPros-Journey-Overcoming-Challenges-Through-Governance.pptxrayyansiddiqui034

Designing Interactive and Engaging Museum ExhibitsPeach Prime Consultancy

EEE178-PPT-Theme iasodhajsdkjashdlaskdjbaksdkashdlkasdlkja;dj;kdada.pptx.pdfCastroAngeloReoD

2nd taxonomy, nomen microorganisms-.pptxayeleasefa2

19 Best B,u,y Verified Cash App Accountshttps://sellsusa.com/product/buy-verified-cash-app-accounts/

Take this ppt refference and give content on mahindra commitment to sustainab...kochars428

PPT UNTUK ISU STRATEGIS (1).pptx PPT UNTUK ISU STRATEGIS (1).pptxrachmatunnisa29

mid-term all revisions g11 s1.pmdzs,zxptxomar164646

Lori Vanzant Portfolio. Please take a look !vanzan01

ModevUX AgileUX

1. AGILE UX

2. MICHAEL JOVEL • UI Developer at startapps • My mother tells people I am an international lawyer •Istopped correcting her because it is easier twitter: @mjovel • Worked with US Navy, email: [email protected] Progressive, University of Chicago & University of MD

3. HISTORICALLY DESIGN HAS BEEN BASED ON THE WATERFALL METHOD

4. CREATIVE BRIEF > DESIGN > APPROVAL > PRINTER > DELIVERY

5. http://uxmag.com/articles/change-on-a-dime-agile-design

6. THAT IS NOT WHAT THEY WANTED

7. http://uxmag.com/articles/change-on-a-dime-agile-design

8. DON’T GET CAUGHT UP ON PROCESS

9. VALUE NOT REQUIREMENTS

10. “Eric Reis 4 thstate of agile: A story does not end at acceptance but rather must be validated for value

11. WORK IS MEANINGLESS UNLESS YOU CREATE VALUE

12. LIVE AND BREATHE RESULTS

13. FROM HYPOTHESIS TO REQUIREMENTS

14. HYPOTHESIS • a tentative assumption made in order to draw out and test its logical or empirical consequences - merriam-webster

15. WHY HYPOTHESIS? • Rather than make assertions it puts forth a questions which must be then validated • Engages team creativity

16. WHAT ASSUMPTIONS DO YOU HAVE THAT IF PROVEN FALSE WILL CAUSE YOUR SOLUTION TO FAIL?

17. WE BELIEVE ___________ AND IF THIS IS TRUE WE SHOULD SEE __________

18. COLLABORATION

19. DESIGN STUDIO

20. DESIGN STUDIO • Butcherpaper, painters tape, sharpies and stop watch, grid template sheets • Build small 3-4 person teams composed of designer, developers and business team. • Give each team a persona to focus on

21. SKETCH •5 minutes to create 6-8 sketches individually

22. PITCH •3 Minutes to pitch to group

23. CRITIQUE • two ways it accomplished goals • two ways it failed to accomplish goals

24. TEAM SKETCHING •5 minutes to iterate on best of individual sketches

25. TEAM PITCH •3 minute pitch to entire group

26. TOO MANY SECRETS

27. PROMOTE TRANSPARENCY

28. PROMOTE CODE LITERACY

29. CODE LITERACY IS NOT CODE FLUENCY

30. PAIR DESIGNING • Make sure designers and developers spend time working together • saves time on implementation • promotes ownership

31. PATTERN LIBRARY • Library of UI Patterns that developers can use (i.e. buttons, ﬁelds, etc. • Library of UI Components composed of multiple patterns (i.e. forms, video player, etc.)

32. VALIDATION

33. WHAT IS THE SMALLEST AMOUNT OF WORK WE CAN DO TO VALIDATE OUR CONCEPT?

34. GET IT IN USERS HANDS!

35. PROTOTYPE • Paper • Keynote / Powerpoint • Axure, iRise, etc. • Cordova (a.k.a Phonegap)

36. ITERATE

Editor's Notes

#2: \n
#3: \n
#4: \n
#5: \n
#6: \n
#7: \n
#8: \n
#9: \n
#10: \n
#11: \n
#12: \n
#13: \n
#14: \n
#15: \n
#16: \n
#17: \n
#18: \n
#19: \n
#20: \n
#21: \n
#22: \n
#23: \n
#24: \n
#25: \n
#26: \n
#27: \n
#28: \n
#29: \n
#30: \n
#31: \n
#32: \n
#33: \n
#34: \n
#35: \n
#36: \n
#37: \n

ModevUX AgileUX

Recommended

More Related Content

What's hot (20)

Similar to ModevUX AgileUX (20)

Recently uploaded (20)

ModevUX AgileUX

Editor's Notes