How to justify a team increase when the team is doing good?How can I encourage a culture of punctuality in a...
Would Taiwan and China's dispute be solved if Taiwan gave up being the Republic of China?
Late 1970's and 6502 chip facilities for operating systems
Functional analysis of the Pink Panther
Is it possible to encode a message in such a way that can only be read by someone or something capable of seeing into the very near future?
Cut a cake into 3 equal portions with only a knife
What Secular Civic Space Would Pioneers Build For Small Frontier Towns?
Why is (inf + 0j)*1 == inf + nanj?
What benefits does the Power Word Kill spell have?
Is it really necessary to have a four hour meeting in Sprint planning?
Detect duplicates without exposing underlying data
What do you do if you have developments on your paper during the long peer review process?
Is this a Sherman, and if so what model?
My Project Manager does not accept carry-over in Scrum, Is that normal?
Can "dès que" imply simultaneity ?
Is it more effective to add yeast before or after kneading?
What's the story to "WotC gave up on fixing Polymorph"?
Two trains move towards each other, a bird moves between them. How many trips can the bird make?
To what extent is it worthwhile to report check fraud / refund scams?
Line segments inside a square
Safe to use 220V electric clothes dryer when building has been bridged down to 110V?
What exactly did this mechanic sabotage on the American Airlines 737, and how dangerous was it?
Does "as soon as" imply simultaneity?
My manager quit. Should I agree to defer wage increase to accommodate budget concerns?
How can this Stack Exchange site have an animated favicon?
How to justify a team increase when the team is doing good?
How can I encourage a culture of punctuality in a software company?How can I learn from Senior team member who has fear of being replaced?How to deal with upper management that's taking advantage of an excellent hire?How to communicate that the root cause of a problem is a manager's leadership style?As a scrum master, how do I get everyone to take deadlines seriously?Team member seems to be focusing on everything except core responsibilitiesHow to deal with someone taking all the creditHow to politely ask “pretentious” engineers to simplify language
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I've been working in a large IT company in a 2 man team, for the past 3 years. We are very dedicated and we have a strong image as serious and reliable. Every important development comes our way.
The number of projects has increased and it's getting harder and harder to split our focus between multiple projects (having a high degree of parallelism - and this will start to affect our output eventually).
We've been asking for a team increase, but since we deliver in an acceptable manner, basically we've been told that there is no need, regardless of our stress and overtime.
Now, perhaps I don't know how to properly raise this issue in order to have better odds, so here is my question:
Question: How to properly justify a team increase given that we don't have an output issue? (we are delivering in an acceptable manner for now)
Some additional context information.
A nearby team (of 4 members), whose output is poor, got an additional member.
In terms of importance, my teams products are far more important than the other teams products. This makes it even more frustrating and strange to me (my intuition says: invest where the outcome is good, not vice versa).
software-industry human-resources team people-management
New contributor
add a comment
|
I've been working in a large IT company in a 2 man team, for the past 3 years. We are very dedicated and we have a strong image as serious and reliable. Every important development comes our way.
The number of projects has increased and it's getting harder and harder to split our focus between multiple projects (having a high degree of parallelism - and this will start to affect our output eventually).
We've been asking for a team increase, but since we deliver in an acceptable manner, basically we've been told that there is no need, regardless of our stress and overtime.
Now, perhaps I don't know how to properly raise this issue in order to have better odds, so here is my question:
Question: How to properly justify a team increase given that we don't have an output issue? (we are delivering in an acceptable manner for now)
Some additional context information.
A nearby team (of 4 members), whose output is poor, got an additional member.
In terms of importance, my teams products are far more important than the other teams products. This makes it even more frustrating and strange to me (my intuition says: invest where the outcome is good, not vice versa).
software-industry human-resources team people-management
New contributor
Just to clarify, by "increase" you mean you want another person on the team? I was confused at first because some times, "increase" is assumed to mean salary increase, i.e. raise. I thought you were trying to ask for everyone on the team to get a raise.
– dwizum
8 hours ago
Yes, by increase I mean having an additional team member. I don't know what is the better term to describe this.
– Claudiu A
8 hours ago
Is overtime paid, unpaid?
– Crosbonaught
6 hours ago
Unpaid. We are very passionate in what we do, which is why the suggestions below, to take less stories/tasks is very doable for us.
– Claudiu A
6 hours ago
add a comment
|
I've been working in a large IT company in a 2 man team, for the past 3 years. We are very dedicated and we have a strong image as serious and reliable. Every important development comes our way.
The number of projects has increased and it's getting harder and harder to split our focus between multiple projects (having a high degree of parallelism - and this will start to affect our output eventually).
We've been asking for a team increase, but since we deliver in an acceptable manner, basically we've been told that there is no need, regardless of our stress and overtime.
Now, perhaps I don't know how to properly raise this issue in order to have better odds, so here is my question:
Question: How to properly justify a team increase given that we don't have an output issue? (we are delivering in an acceptable manner for now)
Some additional context information.
A nearby team (of 4 members), whose output is poor, got an additional member.
In terms of importance, my teams products are far more important than the other teams products. This makes it even more frustrating and strange to me (my intuition says: invest where the outcome is good, not vice versa).
software-industry human-resources team people-management
New contributor
I've been working in a large IT company in a 2 man team, for the past 3 years. We are very dedicated and we have a strong image as serious and reliable. Every important development comes our way.
The number of projects has increased and it's getting harder and harder to split our focus between multiple projects (having a high degree of parallelism - and this will start to affect our output eventually).
We've been asking for a team increase, but since we deliver in an acceptable manner, basically we've been told that there is no need, regardless of our stress and overtime.
Now, perhaps I don't know how to properly raise this issue in order to have better odds, so here is my question:
Question: How to properly justify a team increase given that we don't have an output issue? (we are delivering in an acceptable manner for now)
Some additional context information.
A nearby team (of 4 members), whose output is poor, got an additional member.
In terms of importance, my teams products are far more important than the other teams products. This makes it even more frustrating and strange to me (my intuition says: invest where the outcome is good, not vice versa).
software-industry human-resources team people-management
software-industry human-resources team people-management
New contributor
New contributor
edited 8 hours ago
Claudiu A
New contributor
asked 8 hours ago
Claudiu AClaudiu A
1443 bronze badges
1443 bronze badges
New contributor
New contributor
Just to clarify, by "increase" you mean you want another person on the team? I was confused at first because some times, "increase" is assumed to mean salary increase, i.e. raise. I thought you were trying to ask for everyone on the team to get a raise.
– dwizum
8 hours ago
Yes, by increase I mean having an additional team member. I don't know what is the better term to describe this.
– Claudiu A
8 hours ago
Is overtime paid, unpaid?
– Crosbonaught
6 hours ago
Unpaid. We are very passionate in what we do, which is why the suggestions below, to take less stories/tasks is very doable for us.
– Claudiu A
6 hours ago
add a comment
|
Just to clarify, by "increase" you mean you want another person on the team? I was confused at first because some times, "increase" is assumed to mean salary increase, i.e. raise. I thought you were trying to ask for everyone on the team to get a raise.
– dwizum
8 hours ago
Yes, by increase I mean having an additional team member. I don't know what is the better term to describe this.
– Claudiu A
8 hours ago
Is overtime paid, unpaid?
– Crosbonaught
6 hours ago
Unpaid. We are very passionate in what we do, which is why the suggestions below, to take less stories/tasks is very doable for us.
– Claudiu A
6 hours ago
Just to clarify, by "increase" you mean you want another person on the team? I was confused at first because some times, "increase" is assumed to mean salary increase, i.e. raise. I thought you were trying to ask for everyone on the team to get a raise.
– dwizum
8 hours ago
Just to clarify, by "increase" you mean you want another person on the team? I was confused at first because some times, "increase" is assumed to mean salary increase, i.e. raise. I thought you were trying to ask for everyone on the team to get a raise.
– dwizum
8 hours ago
Yes, by increase I mean having an additional team member. I don't know what is the better term to describe this.
– Claudiu A
8 hours ago
Yes, by increase I mean having an additional team member. I don't know what is the better term to describe this.
– Claudiu A
8 hours ago
Is overtime paid, unpaid?
– Crosbonaught
6 hours ago
Is overtime paid, unpaid?
– Crosbonaught
6 hours ago
Unpaid. We are very passionate in what we do, which is why the suggestions below, to take less stories/tasks is very doable for us.
– Claudiu A
6 hours ago
Unpaid. We are very passionate in what we do, which is why the suggestions below, to take less stories/tasks is very doable for us.
– Claudiu A
6 hours ago
add a comment
|
4 Answers
4
active
oldest
votes
Question: How to properly justify a team increase given that we don't have an output issue? (we are delivering in an acceptable manner already)
Stop working overtime and see if your team can still deliver in an acceptable manner. By working overtime, you are simply adding hours of work to each member of the team, which is not much different than those being the hours worked by a new team member. The downside to working overtime is that you are stressed and probably will eventually burn out. So, stop working overtime and then evaluate if you still need a new team member.
5
Since a month ago we have just decided to do this - no more overtime - exactly because of burnout.
– Claudiu A
8 hours ago
4
@ClaudiuA - Do you have metrics showing the growth in your backlog? You want to show what your burndown rate is on average per week, as well as your growth in backlog over time. From there you get points per person, and you will need to show that either the delay is unacceptable (you get this from other teams) or the growth rate in the backlog exceeds about half a person.
– Julie in Austin
6 hours ago
1
We've migrated to Jira a little while so the historical data is not great for seeing the increase on hard metrics. I could however get the growth of the backlog for the last 6-12 months and also calculate the points per person for recent months. This is a really good ideea as it can show the difference in pressure on team member over time which is solid proof for our need
– Claudiu A
6 hours ago
add a comment
|
A nearby team (of 4 members), whose output is poor, got an additional member.
This is a potential red flag for me. Of course, some of the times, the output deficiency is due to not having enough staff, in which case it makes sense to add headcount and continue monitoring output. But if there's a more general pattern of rewarding poor-performing teams with headcount, while high-performing teams are left to do "hero" work, that's toxic.
Further: Regardless of what's going on with the other team, a work environment that has handwaves away the very real problem of ongoing "heroic effort" is, in itself, toxic. It leads to mistakes & rework, burnout, low morale, turnover, etc., all of which are costly to the business in the long run. Of course, sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm.
We've been asking for a team increase, but since we deliver in an acceptable manner, basically we've been told that there is no need, regardless of our stress and overtime.
The way you deal with this is probably in your planning sessions. Assuming you're following some sort of sprint/agile development, commit to reasonable sprint points that don't require heroic efforts (routine after-hours or weekend work). Push back when product owners expect more features to be delivered in a given sprint.
You have past sprints to indicate that your team delivers X points in a 2-week sprint, you can't reasonably deliver X + 20 points in a 2-week sprint. If they insist on increased output, then you have metrics that justify your demand for additional headcount. If this is in flux, then it may be a part-time contractor rather, or maybe you loan someone over from another team/department that has extra bandwidth.
This is a bit of a passive approach, of course. But they've been passively trampling on your acceptance of increased workloads till now. You've unknowingly set expectations that you'll work overtime (if you're salaried, this is probably unpaid and mostly unrecognized, too!) and late nights and weekends to deliver. You need to slowly, but carefully back this expectation down to a more reasonable level.
New contributor
2
I'm glad it is a red flag for others as well. We are working Scrum (two man Scrum). I have to check what kind of metrics we can to use.
– Claudiu A
8 hours ago
The OP needs to demonstrate that the effort is actually "heroic" and not just "temporarily heavy". There are times when a little pain is to be expected, and a growing team is one of those times. Words like "toxic", "handwaves", "heroic" and "trampling" are usually seen as histrionic and not accurate. Remember - the step from 2 to 3 is 40 more person-hours per week, not 5 or 10.
– Julie in Austin
6 hours ago
I agree that it would help OP's case if they can demonstrate that the efforts have been both extraordinary and more than merely "occasional". That may be difficult to do, since salary positions rarely keep detailed logs of hours worked beyond the 40 required to avoid any flags in their HR applications :) Which is why I suggest taking more control over their sprint capacity.
– David Z
5 hours ago
As I clarified in my edit about an hour ago: "Sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm." It sounds like this is not a growing team, but a fixed team of 2 that have been denied requests for additional support. The challenge now is proving (with data, not feelings) that they're working at an unsustainable pace.
– David Z
5 hours ago
add a comment
|
Contact the right people
- HR, and there somebody that is truly engaged in wellbeing and has the power drive the change
- A senior manager that has enough experience and authority
- The source of the tasks
Do not undervalue soft power. A manager that is not necessarily that senior in the hierarchy can have seniority from the years of working valued, sometimes even connection at the top of the organisation.
Use other metrics to justify your case
- Overtime
- Action points per worker
- Number of projects you are working on
- People that have left
- Conversations about different career possibilities raised by the members
Also, remember to have some numbers from history.
Use the right words
- You are highly concerned about the wellbeing
- Your team is starting to lose their drive
- Any buzzword the HR is using for the issue works.
If they see only synonyms they might not recognise it as being important. The words the managers recognise for being held accountable in their scorecards.
I can have a meeting with a manager and I think this list can help me prepare very well. The metrics required are very easy to gather. Thanks!
– Claudiu A
7 hours ago
add a comment
|
Small teams are harder to justify a new team member because the increase in team size is greater. In your case, you are asking for a 50% increase in team size, relative to that other team which only received a 25% increase in size.
Unfortunately, unless you are consistently working more than 10-20% overtime each, that 50% bump is just going to be hard. What you need to show is that either you just can't handle the workload (it sounds like you can ...) or you are working so much overtime that it isn't sustainable.
The other answers rightly point out that what you're doing is somehow "wrong", but it is really only wrong in the long term and is unsustainable. From your employer's perspective it is better to have 2 employees working 110% than three employees working 75%. Two employees working 120-130% isn't sustainable. You need to quantify how how much you're doing and show that the work load is inappropriate and unsustainable.
Edited to add --
Just to clarify, the OP is in a sticky situation precisely because of the small team size. The only thing harder than adding the second team member is adding the second. An alternative to adding a full-time 3rd member is borrowing someone from another team. That's an approach my various teams have had to use to demonstrate "need".
Since the workload increases consistently, it will definitely become unsustainable. I can see a pattern from the answer: "start doing less" and I can see why.
– Claudiu A
8 hours ago
1
The issue remains -- adding a team member requires demonstrating that the existing team cannot handle it AND that the only solution is a 3rd team member who won't be idle most of the time. That may not be the case today, even if it will be at some point in the future.
– Julie in Austin
6 hours ago
add a comment
|
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "423"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/4.0/"u003ecc by-sa 4.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
noCode: true, onDemand: false,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Claudiu A is a new contributor. Be nice, and check out our Code of Conduct.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f145304%2fhow-to-justify-a-team-increase-when-the-team-is-doing-good%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
StackExchange.ready(function () {
$("#show-editor-button input, #show-editor-button button").click(function () {
var showEditor = function () {
$("#show-editor-button").addClass("d-none");
$("#post-form").removeClass("d-none");
StackExchange.editor.finallyInit();
};
var useFancy = $(this).data('confirm-use-fancy');
if (useFancy == 'True') {
var popupTitle = $(this).data('confirm-fancy-title');
var popupBody = $(this).data('confirm-fancy-body');
var popupAccept = $(this).data('confirm-fancy-accept-button');
$(this).loadPopup({
url: '/post/self-answer-popup',
loaded: function (popup) {
var pTitle = $(popup).find('h2');
var pBody = $(popup).find('.popup-body');
var pSubmit = $(popup).find('.popup-submit');
pTitle.text(popupTitle);
pBody.html(popupBody);
pSubmit.val(popupAccept).click(showEditor);
}
})
} else {
var confirmText = $(this).data('confirm-text');
if (confirmText ? confirm(confirmText) : true) {
showEditor();
}
}
});
});
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Question: How to properly justify a team increase given that we don't have an output issue? (we are delivering in an acceptable manner already)
Stop working overtime and see if your team can still deliver in an acceptable manner. By working overtime, you are simply adding hours of work to each member of the team, which is not much different than those being the hours worked by a new team member. The downside to working overtime is that you are stressed and probably will eventually burn out. So, stop working overtime and then evaluate if you still need a new team member.
5
Since a month ago we have just decided to do this - no more overtime - exactly because of burnout.
– Claudiu A
8 hours ago
4
@ClaudiuA - Do you have metrics showing the growth in your backlog? You want to show what your burndown rate is on average per week, as well as your growth in backlog over time. From there you get points per person, and you will need to show that either the delay is unacceptable (you get this from other teams) or the growth rate in the backlog exceeds about half a person.
– Julie in Austin
6 hours ago
1
We've migrated to Jira a little while so the historical data is not great for seeing the increase on hard metrics. I could however get the growth of the backlog for the last 6-12 months and also calculate the points per person for recent months. This is a really good ideea as it can show the difference in pressure on team member over time which is solid proof for our need
– Claudiu A
6 hours ago
add a comment
|
Question: How to properly justify a team increase given that we don't have an output issue? (we are delivering in an acceptable manner already)
Stop working overtime and see if your team can still deliver in an acceptable manner. By working overtime, you are simply adding hours of work to each member of the team, which is not much different than those being the hours worked by a new team member. The downside to working overtime is that you are stressed and probably will eventually burn out. So, stop working overtime and then evaluate if you still need a new team member.
5
Since a month ago we have just decided to do this - no more overtime - exactly because of burnout.
– Claudiu A
8 hours ago
4
@ClaudiuA - Do you have metrics showing the growth in your backlog? You want to show what your burndown rate is on average per week, as well as your growth in backlog over time. From there you get points per person, and you will need to show that either the delay is unacceptable (you get this from other teams) or the growth rate in the backlog exceeds about half a person.
– Julie in Austin
6 hours ago
1
We've migrated to Jira a little while so the historical data is not great for seeing the increase on hard metrics. I could however get the growth of the backlog for the last 6-12 months and also calculate the points per person for recent months. This is a really good ideea as it can show the difference in pressure on team member over time which is solid proof for our need
– Claudiu A
6 hours ago
add a comment
|
Question: How to properly justify a team increase given that we don't have an output issue? (we are delivering in an acceptable manner already)
Stop working overtime and see if your team can still deliver in an acceptable manner. By working overtime, you are simply adding hours of work to each member of the team, which is not much different than those being the hours worked by a new team member. The downside to working overtime is that you are stressed and probably will eventually burn out. So, stop working overtime and then evaluate if you still need a new team member.
Question: How to properly justify a team increase given that we don't have an output issue? (we are delivering in an acceptable manner already)
Stop working overtime and see if your team can still deliver in an acceptable manner. By working overtime, you are simply adding hours of work to each member of the team, which is not much different than those being the hours worked by a new team member. The downside to working overtime is that you are stressed and probably will eventually burn out. So, stop working overtime and then evaluate if you still need a new team member.
answered 8 hours ago
sf02sf02
23.7k14 gold badges49 silver badges89 bronze badges
23.7k14 gold badges49 silver badges89 bronze badges
5
Since a month ago we have just decided to do this - no more overtime - exactly because of burnout.
– Claudiu A
8 hours ago
4
@ClaudiuA - Do you have metrics showing the growth in your backlog? You want to show what your burndown rate is on average per week, as well as your growth in backlog over time. From there you get points per person, and you will need to show that either the delay is unacceptable (you get this from other teams) or the growth rate in the backlog exceeds about half a person.
– Julie in Austin
6 hours ago
1
We've migrated to Jira a little while so the historical data is not great for seeing the increase on hard metrics. I could however get the growth of the backlog for the last 6-12 months and also calculate the points per person for recent months. This is a really good ideea as it can show the difference in pressure on team member over time which is solid proof for our need
– Claudiu A
6 hours ago
add a comment
|
5
Since a month ago we have just decided to do this - no more overtime - exactly because of burnout.
– Claudiu A
8 hours ago
4
@ClaudiuA - Do you have metrics showing the growth in your backlog? You want to show what your burndown rate is on average per week, as well as your growth in backlog over time. From there you get points per person, and you will need to show that either the delay is unacceptable (you get this from other teams) or the growth rate in the backlog exceeds about half a person.
– Julie in Austin
6 hours ago
1
We've migrated to Jira a little while so the historical data is not great for seeing the increase on hard metrics. I could however get the growth of the backlog for the last 6-12 months and also calculate the points per person for recent months. This is a really good ideea as it can show the difference in pressure on team member over time which is solid proof for our need
– Claudiu A
6 hours ago
5
5
Since a month ago we have just decided to do this - no more overtime - exactly because of burnout.
– Claudiu A
8 hours ago
Since a month ago we have just decided to do this - no more overtime - exactly because of burnout.
– Claudiu A
8 hours ago
4
4
@ClaudiuA - Do you have metrics showing the growth in your backlog? You want to show what your burndown rate is on average per week, as well as your growth in backlog over time. From there you get points per person, and you will need to show that either the delay is unacceptable (you get this from other teams) or the growth rate in the backlog exceeds about half a person.
– Julie in Austin
6 hours ago
@ClaudiuA - Do you have metrics showing the growth in your backlog? You want to show what your burndown rate is on average per week, as well as your growth in backlog over time. From there you get points per person, and you will need to show that either the delay is unacceptable (you get this from other teams) or the growth rate in the backlog exceeds about half a person.
– Julie in Austin
6 hours ago
1
1
We've migrated to Jira a little while so the historical data is not great for seeing the increase on hard metrics. I could however get the growth of the backlog for the last 6-12 months and also calculate the points per person for recent months. This is a really good ideea as it can show the difference in pressure on team member over time which is solid proof for our need
– Claudiu A
6 hours ago
We've migrated to Jira a little while so the historical data is not great for seeing the increase on hard metrics. I could however get the growth of the backlog for the last 6-12 months and also calculate the points per person for recent months. This is a really good ideea as it can show the difference in pressure on team member over time which is solid proof for our need
– Claudiu A
6 hours ago
add a comment
|
A nearby team (of 4 members), whose output is poor, got an additional member.
This is a potential red flag for me. Of course, some of the times, the output deficiency is due to not having enough staff, in which case it makes sense to add headcount and continue monitoring output. But if there's a more general pattern of rewarding poor-performing teams with headcount, while high-performing teams are left to do "hero" work, that's toxic.
Further: Regardless of what's going on with the other team, a work environment that has handwaves away the very real problem of ongoing "heroic effort" is, in itself, toxic. It leads to mistakes & rework, burnout, low morale, turnover, etc., all of which are costly to the business in the long run. Of course, sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm.
We've been asking for a team increase, but since we deliver in an acceptable manner, basically we've been told that there is no need, regardless of our stress and overtime.
The way you deal with this is probably in your planning sessions. Assuming you're following some sort of sprint/agile development, commit to reasonable sprint points that don't require heroic efforts (routine after-hours or weekend work). Push back when product owners expect more features to be delivered in a given sprint.
You have past sprints to indicate that your team delivers X points in a 2-week sprint, you can't reasonably deliver X + 20 points in a 2-week sprint. If they insist on increased output, then you have metrics that justify your demand for additional headcount. If this is in flux, then it may be a part-time contractor rather, or maybe you loan someone over from another team/department that has extra bandwidth.
This is a bit of a passive approach, of course. But they've been passively trampling on your acceptance of increased workloads till now. You've unknowingly set expectations that you'll work overtime (if you're salaried, this is probably unpaid and mostly unrecognized, too!) and late nights and weekends to deliver. You need to slowly, but carefully back this expectation down to a more reasonable level.
New contributor
2
I'm glad it is a red flag for others as well. We are working Scrum (two man Scrum). I have to check what kind of metrics we can to use.
– Claudiu A
8 hours ago
The OP needs to demonstrate that the effort is actually "heroic" and not just "temporarily heavy". There are times when a little pain is to be expected, and a growing team is one of those times. Words like "toxic", "handwaves", "heroic" and "trampling" are usually seen as histrionic and not accurate. Remember - the step from 2 to 3 is 40 more person-hours per week, not 5 or 10.
– Julie in Austin
6 hours ago
I agree that it would help OP's case if they can demonstrate that the efforts have been both extraordinary and more than merely "occasional". That may be difficult to do, since salary positions rarely keep detailed logs of hours worked beyond the 40 required to avoid any flags in their HR applications :) Which is why I suggest taking more control over their sprint capacity.
– David Z
5 hours ago
As I clarified in my edit about an hour ago: "Sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm." It sounds like this is not a growing team, but a fixed team of 2 that have been denied requests for additional support. The challenge now is proving (with data, not feelings) that they're working at an unsustainable pace.
– David Z
5 hours ago
add a comment
|
A nearby team (of 4 members), whose output is poor, got an additional member.
This is a potential red flag for me. Of course, some of the times, the output deficiency is due to not having enough staff, in which case it makes sense to add headcount and continue monitoring output. But if there's a more general pattern of rewarding poor-performing teams with headcount, while high-performing teams are left to do "hero" work, that's toxic.
Further: Regardless of what's going on with the other team, a work environment that has handwaves away the very real problem of ongoing "heroic effort" is, in itself, toxic. It leads to mistakes & rework, burnout, low morale, turnover, etc., all of which are costly to the business in the long run. Of course, sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm.
We've been asking for a team increase, but since we deliver in an acceptable manner, basically we've been told that there is no need, regardless of our stress and overtime.
The way you deal with this is probably in your planning sessions. Assuming you're following some sort of sprint/agile development, commit to reasonable sprint points that don't require heroic efforts (routine after-hours or weekend work). Push back when product owners expect more features to be delivered in a given sprint.
You have past sprints to indicate that your team delivers X points in a 2-week sprint, you can't reasonably deliver X + 20 points in a 2-week sprint. If they insist on increased output, then you have metrics that justify your demand for additional headcount. If this is in flux, then it may be a part-time contractor rather, or maybe you loan someone over from another team/department that has extra bandwidth.
This is a bit of a passive approach, of course. But they've been passively trampling on your acceptance of increased workloads till now. You've unknowingly set expectations that you'll work overtime (if you're salaried, this is probably unpaid and mostly unrecognized, too!) and late nights and weekends to deliver. You need to slowly, but carefully back this expectation down to a more reasonable level.
New contributor
2
I'm glad it is a red flag for others as well. We are working Scrum (two man Scrum). I have to check what kind of metrics we can to use.
– Claudiu A
8 hours ago
The OP needs to demonstrate that the effort is actually "heroic" and not just "temporarily heavy". There are times when a little pain is to be expected, and a growing team is one of those times. Words like "toxic", "handwaves", "heroic" and "trampling" are usually seen as histrionic and not accurate. Remember - the step from 2 to 3 is 40 more person-hours per week, not 5 or 10.
– Julie in Austin
6 hours ago
I agree that it would help OP's case if they can demonstrate that the efforts have been both extraordinary and more than merely "occasional". That may be difficult to do, since salary positions rarely keep detailed logs of hours worked beyond the 40 required to avoid any flags in their HR applications :) Which is why I suggest taking more control over their sprint capacity.
– David Z
5 hours ago
As I clarified in my edit about an hour ago: "Sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm." It sounds like this is not a growing team, but a fixed team of 2 that have been denied requests for additional support. The challenge now is proving (with data, not feelings) that they're working at an unsustainable pace.
– David Z
5 hours ago
add a comment
|
A nearby team (of 4 members), whose output is poor, got an additional member.
This is a potential red flag for me. Of course, some of the times, the output deficiency is due to not having enough staff, in which case it makes sense to add headcount and continue monitoring output. But if there's a more general pattern of rewarding poor-performing teams with headcount, while high-performing teams are left to do "hero" work, that's toxic.
Further: Regardless of what's going on with the other team, a work environment that has handwaves away the very real problem of ongoing "heroic effort" is, in itself, toxic. It leads to mistakes & rework, burnout, low morale, turnover, etc., all of which are costly to the business in the long run. Of course, sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm.
We've been asking for a team increase, but since we deliver in an acceptable manner, basically we've been told that there is no need, regardless of our stress and overtime.
The way you deal with this is probably in your planning sessions. Assuming you're following some sort of sprint/agile development, commit to reasonable sprint points that don't require heroic efforts (routine after-hours or weekend work). Push back when product owners expect more features to be delivered in a given sprint.
You have past sprints to indicate that your team delivers X points in a 2-week sprint, you can't reasonably deliver X + 20 points in a 2-week sprint. If they insist on increased output, then you have metrics that justify your demand for additional headcount. If this is in flux, then it may be a part-time contractor rather, or maybe you loan someone over from another team/department that has extra bandwidth.
This is a bit of a passive approach, of course. But they've been passively trampling on your acceptance of increased workloads till now. You've unknowingly set expectations that you'll work overtime (if you're salaried, this is probably unpaid and mostly unrecognized, too!) and late nights and weekends to deliver. You need to slowly, but carefully back this expectation down to a more reasonable level.
New contributor
A nearby team (of 4 members), whose output is poor, got an additional member.
This is a potential red flag for me. Of course, some of the times, the output deficiency is due to not having enough staff, in which case it makes sense to add headcount and continue monitoring output. But if there's a more general pattern of rewarding poor-performing teams with headcount, while high-performing teams are left to do "hero" work, that's toxic.
Further: Regardless of what's going on with the other team, a work environment that has handwaves away the very real problem of ongoing "heroic effort" is, in itself, toxic. It leads to mistakes & rework, burnout, low morale, turnover, etc., all of which are costly to the business in the long run. Of course, sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm.
We've been asking for a team increase, but since we deliver in an acceptable manner, basically we've been told that there is no need, regardless of our stress and overtime.
The way you deal with this is probably in your planning sessions. Assuming you're following some sort of sprint/agile development, commit to reasonable sprint points that don't require heroic efforts (routine after-hours or weekend work). Push back when product owners expect more features to be delivered in a given sprint.
You have past sprints to indicate that your team delivers X points in a 2-week sprint, you can't reasonably deliver X + 20 points in a 2-week sprint. If they insist on increased output, then you have metrics that justify your demand for additional headcount. If this is in flux, then it may be a part-time contractor rather, or maybe you loan someone over from another team/department that has extra bandwidth.
This is a bit of a passive approach, of course. But they've been passively trampling on your acceptance of increased workloads till now. You've unknowingly set expectations that you'll work overtime (if you're salaried, this is probably unpaid and mostly unrecognized, too!) and late nights and weekends to deliver. You need to slowly, but carefully back this expectation down to a more reasonable level.
New contributor
edited 6 hours ago
New contributor
answered 8 hours ago
David ZDavid Z
2741 silver badge6 bronze badges
2741 silver badge6 bronze badges
New contributor
New contributor
2
I'm glad it is a red flag for others as well. We are working Scrum (two man Scrum). I have to check what kind of metrics we can to use.
– Claudiu A
8 hours ago
The OP needs to demonstrate that the effort is actually "heroic" and not just "temporarily heavy". There are times when a little pain is to be expected, and a growing team is one of those times. Words like "toxic", "handwaves", "heroic" and "trampling" are usually seen as histrionic and not accurate. Remember - the step from 2 to 3 is 40 more person-hours per week, not 5 or 10.
– Julie in Austin
6 hours ago
I agree that it would help OP's case if they can demonstrate that the efforts have been both extraordinary and more than merely "occasional". That may be difficult to do, since salary positions rarely keep detailed logs of hours worked beyond the 40 required to avoid any flags in their HR applications :) Which is why I suggest taking more control over their sprint capacity.
– David Z
5 hours ago
As I clarified in my edit about an hour ago: "Sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm." It sounds like this is not a growing team, but a fixed team of 2 that have been denied requests for additional support. The challenge now is proving (with data, not feelings) that they're working at an unsustainable pace.
– David Z
5 hours ago
add a comment
|
2
I'm glad it is a red flag for others as well. We are working Scrum (two man Scrum). I have to check what kind of metrics we can to use.
– Claudiu A
8 hours ago
The OP needs to demonstrate that the effort is actually "heroic" and not just "temporarily heavy". There are times when a little pain is to be expected, and a growing team is one of those times. Words like "toxic", "handwaves", "heroic" and "trampling" are usually seen as histrionic and not accurate. Remember - the step from 2 to 3 is 40 more person-hours per week, not 5 or 10.
– Julie in Austin
6 hours ago
I agree that it would help OP's case if they can demonstrate that the efforts have been both extraordinary and more than merely "occasional". That may be difficult to do, since salary positions rarely keep detailed logs of hours worked beyond the 40 required to avoid any flags in their HR applications :) Which is why I suggest taking more control over their sprint capacity.
– David Z
5 hours ago
As I clarified in my edit about an hour ago: "Sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm." It sounds like this is not a growing team, but a fixed team of 2 that have been denied requests for additional support. The challenge now is proving (with data, not feelings) that they're working at an unsustainable pace.
– David Z
5 hours ago
2
2
I'm glad it is a red flag for others as well. We are working Scrum (two man Scrum). I have to check what kind of metrics we can to use.
– Claudiu A
8 hours ago
I'm glad it is a red flag for others as well. We are working Scrum (two man Scrum). I have to check what kind of metrics we can to use.
– Claudiu A
8 hours ago
The OP needs to demonstrate that the effort is actually "heroic" and not just "temporarily heavy". There are times when a little pain is to be expected, and a growing team is one of those times. Words like "toxic", "handwaves", "heroic" and "trampling" are usually seen as histrionic and not accurate. Remember - the step from 2 to 3 is 40 more person-hours per week, not 5 or 10.
– Julie in Austin
6 hours ago
The OP needs to demonstrate that the effort is actually "heroic" and not just "temporarily heavy". There are times when a little pain is to be expected, and a growing team is one of those times. Words like "toxic", "handwaves", "heroic" and "trampling" are usually seen as histrionic and not accurate. Remember - the step from 2 to 3 is 40 more person-hours per week, not 5 or 10.
– Julie in Austin
6 hours ago
I agree that it would help OP's case if they can demonstrate that the efforts have been both extraordinary and more than merely "occasional". That may be difficult to do, since salary positions rarely keep detailed logs of hours worked beyond the 40 required to avoid any flags in their HR applications :) Which is why I suggest taking more control over their sprint capacity.
– David Z
5 hours ago
I agree that it would help OP's case if they can demonstrate that the efforts have been both extraordinary and more than merely "occasional". That may be difficult to do, since salary positions rarely keep detailed logs of hours worked beyond the 40 required to avoid any flags in their HR applications :) Which is why I suggest taking more control over their sprint capacity.
– David Z
5 hours ago
As I clarified in my edit about an hour ago: "Sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm." It sounds like this is not a growing team, but a fixed team of 2 that have been denied requests for additional support. The challenge now is proving (with data, not feelings) that they're working at an unsustainable pace.
– David Z
5 hours ago
As I clarified in my edit about an hour ago: "Sometimes heroic effort is needed to meet critical deadlines, etc., but working long hours/weekends/etc should be the exception, not the norm." It sounds like this is not a growing team, but a fixed team of 2 that have been denied requests for additional support. The challenge now is proving (with data, not feelings) that they're working at an unsustainable pace.
– David Z
5 hours ago
add a comment
|
Contact the right people
- HR, and there somebody that is truly engaged in wellbeing and has the power drive the change
- A senior manager that has enough experience and authority
- The source of the tasks
Do not undervalue soft power. A manager that is not necessarily that senior in the hierarchy can have seniority from the years of working valued, sometimes even connection at the top of the organisation.
Use other metrics to justify your case
- Overtime
- Action points per worker
- Number of projects you are working on
- People that have left
- Conversations about different career possibilities raised by the members
Also, remember to have some numbers from history.
Use the right words
- You are highly concerned about the wellbeing
- Your team is starting to lose their drive
- Any buzzword the HR is using for the issue works.
If they see only synonyms they might not recognise it as being important. The words the managers recognise for being held accountable in their scorecards.
I can have a meeting with a manager and I think this list can help me prepare very well. The metrics required are very easy to gather. Thanks!
– Claudiu A
7 hours ago
add a comment
|
Contact the right people
- HR, and there somebody that is truly engaged in wellbeing and has the power drive the change
- A senior manager that has enough experience and authority
- The source of the tasks
Do not undervalue soft power. A manager that is not necessarily that senior in the hierarchy can have seniority from the years of working valued, sometimes even connection at the top of the organisation.
Use other metrics to justify your case
- Overtime
- Action points per worker
- Number of projects you are working on
- People that have left
- Conversations about different career possibilities raised by the members
Also, remember to have some numbers from history.
Use the right words
- You are highly concerned about the wellbeing
- Your team is starting to lose their drive
- Any buzzword the HR is using for the issue works.
If they see only synonyms they might not recognise it as being important. The words the managers recognise for being held accountable in their scorecards.
I can have a meeting with a manager and I think this list can help me prepare very well. The metrics required are very easy to gather. Thanks!
– Claudiu A
7 hours ago
add a comment
|
Contact the right people
- HR, and there somebody that is truly engaged in wellbeing and has the power drive the change
- A senior manager that has enough experience and authority
- The source of the tasks
Do not undervalue soft power. A manager that is not necessarily that senior in the hierarchy can have seniority from the years of working valued, sometimes even connection at the top of the organisation.
Use other metrics to justify your case
- Overtime
- Action points per worker
- Number of projects you are working on
- People that have left
- Conversations about different career possibilities raised by the members
Also, remember to have some numbers from history.
Use the right words
- You are highly concerned about the wellbeing
- Your team is starting to lose their drive
- Any buzzword the HR is using for the issue works.
If they see only synonyms they might not recognise it as being important. The words the managers recognise for being held accountable in their scorecards.
Contact the right people
- HR, and there somebody that is truly engaged in wellbeing and has the power drive the change
- A senior manager that has enough experience and authority
- The source of the tasks
Do not undervalue soft power. A manager that is not necessarily that senior in the hierarchy can have seniority from the years of working valued, sometimes even connection at the top of the organisation.
Use other metrics to justify your case
- Overtime
- Action points per worker
- Number of projects you are working on
- People that have left
- Conversations about different career possibilities raised by the members
Also, remember to have some numbers from history.
Use the right words
- You are highly concerned about the wellbeing
- Your team is starting to lose their drive
- Any buzzword the HR is using for the issue works.
If they see only synonyms they might not recognise it as being important. The words the managers recognise for being held accountable in their scorecards.
answered 8 hours ago
user3644640user3644640
1,0454 silver badges9 bronze badges
1,0454 silver badges9 bronze badges
I can have a meeting with a manager and I think this list can help me prepare very well. The metrics required are very easy to gather. Thanks!
– Claudiu A
7 hours ago
add a comment
|
I can have a meeting with a manager and I think this list can help me prepare very well. The metrics required are very easy to gather. Thanks!
– Claudiu A
7 hours ago
I can have a meeting with a manager and I think this list can help me prepare very well. The metrics required are very easy to gather. Thanks!
– Claudiu A
7 hours ago
I can have a meeting with a manager and I think this list can help me prepare very well. The metrics required are very easy to gather. Thanks!
– Claudiu A
7 hours ago
add a comment
|
Small teams are harder to justify a new team member because the increase in team size is greater. In your case, you are asking for a 50% increase in team size, relative to that other team which only received a 25% increase in size.
Unfortunately, unless you are consistently working more than 10-20% overtime each, that 50% bump is just going to be hard. What you need to show is that either you just can't handle the workload (it sounds like you can ...) or you are working so much overtime that it isn't sustainable.
The other answers rightly point out that what you're doing is somehow "wrong", but it is really only wrong in the long term and is unsustainable. From your employer's perspective it is better to have 2 employees working 110% than three employees working 75%. Two employees working 120-130% isn't sustainable. You need to quantify how how much you're doing and show that the work load is inappropriate and unsustainable.
Edited to add --
Just to clarify, the OP is in a sticky situation precisely because of the small team size. The only thing harder than adding the second team member is adding the second. An alternative to adding a full-time 3rd member is borrowing someone from another team. That's an approach my various teams have had to use to demonstrate "need".
Since the workload increases consistently, it will definitely become unsustainable. I can see a pattern from the answer: "start doing less" and I can see why.
– Claudiu A
8 hours ago
1
The issue remains -- adding a team member requires demonstrating that the existing team cannot handle it AND that the only solution is a 3rd team member who won't be idle most of the time. That may not be the case today, even if it will be at some point in the future.
– Julie in Austin
6 hours ago
add a comment
|
Small teams are harder to justify a new team member because the increase in team size is greater. In your case, you are asking for a 50% increase in team size, relative to that other team which only received a 25% increase in size.
Unfortunately, unless you are consistently working more than 10-20% overtime each, that 50% bump is just going to be hard. What you need to show is that either you just can't handle the workload (it sounds like you can ...) or you are working so much overtime that it isn't sustainable.
The other answers rightly point out that what you're doing is somehow "wrong", but it is really only wrong in the long term and is unsustainable. From your employer's perspective it is better to have 2 employees working 110% than three employees working 75%. Two employees working 120-130% isn't sustainable. You need to quantify how how much you're doing and show that the work load is inappropriate and unsustainable.
Edited to add --
Just to clarify, the OP is in a sticky situation precisely because of the small team size. The only thing harder than adding the second team member is adding the second. An alternative to adding a full-time 3rd member is borrowing someone from another team. That's an approach my various teams have had to use to demonstrate "need".
Since the workload increases consistently, it will definitely become unsustainable. I can see a pattern from the answer: "start doing less" and I can see why.
– Claudiu A
8 hours ago
1
The issue remains -- adding a team member requires demonstrating that the existing team cannot handle it AND that the only solution is a 3rd team member who won't be idle most of the time. That may not be the case today, even if it will be at some point in the future.
– Julie in Austin
6 hours ago
add a comment
|
Small teams are harder to justify a new team member because the increase in team size is greater. In your case, you are asking for a 50% increase in team size, relative to that other team which only received a 25% increase in size.
Unfortunately, unless you are consistently working more than 10-20% overtime each, that 50% bump is just going to be hard. What you need to show is that either you just can't handle the workload (it sounds like you can ...) or you are working so much overtime that it isn't sustainable.
The other answers rightly point out that what you're doing is somehow "wrong", but it is really only wrong in the long term and is unsustainable. From your employer's perspective it is better to have 2 employees working 110% than three employees working 75%. Two employees working 120-130% isn't sustainable. You need to quantify how how much you're doing and show that the work load is inappropriate and unsustainable.
Edited to add --
Just to clarify, the OP is in a sticky situation precisely because of the small team size. The only thing harder than adding the second team member is adding the second. An alternative to adding a full-time 3rd member is borrowing someone from another team. That's an approach my various teams have had to use to demonstrate "need".
Small teams are harder to justify a new team member because the increase in team size is greater. In your case, you are asking for a 50% increase in team size, relative to that other team which only received a 25% increase in size.
Unfortunately, unless you are consistently working more than 10-20% overtime each, that 50% bump is just going to be hard. What you need to show is that either you just can't handle the workload (it sounds like you can ...) or you are working so much overtime that it isn't sustainable.
The other answers rightly point out that what you're doing is somehow "wrong", but it is really only wrong in the long term and is unsustainable. From your employer's perspective it is better to have 2 employees working 110% than three employees working 75%. Two employees working 120-130% isn't sustainable. You need to quantify how how much you're doing and show that the work load is inappropriate and unsustainable.
Edited to add --
Just to clarify, the OP is in a sticky situation precisely because of the small team size. The only thing harder than adding the second team member is adding the second. An alternative to adding a full-time 3rd member is borrowing someone from another team. That's an approach my various teams have had to use to demonstrate "need".
edited 6 hours ago
answered 8 hours ago
Julie in AustinJulie in Austin
4,0319 silver badges31 bronze badges
4,0319 silver badges31 bronze badges
Since the workload increases consistently, it will definitely become unsustainable. I can see a pattern from the answer: "start doing less" and I can see why.
– Claudiu A
8 hours ago
1
The issue remains -- adding a team member requires demonstrating that the existing team cannot handle it AND that the only solution is a 3rd team member who won't be idle most of the time. That may not be the case today, even if it will be at some point in the future.
– Julie in Austin
6 hours ago
add a comment
|
Since the workload increases consistently, it will definitely become unsustainable. I can see a pattern from the answer: "start doing less" and I can see why.
– Claudiu A
8 hours ago
1
The issue remains -- adding a team member requires demonstrating that the existing team cannot handle it AND that the only solution is a 3rd team member who won't be idle most of the time. That may not be the case today, even if it will be at some point in the future.
– Julie in Austin
6 hours ago
Since the workload increases consistently, it will definitely become unsustainable. I can see a pattern from the answer: "start doing less" and I can see why.
– Claudiu A
8 hours ago
Since the workload increases consistently, it will definitely become unsustainable. I can see a pattern from the answer: "start doing less" and I can see why.
– Claudiu A
8 hours ago
1
1
The issue remains -- adding a team member requires demonstrating that the existing team cannot handle it AND that the only solution is a 3rd team member who won't be idle most of the time. That may not be the case today, even if it will be at some point in the future.
– Julie in Austin
6 hours ago
The issue remains -- adding a team member requires demonstrating that the existing team cannot handle it AND that the only solution is a 3rd team member who won't be idle most of the time. That may not be the case today, even if it will be at some point in the future.
– Julie in Austin
6 hours ago
add a comment
|
Claudiu A is a new contributor. Be nice, and check out our Code of Conduct.
Claudiu A is a new contributor. Be nice, and check out our Code of Conduct.
Claudiu A is a new contributor. Be nice, and check out our Code of Conduct.
Claudiu A is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to The Workplace Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fworkplace.stackexchange.com%2fquestions%2f145304%2fhow-to-justify-a-team-increase-when-the-team-is-doing-good%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Just to clarify, by "increase" you mean you want another person on the team? I was confused at first because some times, "increase" is assumed to mean salary increase, i.e. raise. I thought you were trying to ask for everyone on the team to get a raise.
– dwizum
8 hours ago
Yes, by increase I mean having an additional team member. I don't know what is the better term to describe this.
– Claudiu A
8 hours ago
Is overtime paid, unpaid?
– Crosbonaught
6 hours ago
Unpaid. We are very passionate in what we do, which is why the suggestions below, to take less stories/tasks is very doable for us.
– Claudiu A
6 hours ago