Learning from a Culture of Collaboration: Engineers do it better. What can designers learn from them? #GHC15

Learning from a Culture of Collaboration: Engineers do it better. What can designers learn from them? #GHC15

• 1.
  2015   Learning froma Culture of Collaboration:
 Engineers do it better. What can designers learn from them? 
 Yvonne So, Intuit Oct 2015 #GHC15 2015
• 2.
  2015   What isAgile? 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
• 3.
  2015   Traditional WaterfallModel http://www.powerobjects.com/2013/02/11/microsoft-dynamics-crm-and-agile-development/
• 4.
  2015   Agile ScrumApproach http://scrumreferencecard.com/
• 5.
  2015   Dichotomy Engineers Generally cheerful
 More actively engaged
 Motivated to solve problems 
 Productivity is high Designers Stressed out and losing hair 
 Impartial or unengaged Constantly under deadline Low visibility into others’ workstreams
• 6.
  2015   Examples ofDesign Deliverables •  Wireframes •  Conceptual Mockups •  Storyboards •  Functional Specs •  Final Assets •  User Testing •  Prototypes •  Research Decks
• 7.
  2015   What if... Whatif a lot of designers’ work could be alleviated simply by collaborating the way engineers do?
• 8.
  2015   Turn EngineeringPrinciples into Design Principles
• 9.
  2015   PAIRED PROGRAMMING Two programmerswork together as peers at a single computer, focusing on writing quality software. PARTNER DESIGNING Interaction and visual designers communicate regularly. Clearly define roles. Share the workload or divvy up work into smaller tasks.
• 10.
  2015   CODE REVIEWS Themain purpose of code reviews is to keep code quality and readability high. PEER REVIEWS Give and receive feedback. System of checks and balances. Adhere to company’s brand style guide colors and patterns.
• 11.
  2015   REFACTORING Restructuring andcleaning up an existing body of code, altering its internal structure without changing the functionality. SOURCE FILE CONTROL Revisit source files and clean them up. Make sure layers are adequately and logically named. Get rid of any unnecessary layers and metadata.
• 12.
  2015   DAILY STANDUP Everyworkday 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. DESIGN STANDUP Regularly schedule standups so everyone has visibility into each other’s patterns and features. Share out status, designs, feedback. Have quick sketch and brainstorm sessions.
• 13.
  2015   RETROSPECTIVE A sprintretrospective allows a team to continuously evolve and improve throughout the product lifecycle.   DESIGN RETROSPECT Reflect upon what you’ve accomplished. Think of new ways to improve workflow. Identify anything you should stop doing.
• 14.
  2015   Outcome Improved collaboration (increasedcommunication, 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)
• 15.
  2015   What if... Whatif YOUR work could be alleviated by implementing Agile engineering principles?
• 16.
  2015   Thanks! Stay intouch: Yvonne So Sr. UX Designer, Intuit yvonneyso@gmail.com @yvonniks
• 17.
  2015   Got Feedback? Rateand Review the session using the GHC Mobile App
 To download visit www.gracehopper.org