Product Design with Intent-Final

•

0 likes•184 views

This document discusses different approaches to integrating product design into an agile software development process. It presents 5 options: 1) designing up front before development starts, 2) designing at the beginning of each sprint, 3) designing two sprints ahead of development, 4) having dedicated design sprints that alternate with development sprints, and 5) having designers partner directly with developer teams. The document recommends that the best approach is a hybrid that includes doing some initial design up front, having designers partner with developers, and replacing the product owner role with a product designer role to ensure design quality throughout the process. It emphasizes that good product design is important to transform a product from just a bag of features into a unique experience for users.

Here’s
Your
Team
George Lange NBC/NBCU Photo Bank via Getty Images synth bass line. [Photograph]. Retrieved from http://www.gettyimages.com/detail/news-photo/season-6-pictured-michael-richards-as-
cosmo-kramer-julia-news-photo/138432011?license

Powerful
Person
Request
Problem
Photographee.eu / Shutterstock.com.

Slowly
Veer off
Course
Problem
Photo credit: Unknown

Everything
is High
Priority
Problem
Taiga / Shutterstock.com.

Every Person
is Building a
Different
Product
Fact

Strong
Center
Design
Blend all parts of a
software product to
make a single
impression.
Requirement

Graphic
Designers
Use Gestalt
Principles

Strong
Center
Design for
Invisible
Parts
Microexpression
- Upper lid is raised
- Lower lip is raised
- Nose is wrinkled
- Cheeks are raised
- Lines show below the lower lid
Science of People. Retrieved from http://www.scienceofpeople.com/2013/09/guide-reading-microexpressions/

North Star
WHY this product?
[What is most meaningful to people]

NorthStar
Example
Real time traffic intelligence
But has to have basic navigation.

Strong
Center
Guides
Decision
Does this enhance the
product meaning or get in the
way of the product meaning?
^

Strong
Center
Example
Spend time on this?
The cheapest gas station on my route.
Reduce battery usage for passive data
collection.
Restaurants nearby.
Walking directions.
Out
Out
Out
IN

Strong
Center
Design +
Agile
Five options to consider

Option 1
Design up
front
Insert dedicated design sprint zero
[ Has same pitfalls as waterfall ]
Sprint 0
Sprint 1
Sprint 2
Sprint 3

Option 2
Design in
each sprint
A little design at the beginning of every sprint
[ Delays development ]
[ Either design or software development productivity suffers ]
Sprint 1
Sprint 2
Sprint 3
Sprint 4

Design two
sprints ahead
Two separate workflows in each sprint
[ Design first makes the process less agile ]
[ Design team has to support different sprints ]
Sprint 1
Sprint 2
Sprint 3
Sprint 4
Option 3

Option 4
Dedicated
design
sprints
Sprints oscillate between design & development
[ Developers may not have skills for design sprints]
[ Designers may not have skills for development sprints]
Sprint 1
Sprint 2
Sprint 3
Sprint 4

Option 5
Designer &
developer
partnership
Pair a designer with a couple developers
[ Hard to achieve wholeness in the design ]
[ Difficult with distributed team ]
Sprint 1
Sprint 2
Sprint 3
Sprint 4

Lesson 1
North Star before
green light
NL shop / ClipartOf.

Lesson 2
Hybrid approach works best
A little design up front
Designer partnership with developer
+

Lesson 3
Product Designer
replaces Product
Owner

Our
Philosophy
Product design matters
It transforms a product

Theresa Smith
SphereOI Sphere_OITSmith@SphereOI.com

The document discusses the goals and learnings from a design system mission to enable teams to create straightforward user experiences. It notes that the tension between product and design system goals is healthy. Key learnings include looking at existing products, synthesizing information to move forward, focusing on experiences rather than just components, and building the design system like a product. The document also outlines different models for how a design system can be built and aligned with product roadmaps.

UXPin: State of the Union Product Keynote by Marcin Treder

uxpin

#noprojects: Live happily ever after without projects

Dimitri Favre

