Hello SAP Community,
🙂
In this post I want to try to sum up what else I am doing daily
as Scrum Master for my team. (Infrastructural/project specific work not taken into account)
When I asked the development team "what I should do for them", they came up with three things that I should take care of:
- Well-being at work and in the team
- Isolation in terms of "protection from the outside world"
- Faciliate Communication
After giving it some thought ... my daily activities can be summed up as follows:
- I take care of the Pipeline (automated tests functional, build agents working correct)
- I make sure JIRA is used correct (top of backlog orientation of the Scrum Team for exchanging work items, implementation and monitoring of JIRA/Git information flow)
- I coordindate meetings (Scrum Rituals and else, mediation, meeting minutes)
- I do some coaching (speaking skills [language barriers and how to effectivly speak], embracing potential in leading skills, teaching development skills or motivation by transporting the vision of the project)
- Besides being focused on transparency, I generally look out for any decision and communication faciliation
- I check for ideas from the team, and I do a comparison of the actual state of our project with its ideal state(Continuous Deployment and C. Development, self empowered team, detailed work description a couple of sprints in advance)
- I moderate a lot (help people make a point & summarize discussed items, skip to next topics to make sure everything is handled within the timebox: save time)
- I do meeting minutes (in regards to faciliate information, making information explicit)
- I am first contact for developer in regards to how to prepare and handle future work items (how to work down the sprint, when to take tickets from the backlog, when and what to do with slack time, supporting PO with refinment)
- I support the present workflow (how to code review, how to update a ticket, how to collaborate by creating sub tasks, how to search jira for related tickets to gather information)
- And take care of finished work item (templates and training for creating tickets, help refining follow-up tickets)
- I am removing impediments (what to do with technical problem [connection issues, monsoon issues], low quality hardware)
- I uncover issues of human nature (bad pronounciation, shy team members, stressfull sprints, unclear working items, protect team)
- I am keeping track on how tickets/epics are processed in the project (give implications to PO or Development Team, if workflow is getting disruptive)
- I am being a flow evangelist ("tickets or fix?" "Tickets are always the better fix, as they don't take a dev out of his current flow", enable documentation of issues, reference to earlier solutions, collective of linked tickets represents flow of an object through the project)
- I check the Dashboard (any new tickets/comments tell me about what is going on, and combined with the general knowledge it helps me to identify potential value)
- I create Overview Pages (Dashboards, clear documentation of past development work, graphical workflows for training purposes, JIRA views onto the project, support PO with epics description)
Any commenting/feedback/critics welcome! (but please don't be harsh grammer or punctuation wise.
😉 )
Best Regards,
Paul
