> but I would feel guilty slacking off all day. What do I do? Raise your quality bar. Work on things that are peripheral to the original issue but makes everyo

> but I would feel guilty slacking off all day. What do I do? Raise your quality bar. Work on things that are peripheral to the original issue but makes everyone's lives better. Improve effectiveness of testing, make invalid situations impossible or unlikely to arise. Document what you learn, which is ideally done when information is new to you. Another thing you can do is pair with some of the other devs. Maybe you can offer some insights that make their work go more smoothly, or maybe you'll get some context as to what complications exist that aren't in the original estimate. The only good use for points anywhere I've worked was that we could measure 'firefighting hours' per sprint for the whole team relative to the stories that got done. I wish there was a way of connecting slow delivery with tech debt to allow focusing on reducing it. OTOH I've also worked at a supposed-tech-startup where other team members were literally telling me not to work so hard, it's making everyone look bad.