Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
Hazarth94863y@true-dev001
Tip #2 don't put a lot of new people on tight projects, long-term existing teams work best...
But I don't think that's anything you can change so lemme try and give you an actually useful tip
Talk with your manager or leads if you think the deadline wont be met or might be tight. Usually there's extra time allocated that the devs don't really know about, so it might be less tight than you think
If not, then you can try telling them if It's possible to shift it a bit
If management is not the way for you then really the best thing you could probably do is talk to your lead or take charge and try to organize work better, split tasks in a way that can maximize parallel work.
And for personal Tips, all you can do is organize your work, put in the time and effort as best as you can, you can put in some overtime if asked to, but always remember that your own health is a priority. If the project is late then realistically nothing will really happen to you, slow and steady -
Nihil757553yfocus on completing the end-to-end flow first, even with mocked inputs/modifiers, then start filling the gaps adding functionality.
-
Ask if it's actually a hard deadline. If you have 10 features planned - would you launch on the deadline date even if only 7 features are done?
I often get the answer "no" and find out that the deadline is actually soft. -
When I think back on missed deadlines;
* We waited too long to ask for extra resources. They were brought in too late. Should've been brought in instantly as the project got a deadline and became more important than what they were doing. Finishing early wouldn't have been an issues.
* We pushed back "easy" but essential features for too long and got stuck on complex but less essential features. Probably could've launched an MVP on the deadline date if we focused on essentials first.
* We allowed the stakeholders to add changes up until the final days instead of reserving the last week for review, clean up, tests and fixes.
Related Rants
How to work when a project has tight deadlines, give me some tricks of yours?
rant
questions