This document discusses the concept of #noprojects, which advocates switching from a project mindset to a product mindset when developing software. It presents #noprojects as a deliberate act of continuous product management. The document outlines #noprojects in 4 stages: 1) experiments over projects, 2) stable teams over temporary endeavors, 3) products over software, and 4) outcomes over execution. It also provides 10 principles for guiding a #noprojects approach, such as funding capacity not scope, bringing work to stable teams, and ensuring roadmaps are driven by needs not features. The overall message is that organizations should stop viewing software development as projects and instead focus on continuous product management and development.

Agile game development with Scrum

Damir Matas

Agile development values working software over documentation and responding to change over strict plans. This allows game development to focus on iteratively finding the fun through prototypes and user feedback. An agile game project consists of short iterations where cross-functional teams implement user stories to build knowledge and steer the project towards more valuable goals. Scrum defines roles like Product Owner to prioritize features and Scrum Master to remove impediments and ensure the team follows agile practices.

#Noprojects @Agile Venture Prato 2018

Dimitri Favre

La quasi totalità degli sviluppi software è basata su un approccio per progetto. Un progetto, per definizione, è qualcosa di effimero. Ha un inizio, e soprattutto una fine, qualcosa di temporaneo. Il software non è temporaneo. Un software sopravvive fino a quando esiste almeno una persona che lo utilizza. A volte sopravvive anche più a lungo. Perché continuiamo ad usare qualcosa di effimero per gestire qualcosa che effimero non è? Quali alternative abbiamo? Possiamo fare veramente a meno dei progetti?

Case study for agile software development:

Joe Crespo

Lean development based on scrum

Peter Horsten

Realizing a solution is no longer enough Imagine yourself a clever software developer, sitting in his room, working deep at night. For weeks, months, he's breeding on that one perfect solution. He codes like crazy, refactors, rebuilds. He wants it to be perfect. May be he showed it to some of his friends and they told him they like the idea. After a lot of hard work the solution is finally ready. Excited and full of expectations he introduces it to the market. Soon, all his effort will pay off, money will start flowing. Unfortunately, nobody seems to be interested in using the product and for sure they don't want to pay for it. What went wrong? How to prevent? During the lecture we will discuss how to cut this big salami into small pieces by using a lean development approach based on Scrum.

The document discusses lessons learned from implementing lean and agile approaches in three different products or organizations: Microsoft Windows CE.Net Platform Builder, Adobe Revel, and Spotify. For each product, both positive and negative lessons are outlined, such as isolating the effort as an experiment and being careful of early success for Windows, and balancing autonomy and collaboration for Spotify.

Dual Track Agile Or, How I learned to stop worrying and love the scrum

UXDXConf

In software there are two key types of work - discovery and delivery. However, that doesn't mean there are different people doing those jobs. If the whole team is responsible for product success, not just getting things built, then the whole team needs to understand and contribute to both kinds of work. Dual track agile and the UXDX model both convey the approach of design and development working together.

Scaling Products With Design Systems

uxpin

Being a Little Agile

Daniel Blair

The document discusses Agile Scrum methodology and how it was used to develop PanoPla, a virtual reality tool. It describes the Scrum process which involves daily stand-ups, bi-weekly deliverables, and retrospectives. A team including students and a Scrum Master from Bit Space Development iteratively built PanoPla over several months, gaining early feedback from users. The result was an open beta version of PanoPla with over 5,000 users in just 4 months.

From 6 to 126 in 4 Years: The Story Behind Atlassian Design

uxpin

Agile Development Models

DeepaThirumurugan

The document discusses agile development models as an alternative to traditional waterfall models. It describes how agile models use iterative development with short cycles to facilitate adapting quickly to changing requirements. Several specific agile methods are listed such as Scrum, Extreme Programming, and Lean Development. The key principles of agile development are close customer collaboration, preference for working software over documentation, frequent delivery of software increments, and ability to accommodate changing requirements.

Agile Design in Practice

Kmanthei

This document discusses agile design and how it differs from traditional design processes. Agile design engages users early and often through prototyping to get fast, rapid feedback. It presents a framework with two parts: 1) creating initial concepts through research, ideas, and user testing and 2) short cycles of design, testing, and building. Benefits include the ability to respond to change, continuous feedback, and implementing a design true to the original concept. The key is engaging in just enough design and research to begin development in short, iterative cycles with cross-functional teams.

