Agile Design the Fabrique way
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Agile Design the Fabrique way

on

  • 5,194 views

In recent years, Fabrique has executed several large projects in an Agile way. Each time the methods, tools and techniques were used in a different way. I shared our war stories with the Amsterdam UX ...

In recent years, Fabrique has executed several large projects in an Agile way. Each time the methods, tools and techniques were used in a different way. I shared our war stories with the Amsterdam UX community at the Fabrique-hosted UX Cocktail Hour Amsterdam of october 15, 2009. The talk was well received and we got some great discussion out of it. Please contact me for any questions.

Statistics

Views

Total Views
5,194
Views on SlideShare
5,171
Embed Views
23

Actions

Likes
19
Downloads
105
Comments
3

3 Embeds 23

http://www.slideshare.net 15
http://www.linkedin.com 4
https://www.linkedin.com 4

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
  • Hi All, thanks for your interest! For an updated version, please check my more recent presentation on Scrum. Questions? I'd be happy to answer!
    Are you sure you want to
    Your message goes here
    Processing…
  • Exellent points. You're right that this DOD is somewhat skewed. These days we try to balance these three aspects in a DOD: user experience, technical reqs, customer acceptance.
    Are you sure you want to
    Your message goes here
    Processing…
  • I see in your 'definition of done' mostly items about 'building the software right', so more or less whether the quality is passing standards. However, I don't see items about 'building the right software', for instance, passing user acceptance test, or complying with requirements, etc. Also, it doesn't say whether a feature should be running in a production environment or not, so all these items could apply to just a development environment. You could even take it a step further, you could include in your definition of done that the feature is actually being used by end-users in a production environment, although, this may be a somewhat questionable item on your Definition of Done list...
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Agile Design the Fabrique way Presentation Transcript

  • 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
  • 9.  
  • 10.  
  • 11.  
  • 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
  • 16.  
  • 17.  
  • 18.  
  • 19. scrum steps we take
    • prepare
    • decide on team and sprint setup
    • prepare scrum room
    • create product backlog
  • 20.  
  • 21.  
  • 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)
  • 23.  
  • 24.  
  • 25.  
  • 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
  • 27.  
  • 28.  
  • 29.  
  • 30.  
  • 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
  • 32.  
  • 33.  
  • 34.  
  • 35.  
  • 36.  
  • 37.  
  • 38.  
  • 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
  • 40.  
  • 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
  • 52.