Blogs

As of December 2008, the PMBOK released the 4th edition.
Find out what's changed between the 3rd and 4th edition in the attached document from Global Knowledge.

948 visits came from 42 countries/territories in January and February 2009

15 countries in the last 4 days (March)

• Create the plan
• Remember the 80/20 rule (see the pareto principle below)
• Not just status updates
• Stop micro managing
• Don’t do the work
• Create a To-Do List

• Make interruptions the exception rather than the rule.
• Allocate large chunks of time to individual projects. 
• Don’t take on too many projects. 
• Reserve time for self-improvement. 

Pareto Principle: the Pareto Principle, also known as the '80:20 Rule' states that 80% of efforts that are not time managed or unfocused generates only 20% of the desired output. However, 80% of the desired output can be generated using only 20% of a well time managed effort.

You like Excel 2007 Data Bars?

Well, you can do something similar using a function for previous versions:

Get your version (still in beta): http://www.gladinet.com/p/download.htm

1. Projects with realistic budgets and timetables don’t get approved.
2. The more desperate the situation the more optimistic the progress report.
3. A user is somebody who rejects the system because it’s what he asked for.
4. The difference between project success and failure is a good PR company.
5. Nothing is impossible for the person who doesn’t have to do it.
6. Every failing, overly ambitious project, has at its heart a series of successful small ones trying to escape.
7. A freeze on change melts whenever heat is applied.
8. You understood what I said, not what I meant.
9. If you don’t know where you’re going, just talk about specifics.
10. If at first you don’t succeed, rename the project.
11. Everyone wants a strong project manager - until they get him.
12. Only idiots own up to what they really know (thank you to President Nixon).
13. The worst project managers sleep at night.
14. A failing project has benefits which are always spoken of in the future tense.
15. Projects don’t fail in the end; they fail at conception.
16. Visions are usually treatable.
17. Overly ambitious projects can never fail if they have a beginning, middle and no end.
18. In government we never punish error, only its disclosure.
19. The most difficult way is, in the long run, the easiest.
20. A realist is one who’s presciently disappointed in the future.

Source: http://blogs.techrepublic.com.com/tech-manager/?p=881

A great example of what technology can do for a LIMS, ELN and SDMS across an ESB using standards and WS…

Excellent!

Original Post: http://www.room362.com/archives/278-The-History-of-the-Internet-VIDEO.html

“classic mistakes” are mistakes that have been made so often, by so many people, that the consequences of making these mistakes should be predictable and the mistakes should be avoidable.

Top 10:

1. Unrealistic expectations
2. Overly optimistic schedules
3. Shortchanged quality assurance
4. Wishful thinking
5. Confusing estimates with targets
6. Excessive multi-tasking
7. Feature creep
8. Noisy, crowded offices
9. Abandoning planning under pressure
10. Insufficient risk management

In a recent survey, over 40 classic software mistakes were identified (see the attached document for the details of the survey results)