Walk, Don't Run: Incremental Change in Enterprise UX

uxpin

Streamlining of an organization - Scrum with multiple teams (SEACON 2013)

Sven Röpstorff

From an Idea to a Product

Sergey Sundukovskiy

Are you ready to build an MVP? Where do you start? How do you know what features to build? How do you know how many people you need to build it? How do you know that they are building a right thing in a right way? This presentation and conversation will explore strategies for assembling effective teams for building and deploying an MVP while incurring minimal Product and Technical Debt. We will also discuss implementing an effective process to make sure that your MVP will be built on time and on target.

Great Agile in a UX World

Anthony Viviano

Scrum

Balaji Sathram

Scrum is an agile framework for managing product development. It defines three roles - Scrum Master, Product Owner, and Development Team - and three artifacts - Product Backlog, Sprint Backlog, and Product Increment. It also includes five ceremonies - Product Backlog Refinement, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective. Scrum was first defined in 1986 and evolved through the 1990s, with Ken Schwaber and Jeff Sutherland formalizing the method in 2001 in their book Agile Software Development with Scrum.

UX @ agile - myths, legends and the path to success

Ran Liron

This document discusses integrating UX practices into Agile development. It addresses three common misconceptions: 1) that Agile projects don't require planning ahead, 2) that Agile doesn't allow time for research and validation, and 3) that Agile means less mistakes. It provides four tips: 1) ensure UX is part of the MVP, 2) define clear requirements for each design task, and 3) focus on effective communication within cross-functional teams. Overall, the document advocates frontloading research in Sprint 0 and design spikes, allowing the UX team to work one sprint ahead of developers to plan effectively in Agile.

Breaking Barriers with Empathy (Ross Smith at Enterprise UX 2017)

Rosenfeld Media

Incremental Design

Russ Wilson

The document discusses challenges with designing enterprise applications and proposes an incremental approach. The key challenges are that everyone feels like a designer, it's difficult to make final decisions, and justifying designs to critics. The traditional design process does not work for most enterprise apps because they are already in development before a designer is involved, it's too costly to start over, and there is pressure to deliver value fast. The document proposes an incremental approach that focuses on continuously delivering value quickly while providing a foundation to evolve the product over multiple levels of design and development.

Design Thinking in an Agile process: why, how, what's the impact on business

Ilaria Mauric

Queste sono le slide del talk che ho presentato sabato 17 settembre 2016 all'Università Ca' Foscari di Venezia in occasione dell'Agile Business Day 2016. Design Thinking aggiunge cuore e cervello in un processo agile, aumentandone valore ed efficacia. Vedremo le sue fasi fondamentali, accompagnate dai suoi principi guida e spiegate con esempi reali. Come si può innovare un prodotto? Che problema risolve di preciso? Rispondere a queste domande a colpi di brief, roadmap, requisiti, budget e processo non basta più, perché le soluzioni sono prestabilite su assunzioni, tendono a gonfiarsi di funzionalità o a omologarsi nei vincoli. Il processo di Design Thinking aiuta ad affrontare i problemi con la mente aperta, ad esplorare opzioni guardandole da più punti di vista e a superarli con un approccio creativo, proiettato verso il futuro. Il ruolo del designer non è più solo quello di rendere usabile, funzionale e visivamente adeguato il prodotto, ma è anche quello di facilitare la collaborazione cross-team e l’esplorazione di soluzioni, presentando concetti e idee in modo tangibile e comprensibile da tutti le persone coinvolte nella sua realizzazione.

Year 11 DT product design final products 2011

vickismithfis

Collaborative Interactive Class Portfolio interim presentation

Karen Kiely

The document outlines a final year project proposal to create a collaborative interactive class portfolio. It will involve specifying requirements, creating interaction scenarios, and developing a prototype. Students will be able to create and store work on personal devices and share it on networked displays. The project aims to combine working on group projects with technology. It reviews relevant literature on eportfolio systems and collaborative learning. A timeline is provided outlining the research, design, and development process over the course of the academic year.

What's hot

Three's a Party: How Trifectas Help Product, Engineering, and Design Work Tog...

