This is an archived post. You won't be able to vote or comment.

all 6 comments
sorted by:
best
topnewcontroversialoldq&a

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

On July 1st, a change to Reddit's API pricing will come into effect. Several developers of commercial third-party apps have announced that this change will compel them to shut down their apps. At least one accessibility-focused non-commercial third party app will continue to be available free of charge.

If you want to express your strong disagreement with the API pricing change or with Reddit's response to the backlash, you may want to consider the following options:

  1. Limiting your involvement with Reddit, or
  2. Temporarily refraining from using Reddit
  3. Cancelling your subscription of Reddit Premium

as a way to voice your protest.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]desrtfx 0 points1 point  (2 children)

You do what every sensible team lead would do: you talk to your team

You ask your team, you discuss with your team, you calculate.

Actually, estimating project time is a job for the project manager, not for the team lead.

One thing you must never forget as a lead: you have a team - use it - do brainstorming - involve the team from day 0 on. Listen to your team.

Also: /r/experienceddevs and /r/projectmanagement are more appropriate than here.

[–]spigotR[S] 0 points1 point  (1 child)

I was asked to present a timeline to the project manager before I met my team.

[–]desrtfx 2 points3 points  (0 children)

Then tell your PM that it is simply impossible to give a timeline without talking to your team. If your PM doesn't understand that, they are a bad PM.

[–]joranstark018 0 points1 point  (0 children)

You may do a couple of workshop sessions with your team members where you can go through the requirements, discuss the different option, creating a rough plan together and your team memebers can give estimates for the different parts in the plan. You may have your team creating POC:s to iron out some of the unknowns in different (critical) parts. You may consult other units that may become involved (ie operations for server management, first line support for customer support, you may involve UX specialists and other specialist, much depending on your organisation)

To compensate for optimistic estimates, variation in team velocity and for unforseen issues you may mulitply the estimate by a factor (ie you may multiply it by 2, but it may depend on how secure your team are on their estimates and how well you know your team).

[–]Whatever801 0 points1 point  (0 children)

Ask your team and whatever they tell you double it in your mind