Project timeframe issue
Clash Royale CLAN TAG#URR8PPP
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;
up vote
4
down vote
favorite
I have recently been promoted to team lead. My project manager is assigning a new project to me along with two team members. I have discussed the project scope and efforts with project manager and proposed 45 working days to deliver the project. But my project manager is asking me to deliver it within 28 working days.
I have discussed this with the project manger but he is not listening to me. What should I do now?
project-management time-management
add a comment |Â
up vote
4
down vote
favorite
I have recently been promoted to team lead. My project manager is assigning a new project to me along with two team members. I have discussed the project scope and efforts with project manager and proposed 45 working days to deliver the project. But my project manager is asking me to deliver it within 28 working days.
I have discussed this with the project manger but he is not listening to me. What should I do now?
project-management time-management
Dealing with unreasonable deadlines. How do you push back against unreasonable demands without offending your superiors?
– Dukeling
Apr 27 '14 at 11:47
Is it possible to cut out or simplify some of the deliverables?
– La-comadreja
Apr 27 '14 at 13:15
1
Did the PM give a reason for refusing to back away for 45 days? If you don't know why the PM refuses to back away, then you can't attack the reason the PM is not backing away. There is a huge difference between a PM's ego trip as the reason, and a contractual obligation to deliver within 28 days. If it is a contractual obligation, then you might have to ask for more resources. And "resources" may include someone who has put more time in as team lead that you have and who knows, for example, where the re-usable code is, who the fast coders are, and what the acceptable shortcuts are.
– Vietnhi Phuvan
Apr 27 '14 at 14:41
I agree with @Joe Strazzere. Let's make a baby in one month with nine women.
– Jim G.
Apr 27 '14 at 20:43
add a comment |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I have recently been promoted to team lead. My project manager is assigning a new project to me along with two team members. I have discussed the project scope and efforts with project manager and proposed 45 working days to deliver the project. But my project manager is asking me to deliver it within 28 working days.
I have discussed this with the project manger but he is not listening to me. What should I do now?
project-management time-management
I have recently been promoted to team lead. My project manager is assigning a new project to me along with two team members. I have discussed the project scope and efforts with project manager and proposed 45 working days to deliver the project. But my project manager is asking me to deliver it within 28 working days.
I have discussed this with the project manger but he is not listening to me. What should I do now?
project-management time-management
edited Apr 27 '14 at 17:42
yoozer8
4,10442955
4,10442955
asked Apr 27 '14 at 11:31
Jagz W
1244
1244
Dealing with unreasonable deadlines. How do you push back against unreasonable demands without offending your superiors?
– Dukeling
Apr 27 '14 at 11:47
Is it possible to cut out or simplify some of the deliverables?
– La-comadreja
Apr 27 '14 at 13:15
1
Did the PM give a reason for refusing to back away for 45 days? If you don't know why the PM refuses to back away, then you can't attack the reason the PM is not backing away. There is a huge difference between a PM's ego trip as the reason, and a contractual obligation to deliver within 28 days. If it is a contractual obligation, then you might have to ask for more resources. And "resources" may include someone who has put more time in as team lead that you have and who knows, for example, where the re-usable code is, who the fast coders are, and what the acceptable shortcuts are.
– Vietnhi Phuvan
Apr 27 '14 at 14:41
I agree with @Joe Strazzere. Let's make a baby in one month with nine women.
– Jim G.
Apr 27 '14 at 20:43
add a comment |Â
Dealing with unreasonable deadlines. How do you push back against unreasonable demands without offending your superiors?
– Dukeling
Apr 27 '14 at 11:47
Is it possible to cut out or simplify some of the deliverables?
– La-comadreja
Apr 27 '14 at 13:15
1
Did the PM give a reason for refusing to back away for 45 days? If you don't know why the PM refuses to back away, then you can't attack the reason the PM is not backing away. There is a huge difference between a PM's ego trip as the reason, and a contractual obligation to deliver within 28 days. If it is a contractual obligation, then you might have to ask for more resources. And "resources" may include someone who has put more time in as team lead that you have and who knows, for example, where the re-usable code is, who the fast coders are, and what the acceptable shortcuts are.
– Vietnhi Phuvan
Apr 27 '14 at 14:41
I agree with @Joe Strazzere. Let's make a baby in one month with nine women.
– Jim G.
Apr 27 '14 at 20:43
Dealing with unreasonable deadlines. How do you push back against unreasonable demands without offending your superiors?
– Dukeling
Apr 27 '14 at 11:47
Dealing with unreasonable deadlines. How do you push back against unreasonable demands without offending your superiors?
– Dukeling
Apr 27 '14 at 11:47
Is it possible to cut out or simplify some of the deliverables?
– La-comadreja
Apr 27 '14 at 13:15
Is it possible to cut out or simplify some of the deliverables?
– La-comadreja
Apr 27 '14 at 13:15
1
1
Did the PM give a reason for refusing to back away for 45 days? If you don't know why the PM refuses to back away, then you can't attack the reason the PM is not backing away. There is a huge difference between a PM's ego trip as the reason, and a contractual obligation to deliver within 28 days. If it is a contractual obligation, then you might have to ask for more resources. And "resources" may include someone who has put more time in as team lead that you have and who knows, for example, where the re-usable code is, who the fast coders are, and what the acceptable shortcuts are.
– Vietnhi Phuvan
Apr 27 '14 at 14:41
Did the PM give a reason for refusing to back away for 45 days? If you don't know why the PM refuses to back away, then you can't attack the reason the PM is not backing away. There is a huge difference between a PM's ego trip as the reason, and a contractual obligation to deliver within 28 days. If it is a contractual obligation, then you might have to ask for more resources. And "resources" may include someone who has put more time in as team lead that you have and who knows, for example, where the re-usable code is, who the fast coders are, and what the acceptable shortcuts are.
– Vietnhi Phuvan
Apr 27 '14 at 14:41
I agree with @Joe Strazzere. Let's make a baby in one month with nine women.
– Jim G.
Apr 27 '14 at 20:43
I agree with @Joe Strazzere. Let's make a baby in one month with nine women.
– Jim G.
Apr 27 '14 at 20:43
add a comment |Â
2 Answers
2
active
oldest
votes
up vote
5
down vote
- Create a fairly detailed schedule with specific tasks, deliverables, execution times and dependencies (you probably already have that)
- Review with the project manager. Ask "where do you think my time estimates are off?", "what tasks could be skipped or streamlined?", "how do you suggest we compress this to 28 days?"
- Provide options and alternatives. These could be adding more people, dropping features or deliverable, staggering deliverables (so you have the important stuff after 28 days and the whole thing after 45 days), etc
This sounds a very good idea...I will do the same and share PM response in next couple of days with you. Thanks a ton
– Jagz W
Apr 27 '14 at 14:36
add a comment |Â
up vote
2
down vote
Fast, cheap, good. Pick two. This is the reality of project work.
Have a high-level goal-oriented conversation with the PM. Ask him why he has the 28-day deadline. Find out his business goals and try to figure out how to make him successful. Promising 28 days and delivering in 45 will not make him successful. Make the project manager into your ally and make yourself into his ally.
(If his business goal is to prove you are an incompetent idiot, because he's been burned by project workers many times, he has a hard problem. It's not a problem you can solve for him. But you should still do your best to make his project successful even over his opposition.)
Resist the temptation to whip out your detailed schedule to prove you can't make 28 days. Even if it's true, it won't help. People don't react well when you try to prove they're wrong. They do react well when you say "together let's make this work."
Once you understand the PM's real needs, get his permission to share them with your team. Make sure everybody is working to meet those real needs.
If fast (28 days) is legitimately immovable because of some business problem, then you and the PM can sacrifice either cheap (by spending more money or labor) or good (by dropping parts of the requirements, or by declaring schedule victory before you've completed the end-of-project punch list).
add a comment |Â
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
5
down vote
- Create a fairly detailed schedule with specific tasks, deliverables, execution times and dependencies (you probably already have that)
- Review with the project manager. Ask "where do you think my time estimates are off?", "what tasks could be skipped or streamlined?", "how do you suggest we compress this to 28 days?"
- Provide options and alternatives. These could be adding more people, dropping features or deliverable, staggering deliverables (so you have the important stuff after 28 days and the whole thing after 45 days), etc
This sounds a very good idea...I will do the same and share PM response in next couple of days with you. Thanks a ton
– Jagz W
Apr 27 '14 at 14:36
add a comment |Â
up vote
5
down vote
- Create a fairly detailed schedule with specific tasks, deliverables, execution times and dependencies (you probably already have that)
- Review with the project manager. Ask "where do you think my time estimates are off?", "what tasks could be skipped or streamlined?", "how do you suggest we compress this to 28 days?"
- Provide options and alternatives. These could be adding more people, dropping features or deliverable, staggering deliverables (so you have the important stuff after 28 days and the whole thing after 45 days), etc
This sounds a very good idea...I will do the same and share PM response in next couple of days with you. Thanks a ton
– Jagz W
Apr 27 '14 at 14:36
add a comment |Â
up vote
5
down vote
up vote
5
down vote
- Create a fairly detailed schedule with specific tasks, deliverables, execution times and dependencies (you probably already have that)
- Review with the project manager. Ask "where do you think my time estimates are off?", "what tasks could be skipped or streamlined?", "how do you suggest we compress this to 28 days?"
- Provide options and alternatives. These could be adding more people, dropping features or deliverable, staggering deliverables (so you have the important stuff after 28 days and the whole thing after 45 days), etc
- Create a fairly detailed schedule with specific tasks, deliverables, execution times and dependencies (you probably already have that)
- Review with the project manager. Ask "where do you think my time estimates are off?", "what tasks could be skipped or streamlined?", "how do you suggest we compress this to 28 days?"
- Provide options and alternatives. These could be adding more people, dropping features or deliverable, staggering deliverables (so you have the important stuff after 28 days and the whole thing after 45 days), etc
answered Apr 27 '14 at 13:25
Hilmar
23.1k65770
23.1k65770
This sounds a very good idea...I will do the same and share PM response in next couple of days with you. Thanks a ton
– Jagz W
Apr 27 '14 at 14:36
add a comment |Â
This sounds a very good idea...I will do the same and share PM response in next couple of days with you. Thanks a ton
– Jagz W
Apr 27 '14 at 14:36
This sounds a very good idea...I will do the same and share PM response in next couple of days with you. Thanks a ton
– Jagz W
Apr 27 '14 at 14:36
This sounds a very good idea...I will do the same and share PM response in next couple of days with you. Thanks a ton
– Jagz W
Apr 27 '14 at 14:36
add a comment |Â
up vote
2
down vote
Fast, cheap, good. Pick two. This is the reality of project work.
Have a high-level goal-oriented conversation with the PM. Ask him why he has the 28-day deadline. Find out his business goals and try to figure out how to make him successful. Promising 28 days and delivering in 45 will not make him successful. Make the project manager into your ally and make yourself into his ally.
(If his business goal is to prove you are an incompetent idiot, because he's been burned by project workers many times, he has a hard problem. It's not a problem you can solve for him. But you should still do your best to make his project successful even over his opposition.)
Resist the temptation to whip out your detailed schedule to prove you can't make 28 days. Even if it's true, it won't help. People don't react well when you try to prove they're wrong. They do react well when you say "together let's make this work."
Once you understand the PM's real needs, get his permission to share them with your team. Make sure everybody is working to meet those real needs.
If fast (28 days) is legitimately immovable because of some business problem, then you and the PM can sacrifice either cheap (by spending more money or labor) or good (by dropping parts of the requirements, or by declaring schedule victory before you've completed the end-of-project punch list).
add a comment |Â
up vote
2
down vote
Fast, cheap, good. Pick two. This is the reality of project work.
Have a high-level goal-oriented conversation with the PM. Ask him why he has the 28-day deadline. Find out his business goals and try to figure out how to make him successful. Promising 28 days and delivering in 45 will not make him successful. Make the project manager into your ally and make yourself into his ally.
(If his business goal is to prove you are an incompetent idiot, because he's been burned by project workers many times, he has a hard problem. It's not a problem you can solve for him. But you should still do your best to make his project successful even over his opposition.)
Resist the temptation to whip out your detailed schedule to prove you can't make 28 days. Even if it's true, it won't help. People don't react well when you try to prove they're wrong. They do react well when you say "together let's make this work."
Once you understand the PM's real needs, get his permission to share them with your team. Make sure everybody is working to meet those real needs.
If fast (28 days) is legitimately immovable because of some business problem, then you and the PM can sacrifice either cheap (by spending more money or labor) or good (by dropping parts of the requirements, or by declaring schedule victory before you've completed the end-of-project punch list).
add a comment |Â
up vote
2
down vote
up vote
2
down vote
Fast, cheap, good. Pick two. This is the reality of project work.
Have a high-level goal-oriented conversation with the PM. Ask him why he has the 28-day deadline. Find out his business goals and try to figure out how to make him successful. Promising 28 days and delivering in 45 will not make him successful. Make the project manager into your ally and make yourself into his ally.
(If his business goal is to prove you are an incompetent idiot, because he's been burned by project workers many times, he has a hard problem. It's not a problem you can solve for him. But you should still do your best to make his project successful even over his opposition.)
Resist the temptation to whip out your detailed schedule to prove you can't make 28 days. Even if it's true, it won't help. People don't react well when you try to prove they're wrong. They do react well when you say "together let's make this work."
Once you understand the PM's real needs, get his permission to share them with your team. Make sure everybody is working to meet those real needs.
If fast (28 days) is legitimately immovable because of some business problem, then you and the PM can sacrifice either cheap (by spending more money or labor) or good (by dropping parts of the requirements, or by declaring schedule victory before you've completed the end-of-project punch list).
Fast, cheap, good. Pick two. This is the reality of project work.
Have a high-level goal-oriented conversation with the PM. Ask him why he has the 28-day deadline. Find out his business goals and try to figure out how to make him successful. Promising 28 days and delivering in 45 will not make him successful. Make the project manager into your ally and make yourself into his ally.
(If his business goal is to prove you are an incompetent idiot, because he's been burned by project workers many times, he has a hard problem. It's not a problem you can solve for him. But you should still do your best to make his project successful even over his opposition.)
Resist the temptation to whip out your detailed schedule to prove you can't make 28 days. Even if it's true, it won't help. People don't react well when you try to prove they're wrong. They do react well when you say "together let's make this work."
Once you understand the PM's real needs, get his permission to share them with your team. Make sure everybody is working to meet those real needs.
If fast (28 days) is legitimately immovable because of some business problem, then you and the PM can sacrifice either cheap (by spending more money or labor) or good (by dropping parts of the requirements, or by declaring schedule victory before you've completed the end-of-project punch list).
answered Apr 27 '14 at 14:11
O. Jones
13.6k24070
13.6k24070
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f23231%2fproject-timeframe-issue%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Dealing with unreasonable deadlines. How do you push back against unreasonable demands without offending your superiors?
– Dukeling
Apr 27 '14 at 11:47
Is it possible to cut out or simplify some of the deliverables?
– La-comadreja
Apr 27 '14 at 13:15
1
Did the PM give a reason for refusing to back away for 45 days? If you don't know why the PM refuses to back away, then you can't attack the reason the PM is not backing away. There is a huge difference between a PM's ego trip as the reason, and a contractual obligation to deliver within 28 days. If it is a contractual obligation, then you might have to ask for more resources. And "resources" may include someone who has put more time in as team lead that you have and who knows, for example, where the re-usable code is, who the fast coders are, and what the acceptable shortcuts are.
– Vietnhi Phuvan
Apr 27 '14 at 14:41
I agree with @Joe Strazzere. Let's make a baby in one month with nine women.
– Jim G.
Apr 27 '14 at 20:43