Download as PDF, PPTX
Uploaded byAgile Austria Conference
AAC2025-Schanner_All_You_Need_is_Focus.pdf
In this talk, I’ll share how we improved our team’s workflow to better manage 20 people split into 2-4 sub-teams, working across a variety of products. While we were performing well, we recognized inefficiencies in prioritization, visibility, and ownership. By shifting our approach, we introduced a weekly focus, team collaboration, and visual progress tracking that empowered individuals to take responsibility for their work.
More Related Content
Similar to AAC2025-Schanner_All_You_Need_is_Focus.pdf
AAC2025-Schanner_All_You_Need_is_Focus.pdf
- 1. All You Needis Focus Replacing Tickets with Ownership Agile Austria 2025-01-31 Gabriel Schanner
- 2. What do wedo? • shopreme – Scan & Go provider • >55M App installs • ~ €52.5M transaction volume / per month • 650k users / per month
- 3. Why this talk? •Now ~20 people working on ~7 products • How we work • ... With agile principles at heart • Hopefully • Our pain is relatable • Our approaches are helpful
- 5. Supervisor App Handscanner Smartcart matrix (SCO) MobileSDK MGMT Console (Backend) vector (exit system) ~18 people PM/PO Mobile devs Backend devs, UI/UX QA/support
- 6. Setup • Main Challenges •Lots of releases/artifacts • “Awkward middle sized team” GS0
- 7. Folie 6 GS0 Unifythis with goals that come later Gabriel Schanner; 2025-01-28T23:16:55.819
- 8. …what happened sofar • Scrum mostly by the book • cycles had no natural overlap with any artifacts/releases • Team too large for single team • Estimations had no real benefit GS0
- 9. Folie 7 GS0 Nicevisualisation Gabriel Schanner; 2025-01-28T23:19:15.816
- 10. …what happened sofar • Weekly Kanban inspired (Scrumban) • Mixture of full-team and subteam meetings • Refinement by tech leads only
- 11. …what happened sofar • Introducing feature teams • Subteams in charge of larger epics • Recruited from anyone within larger team
- 12. All was well… •Feature teams worked • Stable subteams tackled smaller tickets • Low process overhead
- 13. …but it alwayscould be better • Growth pains • who worked on what with whom? • Jira sucked • Feature teams • Enable growth of team members (make big decisions ) • Increase ownership • Eliminate decision bottle necks • Build product knowledge and mindset • Reduce distractions • What was the Weekly increment • Releases • Hard to see if one is prepared or planning is ongoing? • When should QA test what? • Tracking of deployments • “Hypercare” phase after release using combined resources • A lot of valuable effort was hard to track in tickets • “Make Sure the shopper experience at this retailer is awesome” • “The big release next week needs to work” • “This feature is business critical and go from development to live” • “Talk to this partner, figure out how we can get a system running and make it so”
- 14. …but it alwayscould be better • Growth pains • who worked on what with whom? • Jira sucked • Feature teams • Enable growth of team members (make big decisions ) • Increase ownership • Eliminate decision bottle necks • Build product knowledge and mindset • Reduce distractions • What was the Weekly increment • Releases • Hard to see if one is prepared or planning is ongoing? • When should QA test what? • Tracking of deployments • “Hypercare” phase after release using combined resources • A lot of valuable effort was hard to track in tickets • “Make Sure the shopper experience at this retailer is awesome” • “The big release next week needs to work” • “This feature is business critical and go from development to live” • “Talk to this partner, figure out how we can get a system running and make it so”
- 15. Identifying the bigissues • Lots of issues • Separate symptoms from causes • Big One: • We thought the problem was team size • A lot of energy was wasted
- 16. Identifying the bigissues goals • We want to • work more efficiently as a team • distribute responsibilities better and foster ownership • improve competence of team • improve communication across teams • reduce focus switches • make work more visible
- 17. The Realization • Noteverything can be changed at once • BUT we want to start with a somewhat big cornerstone change
- 18. The Realization • Bigpositive learnings we had • Feature teams and direct communication worked very well • Try to make this default • …without bloating the process
- 19. The Realization • Wewent From Tickets to Focus • New central building block of team effort
- 20. Focus • Determines whatis the Person should work on • For 1 week • Can be related to ticket, but does not have to be • Can be large or small • BUT this is what is important and needs to be worked on • Change tooling
- 21. Focus • Determines whatis the Person should work on • For 1 week • Can be related to ticket, but does not have to be • Can be large or small • BUT this is what is important and needs to be worked on • Change tooling • Extremely underestimated difference maker
- 28. Focus on thedetails • Should ideally not span more than 1 week… • People should not have more than 2 focusses • Does not replace Jira but adds to it • Shown Everyday during the daily
- 29. Weekly Review • Insame FigJam Board • Growing visual timeline of product increment
- 37. Learnings • #LOVE • Easilyvisible what everyone is working on (together) • People know who to talk to – always • Progress and blockers very visible • Visual appeal motivates people • Business critical efforts easier to align • #needs-refinement • Jira is still required -> bit of duplicate effort • Roadmap planning still cumbersome
- 38. Thank you! • Andhave a great day! • And a big shoutout to the spr-team
- 39. Q & A •Anyone with similar adaptation experiences? • What worked for you? • Any recommendations on Roadmap Planning?
- 40. Q & A •Anyone with similar adaptation experiences? • What worked for you? • Any recommendations on Roadmap Planning? • See https://www.figma.com/board/T2i2c0gzfrVeCue 1fWS9Eo/spr-focus-excerpt?node-id=0- 1&t=Riqsies2SGw1Xs5C-1
- 41.
- 42. Clarity for Customer Clarityfor Employees Loss Prevention Dedicated exit hardware
- 43. Modern App -Style UI/UX Eco Receipt CC Detail Tokenization Remote Age Verification Self-Checkout Kiosk
- 44. Employee App Overview ofall baskets in real time Notifications if action is due Spot Checks Risk Assessment Offline-Check CUSTOMER BASKET AUDIT AGE VERIFICATION QR Code appears Employee scans code Employee checks age
- 45. Reporting Real Data In-StoreAnalytics • Prevented loss • Rule-based selections vs AI selections • Type of prevented loss (not scanned, wrong quantity, product mixup) • Customer waiting time & process time