Code yo-ppt-no-notes
Download as PPTX, PDF•0 likes•134 views
The document discusses common issues that teams experience when using agile methodologies like Scrum and provides tips and tricks for remedying those issues from the perspective of Scrum Masters. It addresses issues like lack of documentation, broken feedback loops, poor communication, inefficient meetings, and lack of transparency. For each issue, it provides examples of how to formalize processes, document everything in a single source of truth, define clear communication channels, streamline meetings, and create a culture of openness. The overall message is that documentation, communication, and transparency are key to ensuring agile practices run smoothly.
Code yo-ppt-no-notes
- 1. LINDSAY CZOPUR | KAY VARACALLI SCRUM MASTERS | TURNING TECHNOLOGIES Tools and Tricks to Remedy Agile Issues
- 2. WHAT IS A SCRUM MASTER? Air Traffic Control Communications Department for Software Engineering The Fuzz Atlassian Admins
- 3. No Documentation Common Issues Teams Experience Broken Feedback Loops Poor Team Communication Inefficient Meetings Lack of Transparency
- 4. No Documentation Common Issues Teams Experience Broken Feedback Loops Poor Team Communication Inefficient Meetings Lack of Transparency
- 6. Formalizing Processes How to Decide What We Develop • No official process for how feedback becomes a feature • Documented step-by-step in Confluence • Now it is universal, no exceptions Forces everyone to follow the documented process.
- 7. Keeping a Paper Trail API Documentation • API request made in Jira and assigned • API documented in Confluence, sent for approval via email • Comments/concerns addressed in Confluence • Approved in Slack by emote to a pinned message • Scrum Masters send sign off from the teams via email Every step in the process is documented.
- 8. One System to Rule them All Tech Support Issues • Previously used multiple channels • Upgraded to Jira Service Desk, linked to Jira issues • Instructions documented in Confluence Everything is documented in one place.
- 10. No Documentation Common Issues Teams Experience Broken Feedback Loops Poor Team Communication Inefficient Meetings Lack of Transparency
- 12. User Groups Customer Advisory Board • Get a list of users and start sending invites • Documented their specific use • Phone calls, surveys, A/B testing • Devs on calls to gain customer perspective Customers just want to be heard. Developers want to hear our customers.
- 13. Pre-Made User Group UserTesting.com • Conduct testing/receive feedback from NEW users • Target your ideal audience Internal Stakeholders • Regular meetings with various departments • Gathering feedback- offers transparency Use the resources you have – and then some!
- 14. Page out of the Team Playbook Project Poster • Includes all details for a feature • Place to resolve concerns • Includes user journeys, mock-ups, feedback, links to Jira • Shared with everyone Keep the feedback loop organized.
- 15. No Documentation Common Issues Teams Experience Broken Feedback Loops Poor Team Communication Inefficient Meetings Lack of Transparency
- 17. How and When to Communicate Define Method/Means • API documentation approval? - Email • Server down? - Email and Slack • Standup? - Either GTM, Slack or in-person • Bug? - Jira • Customer issue? - Jira Service Desk Use the appropriate channel of communication.
- 18. Passive Communication Jira Boards • All development happens in Jira • Everyone has access to everything • Company roadmap Find one medium and stick to it.
- 19. No Documentation Common Issues Teams Experience Broken Feedback Loops Poor Team Communication Inefficient Meetings Lack of Transparency
- 21. What are they Good For? Every Meeting has a Goal • Clear agenda IN writing • Documentation sent in advance • Meeting leader Communication does NOT stop outside of meetings.
- 22. Adapt, Adapt, Adapt Shifting Standard Scrum Meetings • Eliminated several meetings with same goals • Eliminated story points • Constant evaluation Do what works best for your organization.
- 23. No Documentation Common Issues Teams Experience Broken Feedback Loops Poor Team Communication Inefficient Meetings Lack of Transparency
- 25. Creating a Culture of Openness Start Small, Dream Big • Share mockups, wireframes, and workflows • Full transparency as a company Establish best practices and spread them.
- 26. Getting Leaders on the Same Page Coordination/ Communication Key • Continuous conversation • Flowing ideas • Proper scaling • Avoiding decision bottlenecks Make sure the right people are all in the same room.
- 27. Growing a Culture of Openness Pay it Forward • Confluence for ALL company information • Jira for the company roadmap • Jira Service Desk for issues • Town Hall meetings Better to over-communicate than under-communicate.
- 28. What did we learn?
- 29. PRO TIPS Document Everything Trust No One Fix Your Feedback Loop Already Just Do It Communication Makes or Breaks Teams Make it Work Meetings != Progress Stop the Madness Be Transparent! Spill the Tea
- 30. Reminder: Adapt!
- 31. Thank You! LINDSAY CZOPUR | KAY VARACALLI SCRUM MASTERS | TURNING TECHNOLOGIES