uxpin

Inspecting and adapting your product

Carlo Kruger

Building Lean

Kevin Goldsmith

Agile UX

Rob Keefer

Building Lean and Agile in the Real World

Kevin Goldsmith

Dual Track Agile Or, How I learned to stop worrying and love the scrum

UXDXConf

Scaling Products With Design Systems

uxpin

Being a Little Agile

Daniel Blair

From 6 to 126 in 4 Years: The Story Behind Atlassian Design

uxpin

Agile Development Models

DeepaThirumurugan

Agile Design in Practice

Kmanthei

Walk, Don't Run: Incremental Change in Enterprise UX

uxpin

Streamlining of an organization - Scrum with multiple teams (SEACON 2013)

Sven Röpstorff

From an Idea to a Product

Sergey Sundukovskiy

Great Agile in a UX World

Anthony Viviano

Scrum

Balaji Sathram

UX @ agile - myths, legends and the path to success

Ran Liron

Breaking Barriers with Empathy (Ross Smith at Enterprise UX 2017)

Rosenfeld Media

Incremental Design

Russ Wilson

Design Thinking in an Agile process: why, how, what's the impact on business

Ilaria Mauric

What's hot (20)

Three's a Party: How Trifectas Help Product, Engineering, and Design Work Tog...

Inspecting and adapting your product

Building Lean

Agile UX

Building Lean and Agile in the Real World

Dual Track Agile Or, How I learned to stop worrying and love the scrum

Scaling Products With Design Systems

Being a Little Agile

From 6 to 126 in 4 Years: The Story Behind Atlassian Design

Agile Development Models

Agile Design in Practice

Walk, Don't Run: Incremental Change in Enterprise UX

Streamlining of an organization - Scrum with multiple teams (SEACON 2013)

From an Idea to a Product

Great Agile in a UX World

Scrum

UX @ agile - myths, legends and the path to success

Breaking Barriers with Empathy (Ross Smith at Enterprise UX 2017)

Incremental Design

Design Thinking in an Agile process: why, how, what's the impact on business

Viewers also liked

Year 11 DT product design final products 2011

vickismithfis

Collaborative Interactive Class Portfolio interim presentation

Karen Kiely

B City Collective social media case study

Karen Kiely

Here are the key points I gathered from summarizing the document: - Karen Kiely was hired as the online communications coordinator for B City Collective, a group of independent Birmingham artists releasing a charity single. - Her initial tasks included setting up social media profiles and a blog/website for the Collective, as the organizers lacked these skills. - She took a behind-the-scenes, authentic approach by sharing photos and live updates from rehearsals and events on Facebook, Twitter, and the blog. - As the release date approached, she implemented a creative Facebook campaign to engage more fans and increase interactions on their page. - Through her social media management and blogging, she helped promote the

3T Design & Technology

damaisec

The syllabus aims to develop pupils' creativity, innovation, design skills, and safe working habits. It focuses on fostering enterprise through design-and-make activities that involve research, idea development, and working with materials and tools. Pupils will exercise technical and aesthetic judgements to create viable solutions within timeframes, while developing an awareness of social and environmental design considerations. The examination consists of a paper assessing knowledge of design and technology areas, and a design project where pupils identify a design opportunity based on a given theme, document their process in a design journal, and present final presentation boards and an artifact.

Final Presentation: Mobile Augmented Reality for Spatial Navigation

sharB

Mobile Video Augmented Reality For Spatial Navigation: Interim Presentation

sharB

CIID Final project report

eilidh dickson

Eilidh is an interaction designer who recently graduated from the Copenhagen Institute of Interaction Design's pilot year program. For her final project, she is investigating how personal informatics tools can help people achieve balance in their lives by making them more aware of their lifestyle habits and enabling behavior changes. She is interested in whether tracking intangible information about daily actions can trigger changes and help people identify areas of fulfillment. Some existing personal informatics tools she has researched include Nike+ for running, Wattson for energy usage, Google Power Meter, Last.fm for music listening, and Dopplr for travel tracking.

Viewers also liked (7)

Year 11 DT product design final products 2011

Collaborative Interactive Class Portfolio interim presentation

