Janet Chang’s Blog about Design

Can’t we just all get alone? Human-centered design meets agile

Speaker: Maria Giudice, Hot Studio, Inc.
Date: September 20, 2008

Waterfall approach

• Predictable and structured approach
• Human-centered: solutions are based on upfront research and strategy
• Team roles are clearly defined (designers design, engineers build)
• Rigid, heavy, and slow
• Documentation and specifications

“Waterfall method is best when you can’t afford to learn from your mistakes. You don’t design software for the Space Shuttle in an Agile manner.” Alon Salant, engineer

When Waterfall method works better
Type of projects:

• Creating experiential, immersive, branded experiences that are not module-driven.
• High-risk or complex projects that require breadth and deep thinking.
• Findings through design research and insight are key to project success.

Team dynamics:

• Engineering platform and team is not defined early on
• Team is remote, making collaboration and quick decision-making difficult

Client situations:

• Clients that don’t understand user’s needs, want and desires and lack domain knowledge
• Cannot be involved face-to-face, day-today or make decisions quickly
• Many stakeholders that require documentation to provide context around decision-making

Agile Manifesto, 2001

We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value:

Individuals and interactions over process and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Agile approach
Deliver useful, working software early and continuously through iteration.

• Trust
• Flexibility and ability to handle changing requirements
• Client-driven or engineer-driven design, designers as consultant
• Solutions largely based on intuition or hunches
• Priorities are focused on addressing business needs and value
• Lightweight
• Fast but not necessarily cheaper

Agile methods

• EX – Extreme Programming
• FDD – Feature Driven Development
• Crystal
• Scrum
• DSDM – Dynamic System Development Method
• Adaptive Software Development
• Lean Software Development
• Rational Unified Process

“All the engineers need is a picture and a conversation.” Josh Damon Williams, user experience architect

When Agile works better
Types of projects:

• Applications with an existing conceptual framework already in place; adding features
• Start-ups with a very clear vision of their product, its features and goals
• Early working prototypes are that required for funding, speed to market is critical

Team dynamics:

• Trust is paramount
• Experienced, embedded team that can collaborate and actively participate
• Designers (user experience and visual) who are comfortable with constant iteration
• Engineers who are human-centric

Client situations:

• Clients who can make quick decisions and are available every day (but can change their mind)
• Business goals and vision are clear and will not change
• Client understands users needs, subject matter, and domain knowledge

Big disconnects – Waterfall vs. Agile
Holistic vs. modular thinking
Research-based assumptions / decisions vs. hunches / intuition
Enumeration and alternatives vs. iterations
User research vs. user validation
Scheduled changes vs. continual change
Artifacts vs. working software
Quality vs. quantity

Similarities
Full team involvement and participation is important on day one
User feedback is valued at all points in the process
Collaboration and respecting individual contribution is key to good design
Prioritization methods help set expectations
Design for flexibility; expect change and evolution
Communication is critical and needs to be transparent

Lesson learned

• Redefined the definition of “designer” – include everyone in the design process, but still be clear on ownership of decisions, including clients.
• Communicate and collaborate early and often.
• Be flexible, trust your team, and don’t let your ego get the best of you.