Why should project managers complete hard problems first in
an OOSAD project?
- 3 Answers
- 8680 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 are the tools you used for OOAD?
Which of the following is tightly bound ? Inheritance or composition ?
Why does java not support multiple inheritance?
Explain the use of Vtable and what are the various problems to override the functions?
What is the difference between public, private and protected access modifiers?
What interface must an object implement before it can be written to a stream as an object?
Can different parts of a partial class inherit from different interfaces?
How to define an interface?
How many methods are there in the serializable interface?
How to define an abstract class?
What is the @functionalinterface annotation?
What is the abstract method modifier?
Design Patterns 