B City Collective social media case study

3T Design & Technology

Final Presentation: Mobile Augmented Reality for Spatial Navigation

Mobile Video Augmented Reality For Spatial Navigation: Interim Presentation

CIID Final project report

Similar to Product Design with Intent-Final

Agile and Design: creating and implementing products (in Italy) is possible

Ilaria Mauric

The wiseman says: "A company specialized in IT consultancy cannot make products." If you decide to break this taboo, the road is only one: understanding how that product can be realized and working hard to make it. This is the story of Indyco, a tool born merging an agile dev team and a lean design team. Teams that didn't know each other before. And they made Indyco real in 6 months. We will share the simple but powerful principles that lead us up to the go-live. Now we are measuring and collecting data for next step. These slides have been presented at Better Software 2014.

Agile and Design: creating and implementing products (in Italy) is possible

Manuel Spezzani

This document discusses agile product development and design processes for startups. It outlines a methodology using scrum, minimum viable products (MVPs), and frequent user testing. A design sprint process is proposed involving analysis, sketching, prototyping, and fixing iterations. Close collaboration between designers and developers is emphasized to iteratively design, develop, and test the MVP within budget and timeline constraints. The goal is to rapidly iterate the product to address user needs and collect strategic data to guide further development.

PCC2 - How do I incorporate Apple-like design into my products?

ProductCamp Chicago

The document discusses how to incorporate Apple-like design principles into products through an agile process called inception. It recommends conducting inception workshops to understand user needs, define personas, map tasks and stories, and create high-level designs in a collaborative and time-boxed manner. The goal is to focus on desirability and get feedback early without large upfront designs, in order to develop products that are simple, useful and delightful for users.

How to Plan for Hyper Growth Success by Slack Software Engineer

Product School

The document summarizes a presentation given by a Slack software engineer on how to plan for success during periods of hyper growth. It discusses common challenges startups face like rapid scaling, communication issues, and lack of experience. It provides a case study of challenges Slack faced with an MDM project and lessons learned. The key messages are to provide strong leadership through documentation like a living product specification, use concise user stories, and over-organize to avoid issues as a company scales rapidly.

Why Can't We All Just Get Along? Improving Designer/Developer Collaboration

Allison Corbett

This document discusses improving collaboration between designers and developers on agile teams. It begins by debunking common myths that designers and developers have about each other. It then provides tips for improving the collaboration process, such as getting design work done before development starts and using tools like sketching, paper prototypes, and wireframes. The document concludes with tips for designers, developers, product owners, and scrum masters to foster collaboration, such as involving all roles in requirements gathering, providing constructive feedback, and maintaining respect.

Agile SharePoint Development With Scrum

Andrew Woodward

Provide an introduction to Agile development using Scrum and discuss how the iterative approach to development helps the customer to get the solution they want. Look at how this approach works when applied to SharePoint projects, how it helps leverage more of the core platform and focuses effort on the biggest value areas. We will look at the challenges this brings to your development team by doing early integration, dealing with upgrades and changes and understand how addressing the hard things early is the right approach. We will also discuss how Scrum gives visibility of the project and brings both good and bad news. How getting customer engagement is the primary challenge and how the flexible approach is often at odds with the way work is contracted.

The Agile PMP - Pillar Technology

Mike Cottmeyer

The document discusses how Agile project management differs from traditional project management. It explains that Agile uses iterative planning with short timeboxes, focuses on delivering working software frequently in small batches, emphasizes individuals/interactions over processes/tools, and values customer collaboration over contract negotiation. The document outlines how Agile manages scope, time, costs, risks, and other factors using techniques like user stories, burndown charts, and frequent inspection and adaptation. It encourages the reader to start implementing Agile practices like iterative planning and daily stand-ups.

PMI CH AMM2023 - Bye Bye Project Manager - SwissQ.pptx

Christoph Wolf

Agile Planning: pragmatic approach

Askhat Urazbaev

Agile planning approaches include code & fix, waterfall, and agile. Agile practices like cross-functionality, planning poker, daily scrums, and task boards can help foster teamwork. Case studies describe how agile was applied in an in-house development team, product development company, and support team. Adopting agile principles through rituals rather than just slogans can help teams work better together to meet goals.

