SharePoint Training and Internal Communication
Thursday, August 21, 2008 9:38 AM

Note to self:

Here are some packaged solutions available to help make the user community aware, prepared, and excited.

PKS
 Office Online

Office Online SharePoint Help

 Office SharePoint Server 2007 Training built on SharePoint Learning Kit

Here is a screen capture video showing how it works.
The SharePoint Learning Kit (SLK) is government SCORM compliant, and can be used to deliver and track any training that uses the SCORM XML course definition. The Office SharePoint Server 2007 training is skinned and contains courses for SharePoint users.

SharePoint Internal Buzz Kit

The Internal Buzz Kit is designed to help you generate demand for your newly deployed SharePoint Server 2007 sites, increasing your Return on Investment.
You may need to revise some of the pieces in the Kit, depending upon your particular deployment environment and company policies.
You may download all the materials in one file, or download them separately

by wkriebel | with no comments
Filed under:
Official Blog Icon?
Thursday, August 21, 2008 9:11 AM

Interesting.  Is this the "official" blog icon?
Not terrible.

http://office.microsoft.com/global/images/default.aspx?assetid=ZA102499971033

blog

Bigger

blog

See it in action here: SharePoint 2007 Help and How-to

by wkriebel | with no comments
Locking Your Computer with a Script
Thursday, July 10, 2008 11:42 AM

For humans: ÿ-L

For computers: %windir%\System32\rundll32.exe user32.dll,LockWorkStation

So cool.

Command line source: Shutting Down Computers and Logging Off Users: TechNet

by wkriebel | with no comments
Filed under:
Model Driven Development
Monday, June 30, 2008 1:31 PM

A great post by Gabriel: Valuing the Undervalued Solution Model

Interesting Read: The Next Revolution in Productivity
Friday, May 16, 2008 8:50 PM

http://harvardbusinessonline.hbsp.harvard.edu/b01/en/common/item_detail.jhtml;jsessionid=R13ZGBCSYGIIUAKRGWDSELQBKE0YIISW?id=R0806D&referral=2341


Link: Managing social networking with Microsoft Office SharePoint Server 2007
Wednesday, April 02, 2008 1:19 PM

Eric mentions an interesting document he co-authored about SharePoint as a social networking platform.

Here is a direct link to the Word doc.

by wkriebel | with no comments
Filed under:
SharePoint for Squirrels
Wednesday, March 19, 2008 4:15 PM

Admittedly, I haven't read to far into this site, but I'm link blogging it because, hey, even Squirrels need a little SharePoint now and then:

SharePoint for Squirrels
by wkriebel | with no comments
Filed under:
Conducting Estimation meetings with Project
Wednesday, March 19, 2008 1:21 PM

Often an engineering team is asked to predict the future amidst uncertainty.

One way to efficiently drive estimation meetings in this environment is to use the Program, Evaluation, and Review Technique (PERT).

Here is the official article that describes this: Use a PERT analysis to estimate task durations

You can expose the PERT Analysis Toolbar by right-clicking anywhere in the toolbar and enabling "Pert Analysis":

 image

You can then click on the PERT Table button PERT Entry Sheet and you get the resultant table:

image

This is also available through the Tables menus: 

imageimage

image

 

Note: The PERT Table is using the fields Duration1, Duration2, and Duration3 and renaming them.  If you are also using these, your values will show up here, and changing the values in this table will change them wherever else you are using Duration1,2,3.

 

You can now quickly go through the meeting asking questions like: "How long do you think this is likely to take?" (expected)  and "If that obstacle or constraint is removed, then how long would it take?" (optimistic) and "If that assumption doesn't play out, then how long would it take?" (pessimistic).

When you are done with the session, click the Calculate PERT button Calculate Pert and using the default weights (1:4:1) Project will update the Duration field with a calculated duration.

I recommend having the notes field open and documenting the pivot points of the conversation for each task. Split the Window, the show the Notes pane:

  1. Window:Split
    Split
  2. Right-click in the entry pane, and select Notes
    Show the notes pane

See also:

by wkriebel | with no comments
Filed under:
Project Summary Task Summing Incorrectly
Wednesday, March 05, 2008 12:51 PM

I was asked recently about summary tasks showing sums of work columns that were too large.

This is caused by summary tasks that have carried their resource assignments from when they were non-summary tasks.

Steps to Reproduce

Here is how it occurs.

  1. Create tasks and assign resources
    task list
  2. Insert a new task amidst the others and assign a resource
    new interim task
  3. Indent the new task using the image button
    indent to subtask 
    In the above shot, notice that the summary task is now larger than the sum of its children

Resolution

Remove the resource assignments from the summary task:

fixing it

by wkriebel | 2 comment(s)
Filed under:
Email Links Enhanced
Friday, February 08, 2008 12:15 PM

Even in the web 2.0 world, often times the most cost effective way to set up a collaboration mechanism is an email distribution group.  How often do you see:

For support contact THISAPPSUP. If you need permissions, send mail to THISAPPLEADS.
If you were really on the ball, you would set up a list or form that had all of the fields and pre-requisite questions, but I understand, sometimes that gets de-prioritized. However, there is something in between that is about as easy as posting the above, but makes it so much easier for you and the user contacting these aliases.

It's our old friend MailTo.

If nothing else make the email addresses hot.  Such as <a href="mailto:thisappsup">THISAPPSUP</A>

But wait, for not that much more effort, how about this.  They click on the link, and instead of just firing up an email, it gives it a little more structure:

image

Maybe not web 2.0, but at least web 1.1:

For support contact THISAPPSUP. If you need permissions, send mail to THISAPPLEADS.

Here is the mailto code: 

<a href="mailto:thisappsup?Subject=Support Request for This App&amp;Body=This App Support Team, I need help with This App">THISAPPSUP</a>

This way you can help give a little structure to the mail request. Even though the sender can still change things, it will still help speed things up and structure it more.  It will also help differentiate sources of the mail if mail groups are used for multiple purposes.  For example, you could include a reference to the page from which the mail is being sent, or a version number.

Note: The email addresses in this post are purely fictitious. The links will initiate an email message, but don't expect that the example recipients will actually work. :)

See also: MailTo Protocol

More Posts Next page »