Learning from a Culture of Collaboration: What Can Designers Learn From Engineers?

If you like this presentation – show it...

Slide 0

#GHC15 Learning from a Culture of Collaboration:
 Engineers do it better. What can designers learn from them? 
 Yvonne So, Intuit Oct 2015 2015 2015  

Slide 1

What is Agile? Agile methodologies are an alternative to waterfall, or traditional sequential development Agile is a mindset, not a process Focus on experimentation and collaboration over deliverables and documentation 2015  

Slide 2

Traditional Waterfall Model http://www.powerobjects.com/2013/02/11/microsoft-dynamics-crm-and-agile-development/ 2015  

Slide 3

Agile Scrum Approach http://scrumreferencecard.com/ 2015  

Slide 4

Dichotomy Designers Engineers Generally cheerful 
 More actively engaged
 Motivated to solve problems 
 Productivity is high Stressed out and losing hair 
 Impartial or unengaged Constantly under deadline Low visibility into others’ workstreams 2015  

Slide 5

Examples of Design Deliverables •  •  •  •  Wireframes Conceptual Mockups Storyboards Functional Specs 2015   •  •  •  •  Final Assets User Testing Prototypes Research Decks

Slide 6

What if... What if a lot of designers’ work could be alleviated simply by collaborating the way engineers do? 2015  

Slide 7

Turn Engineering Principles into Design Principles 2015  

Slide 8

PAIRED PROGRAMMING PARTNER DESIGNING Interaction and visual designers communicate regularly. Two programmers work together as peers at a single computer, focusing on writing quality software. Clearly define roles. Share the workload or divvy up work into smaller tasks. 2015  

Slide 9

CODE REVIEWS PEER REVIEWS The main purpose of code reviews is to keep code quality and readability high. Give and receive feedback. System of checks and balances. Adhere to company’s brand style guide colors and patterns. 2015  

Slide 10

SOURCE FILE CONTROL REFACTORING Revisit source files and clean them up. Restructuring and cleaning up an existing body of code, altering its internal structure without changing the functionality. Make sure layers are adequately and logically named. Get rid of any unnecessary layers and metadata. 2015  

Slide 11

DAILY STANDUP DESIGN STANDUP Regularly schedule standups so everyone has visibility into each other’s patterns and features. Every workday at a specified time, the team meets at a daily standup to bring everyone up to date on the information that is vital for coordination. Share out status, designs, feedback. Have quick sketch and brainstorm sessions. 2015  

Slide 12

DESIGN RETROSPECT RETROSPECTIVE Reflect upon what you’ve accomplished. A sprint retrospective allows a team to continuously evolve and improve throughout the product lifecycle.   Think of new ways to improve workflow. Identify anything you should stop doing. 2015  

Slide 13

Outcome Improved collaboration (increased communication, willingness to give feedback and help others, more sharing of files, shared goals) Increased engagement (more team lunches, regular sketch fests, weekly check-ins) Boosted productivity (knowledge share-outs, cleaned-up files, aligning roadmaps to reduce redundant work) 2015  

Slide 14

What if... What if YOUR work could be alleviated by implementing Agile engineering principles? 2015  

Slide 15

Thanks! Stay in touch: Yvonne So Sr. UX Designer, Intuit yvonneyso@gmail.com @yvonniks 2015  

Slide 16

Got Feedback? Rate and Review the session using the GHC Mobile App
 To download visit www.gracehopper.org 2015  

Slide 17