ONLamp.com: Collaborative Document Editing with svk

Copied:
"Conclusion

Using branch and merge in svk as presented in the article can apply to any other version control system that supports branching and merge tracking and, perhaps, external merge tools.

Translation is an extreme type of article editing. The concepts here can also apply to conventional editing. Make a branch for the article that you are proofreading. When the author sends an updated version, you can smerge the changes painlessly, retaining the modification you made, or vice versa.

Chia-liang Kao is the original author of svk and the Perl bindings for Subversion. "

MS Project Training: Kansas University courses - Free

If you really want to learn, play with the software itself, check all its features. I am a do it myself person and do believe the things that one learns by itself are better learned.
However, this course is fearly good.
Also: http://www.k-state.edu/InfoTech/epm/training/index.html

Choose the right vendor: Size does matter

The win-win relationship that you have with your client is critical. A
one person small business can be the right choice for a multi-million
revenue public company. Fortunately there are thousands of examples.

What about a partnership to provide a new service or scalable solution
to that key costumer of yours? Be careful who you partner with.

I've been confronted with a small business that had the opportunity to grow their business by providing a new service to one of their key
clients. Considering the importance of the opportunity the CEO decided
to sacrifice some of the possible margin they could get and partner with
what he believed would be the best service provider his company could afford. The
decision was to work with a leading public company. That partnership's
win-win interrelation was suposed to be clear: one will provide the top
level service, the new partner will have chance to get to a client
they've been chasing with not much success.

However there was a major misbalance between the importance of the
project for the small consulting firm and their partner. For our poor
small business, this was the biggest opportunity they had ever faced:
this opportunity will boost their revenue to a new level. For their
partner this project was not even 0,00025% of their annual revenue.

Guess what happened: at the first hickup it was clear that the
commitment to please and provide a good service was so dispair between
the two partners that the complete project was at risk. The project was
the top priority for the small business. It was just a minor small
action item in the PM's busy project portfolio of the huge public
company service provider. There are possibly even ethical issues that
could be analysed here but the result was simple. Project cancelled.
Disaster. Key account lost.

The intention was good, the choice for that partnership seemed to make
sense, but an essential rule was ommited: in a partnership relation,
the project you are involved with, has to be as important for you as for
your partner.