"Failure is pillar to success". But many times we fail to utilize this. Following are some simple but effective guidelines. I hope it will help you.
1. Don't sugarcoat the situation.
Present the facts in a realistic manner.
Don't overestimate the likeliness of recovery.
Explain the consequences in concrete terms.
2. Divorce the failure from the people involved.
Don't think in terms of "blame."
Don't use the names of colleagues and reasons for decision failure in the same breath.
Bear in mind that many decisions fail as a result of pure chance and bad luck.
Also take to heart the notion that people often have less control over decisions and their implementations than you may have assumed.
3. Form a review team.
Compose the team of members most directly affected by the decision failure.
Include participants who have the ability to implement backup plans.
Contexts and Dependency Injection (CDI) is one of several Java EE 6 features that help to knit together the web tier and the transactional...
MongoDB is the most popular No-SQL database. Lets try it out: 1) Install: Go to the MongoDb website and download latest release....
Javabench is a collection of Java tutorials, sample code / examples, articles, interview questions & answers, OCP JP (formerly SCJP) qu...
Some are common, but some are very core technical, senior level questions: 1) What's difference / comparison between hibernate and I...