The document discusses Agile design principles as presented by Pieter Jongerius, focusing on Scrum methodology and its emphasis on process over product speed. It outlines the steps involved in Scrum, such as team setup, sprint planning, and the importance of user-centered stories. The document also raises critical questions about the efficiency of Agile compared to traditional methods, the role of designers, and the nature of Agile work dynamics.

1. UX Cocktail Hour on Agile design @ Fabrique Pieter Jongerius, Interaction Director twitter.com/pieterj linkedin.com/in/pieterj 15 oktober 2009 Last time: Steve Portigal

2. agile design / agile development /!\ some of the images have been intentionally blurred, sorry about that... agile basics steps we take physical design agree/disagree, or questions we still have about Fabrique

3. So, let’s go agile.

4. scrum is an agile method.

5. no trafficlights

6. to us, agile is about process, not product speed people physicality discovery learning forgetting your discipline equality Fun! customer emotions responsibility results,

7. the scrum cycle scrum team interaction designers, designers, developers, product owner, project manager(?), scrum master These images some rights reserved by original owners

8. scrum board

12. Steps we take

13. scrum steps we take prepare decide on team and sprint setup

14. sprint setup sprint 0 self-regulated sprints fixed deliverable sprints sweep sprint

15. scrum steps we take prepare decide on team and sprint setup prepare scrum room

19. scrum steps we take prepare decide on team and sprint setup prepare scrum room create product backlog

22. scrum steps we take prepare decide on team and sprint setup prepare scrum room create product backlog sprint! sprint planning meeting (stories, actions, estimations)

26. scrum steps we take prepare decide on team and sprint setup prepare scrum room create product backlog sprint! sprint planning meeting (stories, actions, estimations) daily scrum & evaluation

31. scrum steps we take prepare decide on team and sprint setup prepare scrum room create product backlog sprint! sprint planning meeting (stories, actions, estimations) daily scrum & evaluation design physically, build for real

39. scrum steps we take prepare decide on team and sprint setup prepare scrum room create product backlog sprint! sprint planning meeting (stories, actions, estimations) daily scrum & evaluation design physically, build for real demo

41. demo designs prototype built product (or part)

42. done!

43. questions so far?

44. agree or disagree

45. agree or disagree? agile at all? scrum is less efficient than waterfall responsibility comes from within, not from post-it agile means messy code. always. agile dogmas real agile cannot be design-only stories must always be formulated from a user need “as a user, I want to…” agile puzzles how specific should stories be before they are ready? do designers get bored at the end of a sprint? in agile, is there a place for junior team members?

46. Fabrique Communication and Design

47. Delft

48. Amsterdam

49. since ’92 80 employees artists & engineers

50. clients

51. seemingly simple solutions to complex questions