Why should project managers complete hard problems first in
an OOSAD project?
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 |
Which OOPS concept exposes only the necessary information to the calling functions?
What are the major differences between late and dynamic binding?
Explain serialization and overriding?
How to use CRC Cards for Class Design?
Write a note on encapsulation?
What is the use of ‘finalize’?
What is difference between polymorphism and normalization?
What is the default access specifier in a class definition?
What is abstract method?
Why is class hierarchies managed in object-oriented programming?
Differentiate between overloading and overriding.
Define modularity?