The importance of identity and vision to UX designers on agile projects
by johanna kollmann on Sep 01, 2009
- 10,964 views
Talk, Agile2009 conference in Chicago.
Exploring a UX perspective on agile. Based on MSc project research, University College London, 2008.
Talk, Agile2009 conference in Chicago.
Exploring a UX perspective on agile. Based on MSc project research, University College London, 2008.
Accessibility
Categories
Tags
More...Upload Details
Uploaded via SlideShare as Microsoft PowerPoint
Usage Rights
© All Rights Reserved
Statistics
- Favorites
- 45
- Downloads
- 237
- Comments
- 5
- Embed Views
- Views on SlideShare
- 10,627
- Total Views
- 10,964
aligning design and business in the agile UX way
-------------------------------------------------------------------------------
part A : UX and dev , kick-off meeting, happens 3 weeks before sprint
--------------------------------------------------------------------------------------------------
1) aligning all stakeholders, becoming the facilitator who makes sure everyone is talking to each other ( backend, front end, marketing , product owners)
2) aligning overall business strategy with sprints wishlist, stories and use-cases.
3) where we are in the product map.
- prioritising, release and backlog planning based on above.
4) setting design direction and defining the UX scope of this sprint based on priorities.
5) user research if needed before the design cycle starts
part B: the design cycle, what happens in the 2 week before current sprint
------------------------------------------------------------------------------------------------------
1) defining design goals and lots of sketching
2) discuss with stakeholders, refine
3) research & test - do hall way tests with paper sketches, maybe get in 5 users every friday type thing ?
3) lightweight wireframing and visual design
4) writing given, when, then (user story) and acceptance criteria
Part C- sprint kickoff ( day 0)
--------------------------------------------------------------
1) explain design and decisions to dev team
2) take questions, fill gaps if any
3) create visual assets and detailed storyboards where needed
during the sprint
-------------------------------------------
1) be in a standby support role
2) review development and ensure things are built to spec
3) UX - QA of completed development
4) usability testing of completed development
5) create stories based on usability findings ( these go into backlog)
6) Track numbers and use metrics as far as possible :)
Talk bout your work,
Spread the joy of designing things that actually get shipped and not just wireframed and specd'.
Let me know if you want to work on this together,
the photos on 360.com is a good case study for this. 1 year ago Reply