Deployments and deployment frequency pretty squarely a developer's responsibility...
Starting a project early enough to deploy on time is a management responsibility.
Best I can do is add 3 tickets during Monday's scrum
("What do you mean your tickets slipped again?)
Yall aren't being told to write your own tickets?
Nah we get given tickets.
The tickets only have an ambiguous title, then it's our responsibility to figure out what it's about and come up with the estimates.
After our weekly planning meeting
Give me a perfect spec and I'll give a perfect timeline
No you won't, because even if everything is perfectly specced you'll encounter unforeseen issues during implementation. So you'll either overestimate or underestimate the time required.
Deployments and deployment frequency pretty squarely a developer's responsibility...
Starting a project early enough to deploy on time is a management responsibility.
Best I can do is add 3 tickets during Monday's scrum
("What do you mean your tickets slipped again?)
Yall aren't being told to write your own tickets?
Nah we get given tickets.
The tickets only have an ambiguous title, then it's our responsibility to figure out what it's about and come up with the estimates.
After our weekly planning meeting
Give me a perfect spec and I'll give a perfect timeline
No you won't, because even if everything is perfectly specced you'll encounter unforeseen issues during implementation. So you'll either overestimate or underestimate the time required.
Our mind reading powers can only go so far.