Agile, not just for software

John Paz

This document provides an overview of Agile and Scrum frameworks. It begins with introductions and then discusses what Agile is, comparing it to the traditional Waterfall model. Key aspects of Scrum like roles, meetings, events and artifacts are explained. The document argues that Agile is not just for software teams and discusses how Atlassian uses Agile to promote innovation through a culture that provides employees freedom, time, collaboration, funding and experimentation.

Agile – The New Kid in the Block?

Michael Tarnowski

Beyond agile - Pitfalls & misconceptions when working with SCRUM & Co | Ralf ...

Ralf C. Adam

Agile Experience In Complex Projects

Borys Lebeda

The document discusses several challenges for implementing agile practices in complex projects. It emphasizes the importance of having the right product owner and manager who understand agile principles and can help organize cross-functional teams. Establishing a knowledge base and continuous integration are also highlighted as important for facilitating collaboration across distributed teams working on evolving products.

Andrew Lukianenko: Role of Project Manager in tech startups (UA)

Lviv Startup Club

What it Really Means to Be Agile

Kent McDonald

Some teams think they can be agile by using a defined process or set of practices as defined by one of the agile approaches. This is just “doing Agile.” Other teams are agile in name only – the team says it’s “doing Agile” but ends up using the same old practices and achieving the same results. Teams adopt agile for a variety of reasons, but it’s not the process or set of practices they select that produces the results they seek. Teams are most successful when they adopt a particular mindset in order to “be agile”. Join Kent McDonald as he describes this mindset through 7 key ideas based on how people and organizations work best. We’ll discuss some specific techniques you can use to adopt the mindset on your project, how the project manager role changes along with the mindset, and how to help your team move from “doing Agile” to actually “being agile”.

Scrum Framework in Agile

Wipro

This document provides an overview of Scrum and its key concepts. It defines the waterfall and agile models of software development. Scrum is described as an agile method that uses cross-functional teams, product backlogs, sprints, daily stand-ups, and sprint reviews. Key Scrum roles like the Product Owner and Scrum Master are explained. The document also discusses estimating techniques, burndown charts, and how Scrum compares to other agile frameworks.

Google: Rapid Prototyping for AR

AugmentedWorldExpo

A talk from the Creator Track at AWE USA 2019 - the World's #1 XR Conference & Expo in Santa Clara, California May 29-31, 2019. Google: Rapid Prototyping for AR Austin McCasland | Google Diane Wang | Google With many unknowns and opportunities in AR, rapid prototyping has been critical to understand and define what makes immersive experiences valuable and usable. This talk will take a peek into how we approach rapidly designing and building prototypes for AR applications. https://awexr.com

Just Married: User Centered Design and Agile

Memi Beltrame

User Centred Design (UCD) and Agile Development are two of the most exciting and productive Methods to achieve high quality appication both desired by the customers and loved by the users. UCD and Agile Development are though often said to be impossible to combine and that despite their great advantages any attempt would most certainly lead to disaster. This talk picks up the main points of both methods, shows the key issues and tries to offer a pragmatic approach on how to successfully combine User Centered Design and Agile Development.

Introduction to agile and scrum

Anat (Alon) Salhov

1. The document provides an overview of practical scrum concepts including lean thinking, agile principles, scrum roles and ceremonies. 2. It discusses the roles of the product owner, scrum master and team in scrum and describes the four main scrum ceremonies: sprint planning, daily scrum, sprint review, and retrospective. 3. Key aspects of each ceremony are outlined such as their purpose, participants, and goals to continuously deliver working software and improve the process.

What can DesignOps do for you? by Carol Smith at TLMUX in Montreal

Carol Smith

You have probably seen the terms DesignOps and/or ResearchOps float by in your social media queue. These teams make designing (and researching) at scale beautifully efficient and successful. Carol steps through how these teams work, the types of activities they perform, situations they are helpful for, and ways you can leverage these types of programs in your organization. Carol will share examples from her experiences and stories from other organizations that are using Design Ops to do effective design at scale. Presented at Tout le monde UX in Montreal, Quebec, Canada on February 28, 2019. http://toutlemonde-ux.com/

