My tabularx gives error, “Missing number, treated as zero”
up vote
1
down vote
favorite
begin{table*}[h!]
caption{list of unique effects on project plan with their descriptions}
label{tab:defination}
resizebox{textwidth}{!}{
centering
begin{tabularx}{textwidth}{X|X|X}
noindent
begin{tabular}{
|p{dimexpr.10linewidth-2tabcolsep-1.3333arrayrulewidth}% column 1
|p{dimexpr.26linewidth-2tabcolsep-1.3333arrayrulewidth}% column 2
|p{dimexpr.65linewidth-2tabcolsep-1.3333arrayrulewidth}% column 3
}
hline
No & Effects & Descriptions \
hline
1 & Project priority (EFF1) & Change in dependency of task and project milestone due to redirection, reallocation and prioritization of project scope resulting change in project priority. Thus change activities in the critical path and slips the project schedule \
hline
2 & Lack of motivation and direction (EFF2) & Difference in individual's perception, culture and scope cross cutting (De-scoping of feature) leads to decrease in staff motivation and unmeet project deadlines.\
hline
3 & Increase cost (EFF3) & Change in life cycle costing, unapproved scope, risk mitigation, initial estimates and adding more decision points increase project cost and reduce contingency reserved.\
hline
4 & Project resources change (EFF4) & Change in project resources (team member, project manager, hardware, software) with limited boundaries of the project leads to the scope issues and increases overhead for potential delays and budget.\
hline
5 & Project risks (EFF5) & Technological uncertainty, untried assumption constrains, requirement uncertainty and volatility (have impact on project risk management) can direct blowout cost afterwards.\
hline
6 & Rework (EFF6) & Redefining new process, methodology, strategy, policy, alternatives and assessments can cause impact through rework, resulting in budget and schedule overrun.\
hline
7 & Schedule delays (EFF7) & Number of breaks, waiting periods, third party tool provider, vague scope definition, ineffective or immature process contribute towards lengthy lead time. \
hline
8 & Communication and coordination gaps (EFF8) & Unrealistic scope changes, trust issues, in-appropriate sharing of document and
lack of decision making have an effect on non-technical issues like communication gaps. \
hline
9 & Quality issue(EFF9) & Quality attributes (performance, security, reliability, availability etc.), requirement volatility (code quality, quality of project management and developer's capability) and lack of commitment have an effect on project quality, as it decreases market share and brand value.\
hline
10 & Lower productivity (EFF10) & Workforce experience and forecasted completion date of the project has an effect on actual productivity. During project, increase in workforce size and process losses progressively decrease actual productivity. \
hline
end{tabular}
end{tabularx}
%label{table1:nonlin}
}
end{table*}
gives error missing number treated as zero }.
tabularx
New contributor
avais is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
1
down vote
favorite
begin{table*}[h!]
caption{list of unique effects on project plan with their descriptions}
label{tab:defination}
resizebox{textwidth}{!}{
centering
begin{tabularx}{textwidth}{X|X|X}
noindent
begin{tabular}{
|p{dimexpr.10linewidth-2tabcolsep-1.3333arrayrulewidth}% column 1
|p{dimexpr.26linewidth-2tabcolsep-1.3333arrayrulewidth}% column 2
|p{dimexpr.65linewidth-2tabcolsep-1.3333arrayrulewidth}% column 3
}
hline
No & Effects & Descriptions \
hline
1 & Project priority (EFF1) & Change in dependency of task and project milestone due to redirection, reallocation and prioritization of project scope resulting change in project priority. Thus change activities in the critical path and slips the project schedule \
hline
2 & Lack of motivation and direction (EFF2) & Difference in individual's perception, culture and scope cross cutting (De-scoping of feature) leads to decrease in staff motivation and unmeet project deadlines.\
hline
3 & Increase cost (EFF3) & Change in life cycle costing, unapproved scope, risk mitigation, initial estimates and adding more decision points increase project cost and reduce contingency reserved.\
hline
4 & Project resources change (EFF4) & Change in project resources (team member, project manager, hardware, software) with limited boundaries of the project leads to the scope issues and increases overhead for potential delays and budget.\
hline
5 & Project risks (EFF5) & Technological uncertainty, untried assumption constrains, requirement uncertainty and volatility (have impact on project risk management) can direct blowout cost afterwards.\
hline
6 & Rework (EFF6) & Redefining new process, methodology, strategy, policy, alternatives and assessments can cause impact through rework, resulting in budget and schedule overrun.\
hline
7 & Schedule delays (EFF7) & Number of breaks, waiting periods, third party tool provider, vague scope definition, ineffective or immature process contribute towards lengthy lead time. \
hline
8 & Communication and coordination gaps (EFF8) & Unrealistic scope changes, trust issues, in-appropriate sharing of document and
lack of decision making have an effect on non-technical issues like communication gaps. \
hline
9 & Quality issue(EFF9) & Quality attributes (performance, security, reliability, availability etc.), requirement volatility (code quality, quality of project management and developer's capability) and lack of commitment have an effect on project quality, as it decreases market share and brand value.\
hline
10 & Lower productivity (EFF10) & Workforce experience and forecasted completion date of the project has an effect on actual productivity. During project, increase in workforce size and process losses progressively decrease actual productivity. \
hline
end{tabular}
end{tabularx}
%label{table1:nonlin}
}
end{table*}
gives error missing number treated as zero }.
tabularx
New contributor
avais is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
Why are you nesting a tabular inside the tabularx and the tabularx inside a resizebox?
– Ulrike Fischer
yesterday
never put tables inresizebox{textwidth}{!}{it just produces inconsistent font sizes (as well as if you have a linebreak after{a sprurious space on the left). If you want help with an error please provide a complete but small test file, no one can run your fragment as posted but remove the innertabulara s currently everything is in a one-row one column tabularx
– David Carlisle
yesterday
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
begin{table*}[h!]
caption{list of unique effects on project plan with their descriptions}
label{tab:defination}
resizebox{textwidth}{!}{
centering
begin{tabularx}{textwidth}{X|X|X}
noindent
begin{tabular}{
|p{dimexpr.10linewidth-2tabcolsep-1.3333arrayrulewidth}% column 1
|p{dimexpr.26linewidth-2tabcolsep-1.3333arrayrulewidth}% column 2
|p{dimexpr.65linewidth-2tabcolsep-1.3333arrayrulewidth}% column 3
}
hline
No & Effects & Descriptions \
hline
1 & Project priority (EFF1) & Change in dependency of task and project milestone due to redirection, reallocation and prioritization of project scope resulting change in project priority. Thus change activities in the critical path and slips the project schedule \
hline
2 & Lack of motivation and direction (EFF2) & Difference in individual's perception, culture and scope cross cutting (De-scoping of feature) leads to decrease in staff motivation and unmeet project deadlines.\
hline
3 & Increase cost (EFF3) & Change in life cycle costing, unapproved scope, risk mitigation, initial estimates and adding more decision points increase project cost and reduce contingency reserved.\
hline
4 & Project resources change (EFF4) & Change in project resources (team member, project manager, hardware, software) with limited boundaries of the project leads to the scope issues and increases overhead for potential delays and budget.\
hline
5 & Project risks (EFF5) & Technological uncertainty, untried assumption constrains, requirement uncertainty and volatility (have impact on project risk management) can direct blowout cost afterwards.\
hline
6 & Rework (EFF6) & Redefining new process, methodology, strategy, policy, alternatives and assessments can cause impact through rework, resulting in budget and schedule overrun.\
hline
7 & Schedule delays (EFF7) & Number of breaks, waiting periods, third party tool provider, vague scope definition, ineffective or immature process contribute towards lengthy lead time. \
hline
8 & Communication and coordination gaps (EFF8) & Unrealistic scope changes, trust issues, in-appropriate sharing of document and
lack of decision making have an effect on non-technical issues like communication gaps. \
hline
9 & Quality issue(EFF9) & Quality attributes (performance, security, reliability, availability etc.), requirement volatility (code quality, quality of project management and developer's capability) and lack of commitment have an effect on project quality, as it decreases market share and brand value.\
hline
10 & Lower productivity (EFF10) & Workforce experience and forecasted completion date of the project has an effect on actual productivity. During project, increase in workforce size and process losses progressively decrease actual productivity. \
hline
end{tabular}
end{tabularx}
%label{table1:nonlin}
}
end{table*}
gives error missing number treated as zero }.
tabularx
New contributor
avais is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
begin{table*}[h!]
caption{list of unique effects on project plan with their descriptions}
label{tab:defination}
resizebox{textwidth}{!}{
centering
begin{tabularx}{textwidth}{X|X|X}
noindent
begin{tabular}{
|p{dimexpr.10linewidth-2tabcolsep-1.3333arrayrulewidth}% column 1
|p{dimexpr.26linewidth-2tabcolsep-1.3333arrayrulewidth}% column 2
|p{dimexpr.65linewidth-2tabcolsep-1.3333arrayrulewidth}% column 3
}
hline
No & Effects & Descriptions \
hline
1 & Project priority (EFF1) & Change in dependency of task and project milestone due to redirection, reallocation and prioritization of project scope resulting change in project priority. Thus change activities in the critical path and slips the project schedule \
hline
2 & Lack of motivation and direction (EFF2) & Difference in individual's perception, culture and scope cross cutting (De-scoping of feature) leads to decrease in staff motivation and unmeet project deadlines.\
hline
3 & Increase cost (EFF3) & Change in life cycle costing, unapproved scope, risk mitigation, initial estimates and adding more decision points increase project cost and reduce contingency reserved.\
hline
4 & Project resources change (EFF4) & Change in project resources (team member, project manager, hardware, software) with limited boundaries of the project leads to the scope issues and increases overhead for potential delays and budget.\
hline
5 & Project risks (EFF5) & Technological uncertainty, untried assumption constrains, requirement uncertainty and volatility (have impact on project risk management) can direct blowout cost afterwards.\
hline
6 & Rework (EFF6) & Redefining new process, methodology, strategy, policy, alternatives and assessments can cause impact through rework, resulting in budget and schedule overrun.\
hline
7 & Schedule delays (EFF7) & Number of breaks, waiting periods, third party tool provider, vague scope definition, ineffective or immature process contribute towards lengthy lead time. \
hline
8 & Communication and coordination gaps (EFF8) & Unrealistic scope changes, trust issues, in-appropriate sharing of document and
lack of decision making have an effect on non-technical issues like communication gaps. \
hline
9 & Quality issue(EFF9) & Quality attributes (performance, security, reliability, availability etc.), requirement volatility (code quality, quality of project management and developer's capability) and lack of commitment have an effect on project quality, as it decreases market share and brand value.\
hline
10 & Lower productivity (EFF10) & Workforce experience and forecasted completion date of the project has an effect on actual productivity. During project, increase in workforce size and process losses progressively decrease actual productivity. \
hline
end{tabular}
end{tabularx}
%label{table1:nonlin}
}
end{table*}
gives error missing number treated as zero }.
tabularx
tabularx
New contributor
avais is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
avais is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited yesterday
Ulrike Fischer
182k7288661
182k7288661
New contributor
avais is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked yesterday
avais
232
232
New contributor
avais is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
avais is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
avais is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
2
Why are you nesting a tabular inside the tabularx and the tabularx inside a resizebox?
– Ulrike Fischer
yesterday
never put tables inresizebox{textwidth}{!}{it just produces inconsistent font sizes (as well as if you have a linebreak after{a sprurious space on the left). If you want help with an error please provide a complete but small test file, no one can run your fragment as posted but remove the innertabulara s currently everything is in a one-row one column tabularx
– David Carlisle
yesterday
add a comment |
2
Why are you nesting a tabular inside the tabularx and the tabularx inside a resizebox?
– Ulrike Fischer
yesterday
never put tables inresizebox{textwidth}{!}{it just produces inconsistent font sizes (as well as if you have a linebreak after{a sprurious space on the left). If you want help with an error please provide a complete but small test file, no one can run your fragment as posted but remove the innertabulara s currently everything is in a one-row one column tabularx
– David Carlisle
yesterday
2
2
Why are you nesting a tabular inside the tabularx and the tabularx inside a resizebox?
– Ulrike Fischer
yesterday
Why are you nesting a tabular inside the tabularx and the tabularx inside a resizebox?
– Ulrike Fischer
yesterday
never put tables in
resizebox{textwidth}{!}{ it just produces inconsistent font sizes (as well as if you have a linebreak after { a sprurious space on the left). If you want help with an error please provide a complete but small test file, no one can run your fragment as posted but remove the inner tabular a s currently everything is in a one-row one column tabularx– David Carlisle
yesterday
never put tables in
resizebox{textwidth}{!}{ it just produces inconsistent font sizes (as well as if you have a linebreak after { a sprurious space on the left). If you want help with an error please provide a complete but small test file, no one can run your fragment as posted but remove the inner tabular a s currently everything is in a one-row one column tabularx– David Carlisle
yesterday
add a comment |
1 Answer
1
active
oldest
votes
up vote
2
down vote
The posted code (if completed to a document) does not give the error in the title, it runs without error but with the warning
LaTeX Warning: `!h' float specifier changed to `!ht'.
However it is a one-row one column table with a nested table in that cell

documentclass{article}
usepackage{tabularx,graphicx}
begin{document}
begin{table*}[htp]
caption{list of unique effects on project plan with their descriptions}
label{tab:defination}
small
begin{tabularx}{textwidth}{l|>{raggedright}p{3cm}|X}
hline
No & Effects & Descriptions \
hline
1 & Project priority (EFF1) & Change in dependency of task and project milestone due to redirection, reallocation and prioritization of project scope resulting change in project priority. Thus change activities in the critical path and slips the project schedule \
hline
2 & Lack of motivation and direction (EFF2) & Difference in individual's perception, culture and scope cross cutting (De-scoping of feature) leads to decrease in staff motivation and unmeet project deadlines.\
hline
3 & Increase cost (EFF3) & Change in life cycle costing, unapproved scope, risk mitigation, initial estimates and adding more decision points increase project cost and reduce contingency reserved.\
hline
4 & Project resources change (EFF4) & Change in project resources (team member, project manager, hardware, software) with limited boundaries of the project leads to the scope issues and increases overhead for potential delays and budget.\
hline
5 & Project risks (EFF5) & Technological uncertainty, untried assumption constrains, requirement uncertainty and volatility (have impact on project risk management) can direct blowout cost afterwards.\
hline
6 & Rework (EFF6) & Redefining new process, methodology, strategy, policy, alternatives and assessments can cause impact through rework, resulting in budget and schedule overrun.\
hline
7 & Schedule delays (EFF7) & Number of breaks, waiting periods, third party tool provider, vague scope definition, ineffective or immature process contribute towards lengthy lead time. \
hline
8 & Communication and coordination gaps (EFF8) & Unrealistic scope changes, trust issues, in-appropriate sharing of document and
lack of decision making have an effect on non-technical issues like communication gaps. \
hline
9 & Quality issue(EFF9) & Quality attributes (performance, security, reliability, availability etc.), requirement volatility (code quality, quality of project management and developer's capability) and lack of commitment have an effect on project quality, as it decreases market share and brand value.\
hline
10 & Lower productivity (EFF10) & Workforce experience and forecasted completion date of the project has an effect on actual productivity. During project, increase in workforce size and process losses progressively decrease actual productivity. \
hline
end{tabularx}
end{table*}
end{document}
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
2
down vote
The posted code (if completed to a document) does not give the error in the title, it runs without error but with the warning
LaTeX Warning: `!h' float specifier changed to `!ht'.
However it is a one-row one column table with a nested table in that cell

documentclass{article}
usepackage{tabularx,graphicx}
begin{document}
begin{table*}[htp]
caption{list of unique effects on project plan with their descriptions}
label{tab:defination}
small
begin{tabularx}{textwidth}{l|>{raggedright}p{3cm}|X}
hline
No & Effects & Descriptions \
hline
1 & Project priority (EFF1) & Change in dependency of task and project milestone due to redirection, reallocation and prioritization of project scope resulting change in project priority. Thus change activities in the critical path and slips the project schedule \
hline
2 & Lack of motivation and direction (EFF2) & Difference in individual's perception, culture and scope cross cutting (De-scoping of feature) leads to decrease in staff motivation and unmeet project deadlines.\
hline
3 & Increase cost (EFF3) & Change in life cycle costing, unapproved scope, risk mitigation, initial estimates and adding more decision points increase project cost and reduce contingency reserved.\
hline
4 & Project resources change (EFF4) & Change in project resources (team member, project manager, hardware, software) with limited boundaries of the project leads to the scope issues and increases overhead for potential delays and budget.\
hline
5 & Project risks (EFF5) & Technological uncertainty, untried assumption constrains, requirement uncertainty and volatility (have impact on project risk management) can direct blowout cost afterwards.\
hline
6 & Rework (EFF6) & Redefining new process, methodology, strategy, policy, alternatives and assessments can cause impact through rework, resulting in budget and schedule overrun.\
hline
7 & Schedule delays (EFF7) & Number of breaks, waiting periods, third party tool provider, vague scope definition, ineffective or immature process contribute towards lengthy lead time. \
hline
8 & Communication and coordination gaps (EFF8) & Unrealistic scope changes, trust issues, in-appropriate sharing of document and
lack of decision making have an effect on non-technical issues like communication gaps. \
hline
9 & Quality issue(EFF9) & Quality attributes (performance, security, reliability, availability etc.), requirement volatility (code quality, quality of project management and developer's capability) and lack of commitment have an effect on project quality, as it decreases market share and brand value.\
hline
10 & Lower productivity (EFF10) & Workforce experience and forecasted completion date of the project has an effect on actual productivity. During project, increase in workforce size and process losses progressively decrease actual productivity. \
hline
end{tabularx}
end{table*}
end{document}
add a comment |
up vote
2
down vote
The posted code (if completed to a document) does not give the error in the title, it runs without error but with the warning
LaTeX Warning: `!h' float specifier changed to `!ht'.
However it is a one-row one column table with a nested table in that cell

documentclass{article}
usepackage{tabularx,graphicx}
begin{document}
begin{table*}[htp]
caption{list of unique effects on project plan with their descriptions}
label{tab:defination}
small
begin{tabularx}{textwidth}{l|>{raggedright}p{3cm}|X}
hline
No & Effects & Descriptions \
hline
1 & Project priority (EFF1) & Change in dependency of task and project milestone due to redirection, reallocation and prioritization of project scope resulting change in project priority. Thus change activities in the critical path and slips the project schedule \
hline
2 & Lack of motivation and direction (EFF2) & Difference in individual's perception, culture and scope cross cutting (De-scoping of feature) leads to decrease in staff motivation and unmeet project deadlines.\
hline
3 & Increase cost (EFF3) & Change in life cycle costing, unapproved scope, risk mitigation, initial estimates and adding more decision points increase project cost and reduce contingency reserved.\
hline
4 & Project resources change (EFF4) & Change in project resources (team member, project manager, hardware, software) with limited boundaries of the project leads to the scope issues and increases overhead for potential delays and budget.\
hline
5 & Project risks (EFF5) & Technological uncertainty, untried assumption constrains, requirement uncertainty and volatility (have impact on project risk management) can direct blowout cost afterwards.\
hline
6 & Rework (EFF6) & Redefining new process, methodology, strategy, policy, alternatives and assessments can cause impact through rework, resulting in budget and schedule overrun.\
hline
7 & Schedule delays (EFF7) & Number of breaks, waiting periods, third party tool provider, vague scope definition, ineffective or immature process contribute towards lengthy lead time. \
hline
8 & Communication and coordination gaps (EFF8) & Unrealistic scope changes, trust issues, in-appropriate sharing of document and
lack of decision making have an effect on non-technical issues like communication gaps. \
hline
9 & Quality issue(EFF9) & Quality attributes (performance, security, reliability, availability etc.), requirement volatility (code quality, quality of project management and developer's capability) and lack of commitment have an effect on project quality, as it decreases market share and brand value.\
hline
10 & Lower productivity (EFF10) & Workforce experience and forecasted completion date of the project has an effect on actual productivity. During project, increase in workforce size and process losses progressively decrease actual productivity. \
hline
end{tabularx}
end{table*}
end{document}
add a comment |
up vote
2
down vote
up vote
2
down vote
The posted code (if completed to a document) does not give the error in the title, it runs without error but with the warning
LaTeX Warning: `!h' float specifier changed to `!ht'.
However it is a one-row one column table with a nested table in that cell

documentclass{article}
usepackage{tabularx,graphicx}
begin{document}
begin{table*}[htp]
caption{list of unique effects on project plan with their descriptions}
label{tab:defination}
small
begin{tabularx}{textwidth}{l|>{raggedright}p{3cm}|X}
hline
No & Effects & Descriptions \
hline
1 & Project priority (EFF1) & Change in dependency of task and project milestone due to redirection, reallocation and prioritization of project scope resulting change in project priority. Thus change activities in the critical path and slips the project schedule \
hline
2 & Lack of motivation and direction (EFF2) & Difference in individual's perception, culture and scope cross cutting (De-scoping of feature) leads to decrease in staff motivation and unmeet project deadlines.\
hline
3 & Increase cost (EFF3) & Change in life cycle costing, unapproved scope, risk mitigation, initial estimates and adding more decision points increase project cost and reduce contingency reserved.\
hline
4 & Project resources change (EFF4) & Change in project resources (team member, project manager, hardware, software) with limited boundaries of the project leads to the scope issues and increases overhead for potential delays and budget.\
hline
5 & Project risks (EFF5) & Technological uncertainty, untried assumption constrains, requirement uncertainty and volatility (have impact on project risk management) can direct blowout cost afterwards.\
hline
6 & Rework (EFF6) & Redefining new process, methodology, strategy, policy, alternatives and assessments can cause impact through rework, resulting in budget and schedule overrun.\
hline
7 & Schedule delays (EFF7) & Number of breaks, waiting periods, third party tool provider, vague scope definition, ineffective or immature process contribute towards lengthy lead time. \
hline
8 & Communication and coordination gaps (EFF8) & Unrealistic scope changes, trust issues, in-appropriate sharing of document and
lack of decision making have an effect on non-technical issues like communication gaps. \
hline
9 & Quality issue(EFF9) & Quality attributes (performance, security, reliability, availability etc.), requirement volatility (code quality, quality of project management and developer's capability) and lack of commitment have an effect on project quality, as it decreases market share and brand value.\
hline
10 & Lower productivity (EFF10) & Workforce experience and forecasted completion date of the project has an effect on actual productivity. During project, increase in workforce size and process losses progressively decrease actual productivity. \
hline
end{tabularx}
end{table*}
end{document}
The posted code (if completed to a document) does not give the error in the title, it runs without error but with the warning
LaTeX Warning: `!h' float specifier changed to `!ht'.
However it is a one-row one column table with a nested table in that cell

documentclass{article}
usepackage{tabularx,graphicx}
begin{document}
begin{table*}[htp]
caption{list of unique effects on project plan with their descriptions}
label{tab:defination}
small
begin{tabularx}{textwidth}{l|>{raggedright}p{3cm}|X}
hline
No & Effects & Descriptions \
hline
1 & Project priority (EFF1) & Change in dependency of task and project milestone due to redirection, reallocation and prioritization of project scope resulting change in project priority. Thus change activities in the critical path and slips the project schedule \
hline
2 & Lack of motivation and direction (EFF2) & Difference in individual's perception, culture and scope cross cutting (De-scoping of feature) leads to decrease in staff motivation and unmeet project deadlines.\
hline
3 & Increase cost (EFF3) & Change in life cycle costing, unapproved scope, risk mitigation, initial estimates and adding more decision points increase project cost and reduce contingency reserved.\
hline
4 & Project resources change (EFF4) & Change in project resources (team member, project manager, hardware, software) with limited boundaries of the project leads to the scope issues and increases overhead for potential delays and budget.\
hline
5 & Project risks (EFF5) & Technological uncertainty, untried assumption constrains, requirement uncertainty and volatility (have impact on project risk management) can direct blowout cost afterwards.\
hline
6 & Rework (EFF6) & Redefining new process, methodology, strategy, policy, alternatives and assessments can cause impact through rework, resulting in budget and schedule overrun.\
hline
7 & Schedule delays (EFF7) & Number of breaks, waiting periods, third party tool provider, vague scope definition, ineffective or immature process contribute towards lengthy lead time. \
hline
8 & Communication and coordination gaps (EFF8) & Unrealistic scope changes, trust issues, in-appropriate sharing of document and
lack of decision making have an effect on non-technical issues like communication gaps. \
hline
9 & Quality issue(EFF9) & Quality attributes (performance, security, reliability, availability etc.), requirement volatility (code quality, quality of project management and developer's capability) and lack of commitment have an effect on project quality, as it decreases market share and brand value.\
hline
10 & Lower productivity (EFF10) & Workforce experience and forecasted completion date of the project has an effect on actual productivity. During project, increase in workforce size and process losses progressively decrease actual productivity. \
hline
end{tabularx}
end{table*}
end{document}
answered yesterday
David Carlisle
477k3811061841
477k3811061841
add a comment |
add a comment |
avais is a new contributor. Be nice, and check out our Code of Conduct.
avais is a new contributor. Be nice, and check out our Code of Conduct.
avais is a new contributor. Be nice, and check out our Code of Conduct.
avais 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%2ftex.stackexchange.com%2fquestions%2f461068%2fmy-tabularx-gives-error-missing-number-treated-as-zero%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
2
Why are you nesting a tabular inside the tabularx and the tabularx inside a resizebox?
– Ulrike Fischer
yesterday
never put tables in
resizebox{textwidth}{!}{it just produces inconsistent font sizes (as well as if you have a linebreak after{a sprurious space on the left). If you want help with an error please provide a complete but small test file, no one can run your fragment as posted but remove the innertabulara s currently everything is in a one-row one column tabularx– David Carlisle
yesterday