際際滷shows by User: leobarnes1 / http://www.slideshare.net/images/logo.gif 際際滷shows by User: leobarnes1 / Mon, 28 Mar 2022 15:04:18 GMT 際際滷Share feed for 際際滷shows by User: leobarnes1 When labels go bad /slideshow/when-labels-go-bad/251451426 labels2021v1-220328150418
Removing framework labels for the greater good! Why giving labels can sometimes imply what's 'inside' and how that may not always be true.]]>
Removing framework labels for the greater good! Why giving labels can sometimes imply what's 'inside' and how that may not always be true.]]> Mon, 28 Mar 2022 15:04:18 GMT /slideshow/when-labels-go-bad/251451426 leobarnes1@slideshare.net(leobarnes1) When labels go bad leobarnes1 Removing framework labels for the greater good! Why giving labels can sometimes imply what's 'inside' and how that may not always be true. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/labels2021v1-220328150418-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Removing framework labels for the greater good! Why giving labels can sometimes imply what&#39;s &#39;inside&#39; and how that may not always be true.
When labels go bad from Leo Barnes
]]> 126 0 https://cdn.slidesharecdn.com/ss_thumbnails/labels2021v1-220328150418-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 'User First, Mobile Second' - UX Camp Brighton 2019 /slideshow/user-first-mobile-second-ux-camp-brighton-2019/136554100 uxcampbrighton2019-mobilefirst-190315115243
My talk at UX Camp Brighton 2019 around designing for the user needs rather than around platform constraints.]]>
My talk at UX Camp Brighton 2019 around designing for the user needs rather than around platform constraints.]]> Fri, 15 Mar 2019 11:52:43 GMT /slideshow/user-first-mobile-second-ux-camp-brighton-2019/136554100 leobarnes1@slideshare.net(leobarnes1) 'User First, Mobile Second' - UX Camp Brighton 2019 leobarnes1 My talk at UX Camp Brighton 2019 around designing for the user needs rather than around platform constraints. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/uxcampbrighton2019-mobilefirst-190315115243-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> My talk at UX Camp Brighton 2019 around designing for the user needs rather than around platform constraints.
'User First, Mobile Second' - UX Camp Brighton 2019 from Leo Barnes
]]> 609 1 https://cdn.slidesharecdn.com/ss_thumbnails/uxcampbrighton2019-mobilefirst-190315115243-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 The Power of Communication /slideshow/the-power-of-communication-92874836/92874836 communicationbrownbag2018v2uxcampslideshare-180404152321
Communication is something that most of us take for granted. However not everybody thinks to tailor their method or style to match the audience. 'The Power of Communication' looks at why it is important, how bad communication can send a project off the rails and tips for good communication.]]>
Communication is something that most of us take for granted. However not everybody thinks to tailor their method or style to match the audience. 'The Power of Communication' looks at why it is important, how bad communication can send a project off the rails and tips for good communication.]]> Wed, 04 Apr 2018 15:23:21 GMT /slideshow/the-power-of-communication-92874836/92874836 leobarnes1@slideshare.net(leobarnes1) The Power of Communication leobarnes1 Communication is something that most of us take for granted. However not everybody thinks to tailor their method or style to match the audience. 'The Power of Communication' looks at why it is important, how bad communication can send a project off the rails and tips for good communication. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/communicationbrownbag2018v2uxcampslideshare-180404152321-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> Communication is something that most of us take for granted. However not everybody thinks to tailor their method or style to match the audience. &#39;The Power of Communication&#39; looks at why it is important, how bad communication can send a project off the rails and tips for good communication.
The Power of Communication from Leo Barnes
]]> 160 1 https://cdn.slidesharecdn.com/ss_thumbnails/communicationbrownbag2018v2uxcampslideshare-180404152321-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Fists with Your Toes - Learning to relax as a UX / BA crossbreed /slideshow/fists-with-your-toes-learning-to-relax-as-a-ux-ba-crossbreed/73882805 bauxuxcamp2017v2-170329161020
A talk I recently gave at UX Camp Brighton (25th March 2017) discussing my role as a User Experience Designer and Business Analyst. ]]>
A talk I recently gave at UX Camp Brighton (25th March 2017) discussing my role as a User Experience Designer and Business Analyst. ]]> Wed, 29 Mar 2017 16:10:20 GMT /slideshow/fists-with-your-toes-learning-to-relax-as-a-ux-ba-crossbreed/73882805 leobarnes1@slideshare.net(leobarnes1) Fists with Your Toes - Learning to relax as a UX / BA crossbreed leobarnes1 A talk I recently gave at UX Camp Brighton (25th March 2017) discussing my role as a User Experience Designer and Business Analyst. <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/bauxuxcamp2017v2-170329161020-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> A talk I recently gave at UX Camp Brighton (25th March 2017) discussing my role as a User Experience Designer and Business Analyst.
Fists with Your Toes - Learning to relax as a UX / BA crossbreed from Leo Barnes
]]> 629 4 https://cdn.slidesharecdn.com/ss_thumbnails/bauxuxcamp2017v2-170329161020-thumbnail.jpg?width=120&height=120&fit=bounds document Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 Writing Great User Stories /slideshow/brownbaguserstoriesv2/58154742 e2e11ceb-da2c-40e4-9a28-32311ef04715-160211153053
1. Setup slide 2. I'm here to talk about elements that make up user stories. It's supposed to be a starting point and does not discuss priority, planning or other elements of AGILE. Even if you don't write user tories, you should expect certain things. 3. Don't consider it a chore, be creative and try to discover edge cases. 4. This isn't strictly true but it's a collaborative process. Don't enforce your style on the rest of the team. Adapt as needed. 5. Do as much work upfront as you can and get rid of ambiguity. Agree a level of acceptability with the developers and testers. 6. We've all seen this. If you leave it to interpretation, people will do just that. Keep your AC in check. 7. You really can! Use as many visual aids as you can... they don't have to be perfect. Use a tool you're comfortable with. 8. Prepare to re-write. This should ALWAYS happen. Stories MUST NOT replace discussions. 9. Write stories that an end-user could do and then have a coffee. 10. Think about everything. It's okay to sit at your desk and just think. Consider the ridiculous and ask all the questions that you can. 11. Stories should be a surprise - planning should involve stories that everyone has previously seen. Do backlog reviews. 12. Write stories as if you had to test them and ask a tester to review the stories with you. Make sure you give them the level of detail that they need. 13. Keep stories small (but not too small). Apply common sense and experience. 14. Even if a story has zero development points, keep it in the sprint. It's a good marker for everyone to make sure it is done. 15. Don't expect to keep the same approach forever. Teams, projects and methods change. 16. Recap 17. Thank you]]>
1. Setup slide 2. I'm here to talk about elements that make up user stories. It's supposed to be a starting point and does not discuss priority, planning or other elements of AGILE. Even if you don't write user tories, you should expect certain things. 3. Don't consider it a chore, be creative and try to discover edge cases. 4. This isn't strictly true but it's a collaborative process. Don't enforce your style on the rest of the team. Adapt as needed. 5. Do as much work upfront as you can and get rid of ambiguity. Agree a level of acceptability with the developers and testers. 6. We've all seen this. If you leave it to interpretation, people will do just that. Keep your AC in check. 7. You really can! Use as many visual aids as you can... they don't have to be perfect. Use a tool you're comfortable with. 8. Prepare to re-write. This should ALWAYS happen. Stories MUST NOT replace discussions. 9. Write stories that an end-user could do and then have a coffee. 10. Think about everything. It's okay to sit at your desk and just think. Consider the ridiculous and ask all the questions that you can. 11. Stories should be a surprise - planning should involve stories that everyone has previously seen. Do backlog reviews. 12. Write stories as if you had to test them and ask a tester to review the stories with you. Make sure you give them the level of detail that they need. 13. Keep stories small (but not too small). Apply common sense and experience. 14. Even if a story has zero development points, keep it in the sprint. It's a good marker for everyone to make sure it is done. 15. Don't expect to keep the same approach forever. Teams, projects and methods change. 16. Recap 17. Thank you]]> Thu, 11 Feb 2016 15:30:53 GMT /slideshow/brownbaguserstoriesv2/58154742 leobarnes1@slideshare.net(leobarnes1) Writing Great User Stories leobarnes1 1. Setup slide 2. I'm here to talk about elements that make up user stories. It's supposed to be a starting point and does not discuss priority, planning or other elements of AGILE. Even if you don't write user tories, you should expect certain things. 3. Don't consider it a chore, be creative and try to discover edge cases. 4. This isn't strictly true but it's a collaborative process. Don't enforce your style on the rest of the team. Adapt as needed. 5. Do as much work upfront as you can and get rid of ambiguity. Agree a level of acceptability with the developers and testers. 6. We've all seen this. If you leave it to interpretation, people will do just that. Keep your AC in check. 7. You really can! Use as many visual aids as you can... they don't have to be perfect. Use a tool you're comfortable with. 8. Prepare to re-write. This should ALWAYS happen. Stories MUST NOT replace discussions. 9. Write stories that an end-user could do and then have a coffee. 10. Think about everything. It's okay to sit at your desk and just think. Consider the ridiculous and ask all the questions that you can. 11. Stories should be a surprise - planning should involve stories that everyone has previously seen. Do backlog reviews. 12. Write stories as if you had to test them and ask a tester to review the stories with you. Make sure you give them the level of detail that they need. 13. Keep stories small (but not too small). Apply common sense and experience. 14. Even if a story has zero development points, keep it in the sprint. It's a good marker for everyone to make sure it is done. 15. Don't expect to keep the same approach forever. Teams, projects and methods change. 16. Recap 17. Thank you <img style="border:1px solid #C3E6D8;float:right;" alt="" src="https://cdn.slidesharecdn.com/ss_thumbnails/e2e11ceb-da2c-40e4-9a28-32311ef04715-160211153053-thumbnail.jpg?width=120&amp;height=120&amp;fit=bounds" /><br> 1. Setup slide 2. I&#39;m here to talk about elements that make up user stories. It&#39;s supposed to be a starting point and does not discuss priority, planning or other elements of AGILE. Even if you don&#39;t write user tories, you should expect certain things. 3. Don&#39;t consider it a chore, be creative and try to discover edge cases. 4. This isn&#39;t strictly true but it&#39;s a collaborative process. Don&#39;t enforce your style on the rest of the team. Adapt as needed. 5. Do as much work upfront as you can and get rid of ambiguity. Agree a level of acceptability with the developers and testers. 6. We&#39;ve all seen this. If you leave it to interpretation, people will do just that. Keep your AC in check. 7. You really can! Use as many visual aids as you can... they don&#39;t have to be perfect. Use a tool you&#39;re comfortable with. 8. Prepare to re-write. This should ALWAYS happen. Stories MUST NOT replace discussions. 9. Write stories that an end-user could do and then have a coffee. 10. Think about everything. It&#39;s okay to sit at your desk and just think. Consider the ridiculous and ask all the questions that you can. 11. Stories should be a surprise - planning should involve stories that everyone has previously seen. Do backlog reviews. 12. Write stories as if you had to test them and ask a tester to review the stories with you. Make sure you give them the level of detail that they need. 13. Keep stories small (but not too small). Apply common sense and experience. 14. Even if a story has zero development points, keep it in the sprint. It&#39;s a good marker for everyone to make sure it is done. 15. Don&#39;t expect to keep the same approach forever. Teams, projects and methods change. 16. Recap 17. Thank you
Writing Great User Stories from Leo Barnes
]]> 516 4 https://cdn.slidesharecdn.com/ss_thumbnails/e2e11ceb-da2c-40e4-9a28-32311ef04715-160211153053-thumbnail.jpg?width=120&height=120&fit=bounds presentation Black http://activitystrea.ms/schema/1.0/post http://activitystrea.ms/schema/1.0/posted 0 https://cdn.slidesharecdn.com/profile-photo-leobarnes1-48x48.jpg?cb=1738680483 Experience in production of digital content since 1998, working across online, interactive television and mobile platforms. I work with a wide range of both internal and external clients and pride myself on being easy to communicate with, as well as consistently getting the job done to the highest standard. I produce content that the user actually wants and that their expectations are not only met, but exceeded. The most successful products are those that are created by people who understand the customers needs. Specialties: Lean product development, project planning, effective brainstorm management, creating products to brand and within budget, focussing on the detail as well as the b... http://www.amazon.com https://cdn.slidesharecdn.com/ss_thumbnails/labels2021v1-220328150418-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/when-labels-go-bad/251451426 When labels go bad https://cdn.slidesharecdn.com/ss_thumbnails/uxcampbrighton2019-mobilefirst-190315115243-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/user-first-mobile-second-ux-camp-brighton-2019/136554100 &#39;User First, Mobile Se... https://cdn.slidesharecdn.com/ss_thumbnails/communicationbrownbag2018v2uxcampslideshare-180404152321-thumbnail.jpg?width=320&height=320&fit=bounds slideshow/the-power-of-communication-92874836/92874836 The Power of Communica...