Agile tour 2018 from post it to prototype
1 like605 views
The Agile Tour Sydney 2018 focuses on addressing key questions regarding strategy, user needs, success metrics, and communication for a web-focused project by the Shire Council. Teams are tasked with designing a prototype over 7 sprints, incorporating insights from user research and ensuring alignment on goals. The workshop emphasizes collaboration, creative idea generation, and connecting with the broader company vision to enhance teamwork and project outcomes.
Agile tour 2018 from post it to prototype
- 1. Agile Tour Sydney 2018 1
- 7. 7
- 8. Can we answer these questions? 1. What is our strategy? 2. What is the user need? 3. What does success look like? 4. Do we have shared understanding on what to deliver when? 5. Have we sufficiently communicated and supported the change? 6. What have we learnt? 7. What constraints are our teams experiencing? What are we doing to remove these challenges? 8. Are we all still connected as we scale? Do we still have good discipline in place, without slowing down?
- 10. The Shire Council is updating the section about pets on their website to reflect updated guidelines and legislation. The ask: ● You have 7 sprints of 10min to research and design a prototype that meets the needs of local residents. ● One person from each team will represent: User needs, council needs/technical requirements, metrics and legislative requirements. ● While the brief is purely web-focussed, your solution doesn’t have to be - if you can make a compelling case for your solution Our challenge for today
- 14. 20 min
- 15. Facilitator notes ● Ask the PM to create a coherent product pitch after the session and share back to the team the next morning ● If multiple users with different needs and/or problems, create one pitch for each user group ● If multiple product pitches, decide which one to take forward Test current knowledge of the problem / opportunity space by filling in the product pitch template. ● Read template out loud to familiarise participants with the format ● Ask everyone to write one sticky per line item, silently and individually (whoever has prior knowledge of the initiative) ● Post them top to bottom per person, left to right ● Organise similar ideas ● Discuss differences, gaps ● Formulate differences and gaps as questions. Add to Sprint Question board 20 min Process
- 16. 45 min
- 17. Facilitator notes Make sure someone in the team understands and prepares this flow based on real user insights Example: Map the main interactions of customers and Siteminder in 5-10 steps on a whiteboard. Use boxes and arrows to describe flows, stickies to indicate pain points. ● Who are our main relevant users? ● What do they want to achieve (eg enjoy a stroll in the park without annoyance)? ● What is their starting point? ● Map out their interactions, systems they use, emotional states, pain points and opportunities along the journey. 45 min Process
- 19. Pirate Metrics – AAARRR Designed by Dave McClure, these can be used to measure funnel performance Awareness - how do customers know you exist? Acquisition - what channels do users come from? Activation - how many have a good first visit? Retention - do they re-visit over time? Referral - do they like it enough to tell their friends? Revenue - can you monetize any of this behavior? Objective Identifying what success looks like can help you to focus on the features that make the biggest impact to the customer’s experience. A framework can help you identify the right metrics. Google’s HEART Framework Measure the quality of user experience. Choose 2 or 3 that are the most important. Happiness - user attitude to the experience (e.g. Satisfaction, Ease of Use, NPS) Engagement - user involvement (e.g. number of site visits, photos uploaded, rooms booked) Adoption - gaining new active users (e.g. upgrades to new version, purchases per new user, additional products taken on) Retention - whether existing users are returning (e.g. # users active over time, customer churn) Task success - ability for users to easily complete the task without error (e.g. completion time, time to upload photos). Goals = what is success? Signals = what will tell you that? Metrics = number of signals you’re aiming for.
- 20. 90 min
- 21. We now bring everything we learned together and focus on solutions.This is a process. Take your time. Facilitator notes ● Don’t share notes until after the last exercise ● Ugly is ok ● Keep to the time limit to enforce thinking under constraint Workshop steps 1. Check what you know (20 min) Remind yourself of everything you already know about the problem. Go back to your walls and remember the research. Capture anything that is important. 2. Ideas (20 min) Transform the most important ideas into rough sketches (user flows, a screen, a diagram, headlines). 3. Crazy 8s (8 min) ● Give everyone an A4 piece of paper ● Fold it in half 3 times (giving you 8 sections) ● Take your strongest idea and sketch 8 variations of that idea in 8min ● If you are out of variations, pick the next best idea and sketch variations 4. Solution Sketch (45 min) Create a 1-5 panel storyboard of a preferred solution from the 8. Make it self explanatory and give it a catchy title 90 min Objective
- 23. Let’s Stay in Touch Sarah Atkinson training@pragma.team 0404 412 188 Get more guides and information under this QR code. Or visit www.pragma.team/learn-about-agile Too often teams feel disconnected from their leaders and the company's strategy and vision. We need to put a focus back on connecting the dancefloor with the balcony. “ ”