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 |
what three "domains" are considered during analysis modeling?
What is the difference between abstract & interface?
What are the methods required to create changes in subclasses?
Are constructors inherited? Can a subclass call the parent's class constructor? When?
What are the features that are provided to make a program modular?
What is the use of Operator Overloading?
How will you define abstract classes?
What are the different types of arguments?
Explain about encapsulation?
Comment: C++ "includes" behavior and java "imports"
Explain the different types of constructors
Can encapsulation be called as a security device?