Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Agile, UX and The Enterprise

942 views

Published on

The story of what it's like being a UXer part of a large organisational transformation journey from Waterfall to Agile practices, and the "in-progress" view of the process looks like.

Published in: Technology
  • Hello, it seems that you took my copyrighted image, modified it and used on slide 49 of your deck. Attribution link also doesn't follow Flickr TOS. Original image can be found here, clearly marked All rights reserved : https://www.flickr.com/photos/81237759@N00/9629749173
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here

Agile, UX and The Enterprise

  1. 1. Agile & The Enterprise From a UX Perspective 13/03/2015 Presented by: Lexi Thorn & Scott Maywood-Bryant #agileux15 @ANZ_AU @lexithorn @ScotTheLot
  2. 2. Thanks to the awesome speakers  • Ben & Diana – disrupting the disruptor (so meta!), and why agile iterative development is well suited to a customer centered test and learn approach • Cameron – agile conversion journey, and overcoming the “cowboys” by not following agile techniques blindly • Sophie – we need to go High Definition with our communication, trust needs to be in the room with distribution • Ruth & Simon – how not to be dicks to each other – awesome • Megan – hands on practical advice for conducting diary studies, love the hand-craftiness too • Karen – Fadgile -> Wagile -> Radgile and your amaze-gile puns • Warwick – on setting UXpectations and a framework for measuring the quality of experience over time • Jake – the importance of having a Vision, and valuing agility over Agile with a capital A 2
  3. 3. 3 Attribute: http://www.sodahead.com/fun/do-you-say-hihelloor-hey/question-2166579/
  4. 4. 4 Attribute: http://www.heyuguys.com/jj-abrams-suggests-3d-post-conversion-for-star-trek-2/starship-enterprise/
  5. 5. 5Attribute: http://hellinspace.com/2014/03/25/5-great-crews-of-5-great-starships-on-the-small-screen/
  6. 6. 6
  7. 7. 7
  8. 8. 8
  9. 9. 9 Built 50% 30% 20% Hardly Ever Used Used Infrequently Used Often Source: Standish Group Chaos Report 2010 Features that are What’s built?
  10. 10. You’re going to get feedback sometime 10 …better earlier than later
  11. 11. It’s awesome working in a great team culture 11
  12. 12. 12Attriute: http://antiekllc.com/banana-split-clipart
  13. 13. Our talk 13 1. Discovery: Iteration 0 - Foundation 2. Planning: Backlog & Releases 3. Delivery: Iteration 1+ 4. Supporting elements (Workspace, tools etc.)
  14. 14. 1. Discovery (Iteration 0) - Foundation 14 Business readiness: • Vision • Project goals • Requirements gathering • Research • Accessibility • Content strategy • Concepts & Prototyping • etc. Technology readiness: • Environments • Tooling • System architecture • BDOS • Devices • etc.
  15. 15. 1. Discovery (Iteration 0) - Foundation Business readiness • 1.1 Vision • 1.2 Concepting & Prototype 15
  16. 16. 16 Attribute: http://www.radhanathsvami.si/vsi-clanki/
  17. 17. 17 Attribute: http://blog.abovethefolddesign.com/2012/11/02/teaming-with-success/
  18. 18. 18 Attribute: http://blog.abovethefolddesign.com/2012/11/02/teaming-with-success/
  19. 19. 1.1 Vision 19 Q. How do we know our team has the same view of success?
  20. 20. Three workshops covered: Workshop 1 – Product landscape • Review of Product Strategy and roadmap • What will make this project a success from a Product point of view? • What are the best ways of working together? Workshop 2 – Overarching Vision and Principles • What do we collectively know about the customer and their needs? • What is our Vision for the product? • CX and Content principles Workshop 3 – Visual Design Principles • What attributes should our customers use to describe our design? • How can we articulate the visual design Vision? • How should the site look and feel to our customers? We have also revisited previous knowledge gathered e.g. Digital Sales and Marketing analytics, branch and contact centre visits etc. 20 1.1 Vision: Stakeholder workshops Goal: Shared understanding of the vision, business context and design challenges
  21. 21. 1.1 Vision: Research 21Attribute: http://imgarcade.com/1/synthesize-clipart/
  22. 22. Synthesising outputs to formulate brief
  23. 23. 1.1 Vision: We then created a clear brief Contains: • Our Vision for the project, and the drivers of success • Playback of business context gathered to date • Design challenges: • They are actionable and meaningful • I can make design decisions off these • I can check my design work against these • …to confirm that I’m heading in the right direction • We describe what we are aiming to solve rather than how we are solving it
  24. 24. 24 Attribute: http://loricca.com/security-awareness-and-compliance-training/ 1.1 Vision: Outcome
  25. 25. 1. Discovery (Iteration 0) Business readiness • 1.1 Vision • 1.2 Concepting & Prototype 25
  26. 26. 1.3 Concepting & Prototype 26 Divergent thinking Convergent thinking Prototype Customer research Brief & Design challenges
  27. 27. 1.3 Concepting & Prototype: Exploratory research 27Attribute: http://www.uxpassion.com/uxp/wp-content/uploads/2014/04/usability_contextual_inquiry-784x681.jpg
  28. 28. 1.3 Concepting & Prototype: Divergent 28 Attribute: http://webdesignledger.com/wp- content/uploads/2013/06/wireframe01.jpghttp://webdesignledger.com/wp- content/uploads/2012/10/wireframes25.jpg
  29. 29. 1.3 Concepting & Prototype: Refinement research 29
  30. 30. 1.3 Concepting & Prototype 30 Q. What’s the output at this stage?
  31. 31. 1.3 Concepting & Prototype: Artefacts 31 Prototypes Attribute: http://www.paulnobles.com/wp-content/uploads/2011/08/axure-prototype1.png • Breadth of the system • Tricky interactions …deferring detailed design decisions to the last responsible moment (within Sprint cycles) • Interaction framework • Allows us to estimate
  32. 32. 1.3 Concepting & Prototype: Artefacts 32 Attribute: http://styletil.es/ Style guide (lightweight), Grid system
  33. 33. Lightweight, communicative artifacts over large upfront design 33 Attribute: http://www.agilemodeling.com/essays/agileDocumentationBestPractices.htm
  34. 34. 34 http://moodybluesattitude.yuku.com/topic/10833/2012-My-First- House-as-its-being-built#.VOKt2lWUfp0
  35. 35. 35 http://www.martzoukos.com/wp-content/uploads/overdesigned- swiss-army-knife3.jpg
  36. 36. Our talk 36 1. Discovery: Iteration 0 2. Planning: Backlog & Releases 3. Delivery: Iteration 1+ 4. Supporting elements (Workspace, tools etc.)
  37. 37. 2. Planning 37 Q. How do you move from…
  38. 38. 38 Prototype User stories for development
  39. 39. 2.1 Break prototype into components, modules, features 39
  40. 40. 2.2 Write user stories & acceptance criteria 40 …providing enough information so each module can be estimated by dev at a high level 8 13 5 2 3
  41. 41. 2.3 Prioritised by the Product Owner 41
  42. 42. 42 http://www.clipartbest.com/cliparts/jTx/K4b/jTxK4bqTE.jpeg Cool
  43. 43. Our talk 43 1. Discovery: Iteration 0 2. Planning: Backlog & Releases 3. Delivery: Iteration 1+ 4. Supporting elements (Workspace, tools etc.)
  44. 44. 44 Attribute: http://www.agilemodeling.com/essays/agileDocumentationBestPractices.htm
  45. 45. 3. Delivery: Designing for optimisation 45
  46. 46. 3. Delivery: UX as part of the delivery team 46 IT -1 IT IT +1 2 weeks 2 weeks 2 weeks Working together with the BA’s to detail our design ready to support the development team throughout the sprint. Up-front design In-flight design Working together with the devs and system test team in the nuts and bolts of the code, supporting and making minor design decisions/tweaks on the fly as things come to life. Working together with the UAT team to make sure the design meets business acceptance criteria. Design acceptance
  47. 47. …we could wear one of any three hats in an iteration IT +1 2 weeks IT IT -1 IT +1 2 weeks IT IT -1 IT +1 2 weeks IT IT -1
  48. 48. 48 Attribute: http://school.discoveryeducation.com/clipart/clip/answer-girl2.html All clip art in Discovery Education's Clip Art Gallery created by Mark A. Hicks, illustrator.
  49. 49. Moving from a model of solving problems linearly… 49 Attribute: https://farm6.staticflickr.com/5495/9629749173_962f61f5af.jpg Requirements > Design > Development > Testing
  50. 50. …to solving problems as a team 50 https://lh5.googleusercontent.com/- ZYzhnCG8Gak/Uy24FWTmKEI/AAAAAAAAAFQ/d89KwykVFKA/w654-h654/lego_group.png
  51. 51. Our talk 51 1. Discovery: Iteration 0 2. Planning: Backlog & Releases 3. Delivery: Iteration 1+ 4. Supporting elements (Workspace, tools etc.)
  52. 52. 4. Supporting elements 52 Q. What things help?
  53. 53. 53
  54. 54. 4. Supporting elements: Workspace 54
  55. 55. 4. Supporting elements: Resourcing • Our CX team are resourced in a way that can work with this process • People that can do heavy lifting during discovery • Then have people (1 UX, 1 Designer) that sit alongside the delivery team 55
  56. 56. 4. Supporting elements: Tools 56
  57. 57. 4. Supporting elements: Umbrella people 57http://images.clipartpanda.com/umbrella-clipart-9ipez9X9T.svg
  58. 58. 4. Supporting elements: Communication 58 Governance Project team Attribute: http://manage-it.biz/services/itil-process-modules/manage-governance/
  59. 59. 4. Supporting elements: Coach 59 Attribute: http://www.prepare1.com/linkedin-ranks-profile-based-views/
  60. 60. 60 Fair use - © Miller-Milkis Productions (Miller-Milkis-Boyett Productions in later years) and Henderson Productions in association with Paramount Television. 4. Supporting elements: More Fonzies
  61. 61. 61 He’s laughing on the inside http://www.kethinov.com/images/startrek/TOS2x15q.png
  62. 62. 62 Attribute: http://www.heyuguys.com/jj-abrams-suggests-3d-post-conversion-for-star-trek-2/starship-enterprise/
  63. 63. 63 Leonard Nimoy 1931 -2015 Attribute: http://teeroy766.deviantart.com/
  64. 64. QUESTIONS  64
  65. 65. Discussion topics • Has anyone else got a perspective that they’d like to share? • Enterprise or other? • What are the biggest challenges you’ve had to overcome in your Agile projects? • How does your Iteration 0 planning/discovery process work? • Do you do one? • What are the ratios of people in your teams? Product/BA/UX/Visual/FE/BE/Test • What kinds of research to you do? How do you weave this in? • How do you manage all of this in “Sprints” • Do you work, one, two, three or more sprints ahead? 65

×