Similar to Product Design with Intent-Final (20)

Agile and Design: creating and implementing products (in Italy) is possible

PCC2 - How do I incorporate Apple-like design into my products?

How to Plan for Hyper Growth Success by Slack Software Engineer

Why Can't We All Just Get Along? Improving Designer/Developer Collaboration

Agile SharePoint Development With Scrum

The Agile PMP - Pillar Technology

PMI CH AMM2023 - Bye Bye Project Manager - SwissQ.pptx

Agile Planning: pragmatic approach

Agile, not just for software

Agile – The New Kid in the Block?

Beyond agile - Pitfalls & misconceptions when working with SCRUM & Co | Ralf ...

Agile Experience In Complex Projects

Andrew Lukianenko: Role of Project Manager in tech startups (UA)

What it Really Means to Be Agile

Scrum Framework in Agile

Google: Rapid Prototyping for AR

Just Married: User Centered Design and Agile

Introduction to agile and scrum

What can DesignOps do for you? by Carol Smith at TLMUX in Montreal

Product Design with Intent-Final

1. Product Design Agile Project in an

2. Here’s Your Team George Lange NBC/NBCU Photo Bank via Getty Images synth bass line. [Photograph]. Retrieved from http://www.gettyimages.com/detail/news-photo/season-6-pictured-michael-richards-as- cosmo-kramer-julia-news-photo/138432011?license

3. Powerful Person Request Problem Photographee.eu / Shutterstock.com.

4. Slowly Veer off Course Problem Photo credit: Unknown

5. Everything is High Priority Problem Taiga / Shutterstock.com.

6. Every Person is Building a Different Product Fact

7. Do one thing well^

8. Strong Center Design Blend all parts of a software product to make a single impression. Requirement

9. Mish Mash

10. Graphic Designers Use Gestalt Principles

11. Strong Center Design for Invisible Parts Microexpression - Upper lid is raised - Lower lip is raised - Nose is wrinkled - Cheeks are raised - Lines show below the lower lid Science of People. Retrieved from http://www.scienceofpeople.com/2013/09/guide-reading-microexpressions/

12. North Star WHY this product? [What is most meaningful to people]

13. NorthStar Example Real time traffic intelligence But has to have basic navigation.

14. Strong Center Guides Decision Does this enhance the product meaning or get in the way of the product meaning? ^

15. Strong Center Example Spend time on this? The cheapest gas station on my route. Reduce battery usage for passive data collection. Restaurants nearby. Walking directions. Out Out Out IN

16. Strong Center Design + Agile Five options to consider

17. Option 1 Design up front Insert dedicated design sprint zero [ Has same pitfalls as waterfall ] Sprint 0 Sprint 1 Sprint 2 Sprint 3

18. Option 2 Design in each sprint A little design at the beginning of every sprint [ Delays development ] [ Either design or software development productivity suffers ] Sprint 1 Sprint 2 Sprint 3 Sprint 4

19. Design two sprints ahead Two separate workflows in each sprint [ Design first makes the process less agile ] [ Design team has to support different sprints ] Sprint 1 Sprint 2 Sprint 3 Sprint 4 Option 3

20. Option 4 Dedicated design sprints Sprints oscillate between design & development [ Developers may not have skills for design sprints] [ Designers may not have skills for development sprints] Sprint 1 Sprint 2 Sprint 3 Sprint 4

21. Option 5 Designer & developer partnership Pair a designer with a couple developers [ Hard to achieve wholeness in the design ] [ Difficult with distributed team ] Sprint 1 Sprint 2 Sprint 3 Sprint 4

22. works What we have learned what

23. Lesson 1 North Star before green light NL shop / ClipartOf.

24. Lesson 2 Hybrid approach works best A little design up front Designer partnership with developer +

25. Lesson 3 Product Designer replaces Product Owner

26. We like Agile software development But…

27. But…. Agile won’t fix your products

28. Our Philosophy Product design matters It transforms a product

29. Take a commodity Bag of features

30. Into a unique experience Transform it

31. Theresa Smith SphereOI Sphere_OITSmith@SphereOI.com