When Scrum Team doesn't love own mobile product

What to do when your Scrum Team doesn't feel engagement?

Transcript

1. When Scrum Team doesn’t love own mobile product Michał Aleksander Design Team Manager at Pearson English Technologies
2. A Story… …based on true experiences UX DESIGNER UX RESEARCHER SCRUM TEAM PRODUCT OWNER
3. This can happen in every company… When we can hear: “We’ve got Scrum” But in fact they are still “Business” prisoners in new kind of teams
4. CONTROL Trust me, I know We need more money NEED YOU My boss wants it My Roadmap I have a mortgage We know what and why TO WE
5. JUST DO IT.
6. THEN SCRUM TEAM MAY NOT BE IN LOVE WITH OWN PRODUCT
7. And it’s ready for affair…
8. HOW CAN WE CHANGE THAT?
9. THE TEAM NEEDS INFORMATION AND TRANSPARENCY
10. THE TEAM NEEDS TO UNDERSTAND WHY THEY DO THEIR JOB.
11. That’s why every Business Requirement should have an explanation. Sharing an information is not equal to lose control over product development.
12. THE TEAM NEEDS TO FOCUS ON VALUE
13. PRODUCT Tasks on Jira Code Review WHAT IS NOT Company WiFi Sprints Bounce rate Business Value OUR THIS IS
14. Users have needs and expectations but they also collect an experience from digital products…. …and no one wants to have bad memories
15. EVERYONE WANTS TO BE A PRODUCT DESIGNER NOWADAYS.
16. BUT WE ARE NOT USERS.
17. WE NEED TO FOCUS ON USERS.
18. FOCUSING ON SOMETHING DETERMINES WHAT VALUE WE CAN SEE.
19. THE TEAM NEEDS TO BE ENGAGED
20. YOU WILL BE SUPRISED BUT WE HAVE NEVER STOPPED BEING KIDS
21. AND KIDS WANT TO PLAY AND BE A PART OF A GROUP
22. The Team should be a part of design workshops. …and have to speak loud about technical limitations.
23. THE TEAM NEEDS TO BE TRUSTED
24. GIVE THEM A SPACE
25. THANK YOU QUESTIONS? MICHAL.ALEKSANDER@PEARSON.COM