Surviving The Software Development Process

33 %
67 %
Information about Surviving The Software Development Process

Published on February 19, 2008

Author: frogdesign

Source: slideshare.net

Description

Surviving the Software Development Process. Collin ColeSenior Vice President, frog design

Collin Cole Senior Vice President, frog design Austin TX collin.cole@frogdesign.com Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 1

frog is a strategic-creative consulting firm. We bring a unique combination of strategic and creative talent to help companies evolve, expand, and envision their business. Our rigorous yet unorthodox approach yields breakthrough innovation and a sustainable competitive edge. Palo Alto San Jose San Francisco Seattle Austin New York Stuttgart Milan Shanghai Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 2

Surviving the Software Development Process How to deliver a great brand experience through better software design Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 3

Two parts: 1. Why good software design is difficult 2. Five ways to survive the process and deliver a great design Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 4

A couple of quick definitions “Software” = web, embedded, mobile, desktop applications “Designers” = agencies, contractors, internal corporate groups Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 5

Software is a vital element of your brand identity. Software is your customer’s daily interaction with your brand. Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 6

Think of the care that goes into the consistent delivery of your brand. Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 7

Why isn’t it the same with your company’s software? Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 8

The software landscape is overwhelming. Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 9

Software is complex. Applications entertainment, information, productivity Device Connectivity policies, permissions, protocols Devices home, mobile, business, entertainment Services, Servers & Data content, contacts, media, commerce Networks fixed, wireless, satellite Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 10

The process is hard. Tools are difficult (they’re getting better) Traditional roles inhibit collaboration The traditional, sequential process has gaps. Crossing each gap requires translation and interpretation MARCOM/STRATEGY ? DESIGN ? DEVELOPMENT 0100110100 01001 1101010001 0010111011 Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 11

But mostly, it’s because your design is left in the hands of others with very different priorities. Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 12

How we’ve adapted at frog design. Focused our tech efforts on UI/UX Increased the designer:developer ratio to about 4:1 Created a “design technologist” position : a design-minded, UI-focused developer, and added other complementary roles Invested in new design & development tools Updated our process to be more collaborative and iterative Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 13

Case Study: How we’ve adapted at frog BEST IN SHOW AWARD Best Business/Productivity Application, People’s Choice Award Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 14

Collaborative and concurrent design and development How we’ve adapted at frog January December Strategy & Design Development PROJ 1 PROJECT 2 PROJECT 3 Discovery Proof of concept Full product design and prototype (on handset) development, testing, launch First idea to final product (tested, on the market) in less than 12 months Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 15

SURVIVING THE SOFTWARE DEVELOPMENT PROCESS five ways to keep your brand in one piece Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 16

1. Own the user experience. Ensuring a quality implementation is YOUR responsibility. Expand your skills; stretch and grow. If you don’t have developers, hire them. Deliver what you can; simulations, key templates, reference implementations. Old-style design specifications just don’t work. Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 17

Major League Baseball Microsoft Silverlight Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 18

Lawson M3 Smart Client 4 month Design-UI Development cycle Microsoft .NET3/WPF Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 19

Designers are designing while developers have already started. DESIGN PHASE DEVELOPMENT design research, information architecture, wireframes,  workflows, interaction design, visual design, flash demos,  usability testing, internal presentations, design  Design documentation…  Specification * Rate of increase is proportional  Project to the number of executives involved Brief TIME… Development Reality functional requirements and feature lists, team assignments  and scheduling, systems architecture, platform development,  proof‐of‐concept prototyping… (they’ve already started!)  Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 20

2. Start building something. Drastically shorten the first design step. Rough out a wireframe and start prototyping. Get out of Photoshop/Illustrator/Visio. Prototype as a process. What you build serves to communicate between all groups and continually resets expectations. Prototype as a specification. If a picture is worth a thousand words, a prototype is worth a thousand pages of pretty documentation. Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 21

Yahoo! Messenger Microsoft .NET3/WPF 2 designers, 2 developers 6 months Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 22

3. Everyone is a designer. Build a team of technically-minded designers and design-aware developers. Encourage a collaborative and concurrent design-develop process. Get the design and development teams talking and working together, from the beginning. Take advantage of the uniquely different perspectives on the team. Good ideas can come from anywhere. Developers are often in the best position to recognize improvements in interaction design. Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 23

Fox Sports Microsoft Media Center application Silverlight/MCML Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 24

4. You’re not finished until it ships. Stay involved during implementation to provide design oversight for the inevitable surprises, compromises, and on-the-spot fixes. Remember, the quality of the final product is YOUR responsibility. No finger pointing allowed when it’s done. Schedule time for Design QA or “fit & finish” polishing. Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 25

Disney Software Suite “old school” C programming Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 26

5. Build a system, not just screens. Create a software DNA for your brand (personality, voice, visual components, interactions) Think modularly. Design for reuse and built-in consistency, even across different media, platforms, and devices. Make doing the right thing the easiest choice. Deliver your design documentation in a format that is easily accessed and used by engineers. Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 27

Online design specifications with design rules, copy & paste code snippets, and interactive, functional examples Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 28

HP’s elegant Photosmart identity spans platforms and devices. Collin Cole, SVP © 2008 frog design. Confidential & Proprietary. 2/17/2008 29

© 2008 frog design. Confidential & Proprietary.

Add a comment

Related presentations

Related pages

A Writer's Guide to Surviving Agile Software Development

in charge of the product development process, but Agile doesn't work unless those executives ... A Writer's Guide to Surviving Agile Software Development.
Read more

Software development process - Wikipedia, the free ...

Software development process; Core activities; Requirements; Design; Construction; Testing; Debugging; Deployment; Maintenance; Paradigms and models ...
Read more

Surviving the Wild West Development Process

Surviving the Wild West Development Process ... Nicely summarized typical software development process in disfunctional organizations ...
Read more

Surviving an Audit: Is Your Software Development Process ...

The thought of a software development process audit can literally send an organization into a frenzy ... Surviving an Audit: Is Your Software Development ...
Read more

Surviving the Quagmire of Process Models, Integrated ...

Surviving the Quagmire of Process Models ... and standards imposed on our software development and ... for software process appraisal and ...
Read more

IBM Podcast GIST: Welcome to this IBM Rational podcast ...

-1- IBM Podcast [ MUSIC ] GIST: Welcome to this IBM Rational podcast, Surviving an Audit: is Your Software Development Process Ready? I'm Kimberly Gist ...
Read more

Wiley :: The Accidental Project Manager - John Wiley & Sons

The Accidental Project Manager: Surviving the ... You've just been asked to manage a software development ... In The Accidental Project Manager, ...
Read more

A Writer's Guide to Surviving Agile Software Development ...

A Writer's Guide to Surviving Agile Software Development. 7 September 2011. ... Email any product or process suggestions to everyone on your scrum team.
Read more