Interested to Buy Any Domain ? << Click Here >> for more details...
Why should project managers complete hard problems first in
an OOSAD project?
- 3 Answers
- 9764 Views
- I also Faced
- E-Mail Answers
Answers were Sorted based on User's Feedback
Answer / subrata
The query actually holds good in general for every situation in life. It is one of the principles of good time management.
The idea is to tackle hard (and important) problems first. This, if resolved - will pep up your confidence to deal with other not so hard issues. Also, this could have cascading effect on other issues that may get resolved on its own.
I would rather stress on "important" than "hard" issues. If a "hard" problem is not coming in the way of your deliverables (means it is not important) - keep it aside. There is no need to spend a lot of time on it.
| Is This Answer Correct ? | 4 Yes | 0 No |
Answer / ash
Its not necessary to do hard things first. Instead focus
should be on doing important things first. Important things
are core project features. Many features may be hard but not
necessary most important. Hence don't tire the team with
hard things but focus on important/core things first.
| Is This Answer Correct ? | 1 Yes | 0 No |
Do structs support inheritance?
Why is class hierarchies managed in object-oriented programming?
What is the abstract method modifier?
What do you meant by static and dynamic modeling?
Can I implement polymorphism using abstract class?
Can you define OOP and principles of OOP?
Explain about uml?
What are the tools you used for OOAD?
Explain the use of Vtable and what are the various problems to override the functions?
Difference: 'uses', 'extends', 'includes'
7 Answers Cognizant, Protech, TY, University,
Can we access interface static method using interface references?
Why is planning too much up front a mistake in an OOSAD project?
Design Patterns 
