Transcript
Page 1: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Design and development as one fluid process

Don’t go chasing waterfalls

Page 2: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 3: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 4: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

type influence

Page 5: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 6: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 7: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 8: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Designers who can code

Page 9: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 10: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 11: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

http://screensiz.es

Page 12: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Some things we’ve observed

Page 13: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 14: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 15: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 16: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Some things that are working(for us... so far)

Page 17: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Iterations

Page 18: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 19: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 20: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Minimum Viable Product

Page 21: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 22: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 23: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 24: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Stories rather than artifacts

Page 25: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 26: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Rapid Prototyping

Page 27: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 28: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 29: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Integration

Page 30: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 31: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 32: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 33: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 34: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 35: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 36: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 37: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 38: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 39: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 40: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 41: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 42: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

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

Page 43: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 44: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 45: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

Pragmatism

Page 46: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process
Page 47: After the Jump > Type Code: Don't go chasing waterfalls: design and development as one fluid process

thanks.

@typecode