Context

1. recently started work in an enterprise company
2. work could be called platform engineering
3. mostly work with pipelines, managing the operations for the downstream application, ensuring optimal developer experience for application developers, managing the developer portal (we use Tyk), integrating with observability services (ELK), quarkus extension monorepo for downstream applications (we only support quarkus applications)
4. based on that, it already sounds like quite a lot, there is still more that i wont list, but my point is just that we're not maintaining like 3 applications in total, which is more similar to the work that i used to do before, there is a lot of context switching required in my current job

Planning

1. scrum is good, i enjoyed using it a lot in smaller teams
2. however now i am in a big team (20-40 people)
3. scrum is difficult to employ in the format that i was used to
4. so this required me to figure out a way to manage the work

How to manage the work and plan better

1. there are always some questions coming in from people that work on the periphery of the services we employ within our team
2. these are usually hard to plan
3. additionally, since i still feel relatively new due to the complexity of the environments we work with, planning is also difficult to do when people just kind of go with it, during scrum rituals
   1. the size of our team doesn't help here
4. so in order to plan appropriately;
   1. when someone asks question
   2. figure out if big task or small task
   3. if big task,
      1. create ticket
      2. inform person that asked the question
      3. plan it with team
   4. if small task,
      1. just do it if you have time
      2. otherwise, create ticket!!
5. yeah thats it, just create the tickets
   1. if people say but nothing gets done, that's just not true
   2. this works for me because i dont want to not do it, i like my work
   3. but i cant do everything all at once
   4. i need to focus and id rather not context switch too often

Why create tickets? What are the benefits of this

1. this gives you the opportunity to go over it with your team during scrum rituals
2. ideally should cover blind spots, which, as someone relatively new, is usually nice
3. the scrum rituals in our work are at regular intervals, and everyone is present anyway, so why not use it to your own benefit
4. additionally, makes it clear to the person that asked the question that their request is being taken further or something like that - which is better than forgetting to do the thing because you're already busy with many other things

end

1. its nice if this brain dump helps anyone