I've been keeping track of how much time I spend getting context for my tasks, and it's anywhere from 20 to 45 minutes per ticket. This includes reading the ticket description in Jira, checking related pull requests, looking at Slack discussions, and often asking the project manager what 'done' actually looks like. Is this typical for others in this field? How do you manage this process? Do you just accept it, or have you come up with strategies that help streamline things?
5 Answers
It really depends on the day and the specific ticket. Some days I can work through several similar issues quickly because I know what to look for. But often, I find I understand only about 20% of the requests right off the bat, necessitating follow-ups.
In my experience, getting context is actually more valuable than jumping into coding right away. If you start coding without the right information, you might end up spending way more time fixing problems down the line. I've learned to summarize what I think the ticket entails right in the comments, which helps clarify my understanding and catch any misconceptions early.
It definitely varies depending on who created the ticket. Some folks write them clearly, while others leave you guessing. Honestly, your job includes understanding the context—if everything were laid out perfectly, would you even need to be there? If the ticket lacks clear acceptance criteria, it's up to you to figure it out, so don't see this as wasted time!
I think taking the time to read and gather context is crucial. I've found that misinterpreting a ticket can lead to hours of wasted effort, so investing some time to get it right upfront is worth it. I usually have dedicated sprint planning meetings with my team to make sure we gather as much relevant context as possible.
Exactly! I believe it saves time in the long run, especially when changes come back to bite us due to poor understanding upfront.
Yeah, context-switching can be time-consuming! In my small team, if a ticket is lengthy, I sometimes throw it into ChatGPT for a summary. It’s not a complete replacement, but it gives me a quicker idea and speeds up my understanding without skipping the necessary reading later.
Absolutely! It’s a good habit to make sure everyone is aligned before diving into the code. A few minutes spent on context can save a ton of time later.