Interested to Buy Any Domain ? << Click Here >> for more details...
Why should project managers complete hard problems first in
an OOSAD project?
- 3 Answers
- 9895 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 |
What if we override the conflicting method in the class?
How can I be thrown polymorphically?
What are the rules to define a functional interface?
Explain what you understand by function overloading.
How can we restrict inheritance for a class so that no class can be inherited from it?
What does the keyword virtual represented in the method definition?
When will you use an interface and abstract class?
What is the use of Operator Overloading?
Explain about multiple inheritance?
What do you mean by operator overloading?
What is the difference between an interface and abstract class?
What is the difference between abstract & interface?
Design Patterns 
