Work, Estimated Work, Actual Work, Remaining Work and Work Variance All At Once

Here's a bit more detail on how you can track Work, Estimated Work, Actual Work, Remaining Work and Work Variance using either IntelliGantt or the IntelliGantt Add In for Microsoft Project with WSS 3.0/MOSS 2007.

First of all, you want to make sure your 'Workspace Settings' activate the work fields you need. For this example we will use all the Work Group and the Work Remaining fields, so we mark them as 'Members Read' and 'Members Write' like so:



You won't be able to set the 'Members Write' checkbox for Work Variance because this is a read only field. That is, the value is always computed.

When you share a project to SharePoint with these workspace settings, you'll have the work fields you enabled available for you to edit, like so:



In IntelliGantt or Microsoft Project, when you update 'Work' fields, you will see the ramifications to your updates immediately with schedule changes, percent complete changes or work percent complete changes. This makes it easy to also undo a change. With SharePoint, we get all the data at once and its up to IntelliGantt to make sense of it.

So how does it handle changes to Work, Estimated Work, Actual Work and Remaining Work at once? IntelliGantt enforces an implied order to your changes. That is, IntelliGantt will order the datastream coming back from SharePoint and evaluate the 'Work' fields in the following order:

1) Work
2) Estimated Work
3) Actual Work
4) Remaining Work

Because IntelliGantt has its own scheduling model, it can apply changes that affect the schedule as it works down the list. For example, let's say I only update the Work field. We see in the above example it is 16 hours. What if I make it 24 hours?



I click 'Update' in IntelliGantt and it communicates with SharePoint, performs its calculations and changes the list to...



Wait a second, what happened? The answer is that first it applied the change to Work, which increased from 16 hours to 24 hours. This resulted in the project model being updated. Estimated Work and Actual Work were unaffected by this change. Remaining Work, however, was affected. In the IntelliGantt model the Remaining Work value jumped from 6 hours to 14 hours; an increase of 8 hours-- the same 8 hours we increased Work by.

However, the value in the SharePoint field Remaining Work was still 6. It had not changed. So, as IntelliGantt worked through the order of 'work field' updates, it computed the difference between the IntelliGantt models Remaining Work and SharePoint's incoming data value for Remaining Work. That value? Negative 8 hours, which cancelled the 8 hours we just added. The model worked perfectly! :)

For those non-model types (myself included in this category), we can do a couple things to change behavior so that our Work update 'sticks'.

1) We can turn off the 'Members Write' flag for the Remaining Work field. If this flag is off, IntelliGantt will not receive the Remaining Work value, the difference won't be computed and therefore the model won't add the opposite of the Work value we put in.

2) We can update what we want the new Remaining Work value to be. If we add 8 hours to Work, then we can add 8 hours to Remaining Work. When IntelliGantt adds the new Work value, it will add 8 hours to Work and to Remaining Work in its model. As IntelliGantt works through its order of updates, when it gets to Remaining Work, it will compare the incoming SharePoint value with the value in its model-- and it will match. So no update will happen. Which means Work will be 24 hours and Remaining Work will be 14 hours.

Would you believe there's actually a third way to update Work without updating two fields or performing any match? Remember that these work fields are processed in the order defined above: starting with Work and finishing with Remaining Work. We can take advantage of this and only update Remaining Work like so:



When IntelliGantt processes the incoming data, it will evaluate the work fields as follows:

1) Work -- No Change
2) Estimated Work -- No Change
3) Actual Work -- No Change
4) Remaining Work -- 8 hour change therefore add 8 hours to Work

Of course, we don't want to always add to our work load. We also want to get things done. This is best done by changing Actual Work to reflect how much work you've done and then by changing Remaining Work to reflect how much work you believe is remaining. For example, with our original values:



Let's say I've actually worked (yes, hard to believe) an additional 2 hours but believe there's still 5 hours remaining. In this case, I would add 2 hours to the existing 10 hours in Actual Work and subtract a single hour from Remaining Work.



When IntelliGantt performs a synchronization, it will do the following:

1) Work -- No Change
2) Estimated Work -- No Change
3) Actual Work -- Add 2 hours and, by implication, subtract 2 hours from Remaining Work
4) Remaining Work -- Add 1 hour and, by implication, add 1 hour to Work

The end result will look like this:



Granted, it is easier to simply modify the percent complete field and call it good. But if you'd like to be more rigorous than percent complete updates and want to start tracking hours, simple math with Actual Work and Remaining Work can lead to powerful results.

Working with SharePoint Members as Project Resources

We get this question quite a bit so we've posted a 'Best Practices' page explaining how both IntelliGantt and the IntelliGantt Add In for Microsoft Project work with SharePoint members. They also work with Outlook contacts and resources you add manually, but the SharePoint case is the most interesting.

The two use cases this page covers:

1) Building a simple resource pool from a SharePoint site
2) Turning resources that are really roles into actual SharePoint members (and yet they're still project members-- it's magic!)

Well, not quite magic. Basically, it all comes down to the email address. In MS Project, resources support an Email Address field. This is not in the default view so you have to insert the field into the 'Resource Sheet' view. If the Email Address field for an MS Project resource matches the Work Email field of a SharePoint member, they're connected! That's the manual approach.

Because connecting resources to SharePoint members requires this bit of housekeeping, there's really a third reason for the 'Best Practices' page-- how to add 'SharePoint Approved' members as resources to your project. With the IntelliGantt People pool, once they've been retrieved from SharePoint its as simple as clicking a checkbox.

Hopefully the 'Best Practice' page is more than a good read-- we want it to be helpful too!

IntelliGantt API Update

Just posted a simple 'Getting Started' document that explains the general concepts behind the IntelliGantt API and supports the accompanying sample application. Our goal is to make it very easy for system integrators to connect MS Project and WSS 3.0/MOSS 2007. For example, a hosting provider can easily add a feature that takes an MPP file and fleshes out a task list.

With this API, you will want to install IntelliGantt V4 on the same machine as the sample application. The sample application's reference paths assume you install IntelliGantt V4 into the default C:\Program Files directory.

Since you can now install IntelliGantt V4 on 64-bit machines as well, you may find the sample app doesn't find the references. This is because Windows 64-bit will append Program Files with a (x86). So you will want to update references in this case from:

C:\Program Files\TeamDirection\...

to

C:\Program Files (x86)\TeamDirection\...

You can get the API and documentation from our forum here.

Supporting Actual Work and Remaining Work on SharePoint

We enhanced both the IntelliGantt rich internet application and the IntelliGantt Add In for Microsoft Project recently to better support updating Actual Work and Remaining Work via WSS 3.0 and MOSS 2007. With IntelliGantt RIA it was a snap as our model has proven to be very accurate, especially how we handle Estimates and Actuals.

So we thought it would naturally fall out for the IntelliGantt Add In for Microsoft Project since they both share the same code base. But what we discovered was this:



Notice that each task has a duration of 2 days and a work of 24 hours. We started with with three tasks of 2 days duration and 2 days work. With Task I we set Actual Work to 8 hours and Remaining Work to 16 hours. This increased the Work field to 24 hours and gave us new % Work Complete, % Complete and Actual Duration values. With Task II we set Actual Work to 8 hours and Remaining Work to 16 hours. This increased the Work field to 24 hours and gave us a similar % Work Complete value. However, you'll notice quite a few differences between Task I and Task II: the same action gave us different % Complete and Actual Duration values.

This makes it really difficult to build a model for.

Finally, for Task III we did the exact same steps as above, but then typed in the same % Complete value (56%). MS Project took that value and slightly changed Actual Work, % Work Complete, Remaining Work and Actual Duration.

After studying the issue for a while, and working with our customers, we determined that the % Complete field is the key. Because this field can be arbitrary when updating Actual Work and Work Remaining fields, the solution is to NOT update the % Complete field and just let MS Project do its thing. IntelliGantt can then update and maintain the Actual Work and Work Remaining fields correctly-- and MS Project will maintain them correctly as well.

Everybody wins!

This investigation had an additional benefit in that it spurred us to create a form that a) let's you configure for this option and b) change the default behavior for automatically updating estimates and actuals.

Before, because we've been worried about automatically updating actuals and thereby automatically updating your project schedule, we had people 'Apply Actuals' so there wouldn't be any surprises. With the new usage model, project managers can tell IntelliGantt it's OK to update actuals immediately. Again, this makes it easier to use the Actual Work/Remaining Work update method. IntelliGantt is smart enough so that only the 'Actual Fields' you enable via IntelliGantt->Project->Settings will be applied.

Finally, you'll notice that you can set which Baseline you'd like to use for the current Estimates values. This makes it easy to create multiple baselines but still have an 'active' one that SharePoint members can view.

With build 4.0.0.139 the menu addition under IntelliGantt->Project, as shown below:



We have a help page explaining estimates and actuals options in greater detail. Better yet, you can try either our Rich Desktop or Wicked Smart Add In and see what you think.

Tasks go Here, Milestones go There

A customer asked me about an interesting scenario recently that I thought I'd share. As you know we've been focusing on the more project-centric templates from the 'Fabulous Forty' produced by Microsoft, but we haven't shown how you can roll up tasks and milestones and send subsets of information to specific lists in these templates. In this particular case, IntelliGantt shared tasks and milestones with full 2-way synchronization to the Project Tasks, but they also wanted to send milestones to the Project Milestones list that was also present in the site. The Project Milestones list was an easy way for stakeholders to quickly see a 'big picture' based on milestones being completed or not.

We thought this might happen, so we engineered IntelliGantt such that in addition to sharing individual projects, it could also 'export' groups of projects to lists of your choosing. For example, say we have two projects that have been shared to a Project Tasks list like so:



The Project Tasks list contain tasks and milestones and are handily grouped by their projects. While this example is trivial, imagine 500 tasks and 5 milestones. In this case it because more difficult to spot the major events designated by milestones-- they may be below the viewing fold or on another page altogether.

What would be nice is if we could roll up the two projects, filter out milestones and send them to the Project Milestones list.




Happily we can do just that by using IntelliGantt's dashboard and filters. The Dashboard option is right under the IntelliGant menu in MS Project (the IntelliGantt rich client has multiple ways to export rollups; this example is mainly for MS Project).



The dashboard is populated by clicking the checkboxes next to the projects on the left hand side. Every project you have shared will be listed there. You may want to check everything, or just a set of projects you want to work with. Because we only have two projects shared, we will select them both.



Once we have the projects we want, its time to send the items on their way. Click on the 'Export' button to start this process.



This brings up the 'Export Wizard', which is based on the 'Share Wizard'. Just as you would share a project, first you supply the SharePoint site URL and click 'Go'. The list of available web parts supporting tasks and milestones appears. This time we will select the Project Milestones list.



Finally, we just want to export the milestones from our two projects. To do so we will invoke the 'Workspace Settings', drop down the 'Filters' and select 'Milestones Only'.



Click 'OK' and then 'Next' back in the Export Wizard and IntelliGantt will send your milestones the the Project Milestones list you selected.



Now it is important to note this is different than sharing. You won't be able to synchronize these milestones. For this particular example, subsequent exports will use the 'Clear Task List' option so that only the most recent milestones populate the list.

However, as a means to quickly send important data to one spot where people know to look is very useful. IntelliGantt makes it easy to roll up projects, apply filters and send the result to the spots you need.

IT Team Workspace Integration

Continuing our philosophy of being the data conduit from your desktop to all those rich internet solutions, we've verified that IntelliGantt works well with the IT Team Workspace template for WSS 3.0. Again, its one of the 'Fabulous Forty' that Microsoft produced and follows the same design pattern of a Projects List to contain project summary and a Project Tasks to contain tasks. The Project Tasks has a Lookup ID that binds a task to a project, which IntelliGantt is happy to do for you so you don't have to for each task in your 1000 line project.

I suspect we will be verifying a few more rich SharePoint templates that follow the Projects List and Project Tasks pattern. Another template we've been thinking about is Timecard Management, which makes a lot of sense as a means to show off the new Timesheet feature in IntelliGantt.

In truth, though, we are 100% customer driven with which SharePoint templates we integrate with. In fact, if you're using a template from another vendor or one developed in house, we'd be happy to hook it up to MS Project or to our IntelliGantt desktop and leverage your investment.

We have a 'Best Practices' page up for the IT Team Workspace. On to the next template!

Sometimes the Solution is too Simple

Being a client application that communicates via web services with SharePoint, there's always been one sticking point-- the transition from the client app to SharePoint. That is to say, you have IntelliGantt or Microsoft Project with your project data in one window and SharePoint with your team view in another window. Mouse clicks, Alt+Tab or tiling-- sure there are band-aids. But context swtching is usually the bane of good software and its irked me for a while now.

So a brief context switch... My wife was out of town recently, so I had the two bambinas for a few days all to myself. Obviously, this meant no time in front of the computer. We had great time going to the children's museum, the zoo, the park... lots of kids stuff. After a few days of running around the house, it was time to clean it (especially before the wife returned). After I had cooked breakfast and did the dishes, wiped the counters and changed a diaper, I started vacuuming.

And then it hit me.

You know, IntelliGantt has a Grid/Gantt view and a Dashboard view, why not embed a web browser as another view so you can see your SharePoint tasks in context. Kind of like this:



This is great for a few reasons:

1) It houses IntelliGantt and SharePoint tasks in the same context.
2) It seeds the site URL values when I want to share, export or import.
3) The SharePoint view changes as I select shared projects in IntelliGantt.
4 It captures the powerful 'Dual View' of what the project manager can see and what SharePoint team members see.
5) IntelliGantt changes as I select shared tasks within IntelliGantt!

We've captured the basics in a screencast, but I wanted to expound a bit more on it because, practically, I'm quite pleased with the results. Typically, when I demonstrate IntelliGantt, there's an awkward 'and now I'm changing hats and viewing the project through a web browser' segue. And when I return to IntelliGantt, the reverse seque. And back. And forth.

Now, we can all stay in the same application. Because it embeds the IE web browser, it handles SharePoint the exact same as IE-- adroitly navigating authentication challenges and single sign on issues. Better yet, because the browser is running in the IntelliGantt process space, you don't have to login twice.

What is most powerful, however, is point #4 above-- exploiting a huge advantage that Software + Services provides. The advantage is a rich application with appropriate tools designed for project manipulation combined with a robust collaboration platform with authentication and data views designed for project communication.

A team member doesn't need a powerful scheduling engine in order to see when one of her tasks is due. Similarly, a project manager needs more than a web interface when updating thousands of task start and due dates. Or, more bluntly, would you rather update 1000 tasks in SharePoint by clicking 1000 task edit links, updating at least a start and end date for each, clicking 'OK' and hoping the changes are correct? Or, would you rather open IntelliGantt, click and hold the mouse on the project bar and drag it forward a couple days? One might take 2 hours and is prone to error and the other would take about 5 seconds.

The right tool for the right job... and now all in one context.

I should play with the kids more often!

Working with the Budgeting and Tracking Multiple Projects template

Last week at SPTechCon I did a session on SharePoint project management using WSS and out-of-the-box lists, webparts and templates. The session received a good response because many people are unaware just how much is available with WSS, especially with the 'Fabulous Forty' templates Microsoft produced. And because its WSS, its all free.

Aside from the 'kid in the candy store' aspect of so much functionality a mere download and install away, its worth taking a look of several of the templates and seeing how useful they are for managing projects-- even multiple projects. For example, the template we spent the most time on is called Budgeting and Tracking Multiple Projects. Not only does it have a task list, but also a project list and even a dashboard to aid in monitoring project health!

As a result of the feedback, we created the first of several web pages on the TeamDirection site highlighting both the functionality and how IntelliGantt integrates with it. This particular template is greatly enhanced when paired with IntelliGantt.

For example, to really exploit the value of the Budgeting and Tracking Multiple Projects template you need to create multiple projects each with multiple tasks and link projects to tasks by updating each tasks lookup ids. Not only is that a run-on sentence, but it takes roughly thirty seconds to do per task. If you have a project of 1000 tasks, that time adds up very quickly.

However, with IntelliGantt you can make all the associations in under 30 seconds total! You project manager (or intern changed with updating all those tasks) will thank you.

The rich integration is provided by both IntelliGantt and the IntelliGantt Add In for Microsoft Project. If you already have MS Project 2007 in-house, we encourage you to check out our Add In. If you don't have MS Project or are looking for 'Project Lite', check out our rich client. Either way, we're happy to help you get the most from SharePoint.

If Anyone is at SharePoint Technology Conference Wednesday or Thursday

SPTechCon is running from January 27 - January 29th. Somehow it still snuck up on me.

I am speaking at two sessions. The first session (407, January 28 at 2:45) is a deep dive in to SharePoint web services and how desktop applications, rich internet applications or even Silverlight and Flex can connect and update data. I'm pinging our hosted WSS server right now and retrieving lots of fun XML to go over!

The other session (805, January 29 at 1:30) covers out of the box project management. I'll be highlighting the project management goodness that comes with SharePoint: task list, project task list and dashboards. I'll also be using the latest 64-bit build of the IntelliGantt BETA. Gave me a good excuse to get a new laptop-- needed a test machine!

Publishing Multiple Projects to One SharePoint Task List

We just got a question from an IntelliGantt evaluator that calls to our attention a really great feature that we didn't expose very well. That is, the ability to publish multiple projects (and their tasks, of course) to a single SharePoint list. Customers had asked for this with the previous version of IntelliGantt (the Plus version) and therefore we added Multiple Project Export to version 4.

First, check all the projects you would like to be active by clicking the checkboxes in the 'Projects' view on the left. Then on the right, in our Grid/Gantt control, click the 'Export' button (highlighted in red). This will bring up the export wizard and will allow you to send this group of tasks as a whole to a single task list.



You also might want to use Workspace Settings and apply additional filters to what will probably be a large group of tasks. For example, you can apply the 'Milestones Only' filter so that only milestones from all the projects are sent to SharePoint. Other interesting filters are 'This weeks tasks', 'Next weeks tasks' and 'Summary tasks only.'

Even more filters are available, but you get the idea. IntelliGantt helps you round up groups of projects and send the important information to SharePoint.

IntelliGantt API Example

Several of our clients have been very interested in using IntelliGantt APIs to customize the integration between Microsoft Project and SharePoint. We're happy to oblige and have just posted a Visual Studio 2008 C# solution that shows how you can:

1) Share projects to SharePoint, Local and Cloud workgroups
2) Update projects on SharePoint, Local and Cloud workgroups
3) Unshare projects from SharePoint, Local and Cloud workgroups
4) Create SharePoint task lists based on template IDs
5) Modify Workspace Settings, which in turn modifies the SharePoint task list when updating
6) Import project plans from MS Project
7) Read (ie. update) changes from MS Project to IntelliGantt
8) Export projects to MS Project
9) Write (ie. update) changes from IntelliGantt to MS Project

We opened up a new forum section to introduce and support the API as we start getting feedback-- and ideas!

The other part of this effort was creating a traditional MSI package to install IntelliGantt. This makes it easier for the example to reference IntelliGantt dlls since the ClickOnce installation generates human unfriendly paths and names, whereas the MSI puts assemblies in Program Files\TeamDirection\IntelliGantt.

(As a bonus, this also addresses deployment to Citrix environments, like Xen. Now the IntelliGantt executable can be explicitly identified and shared as a published resource.)

For the purposes of this API example, you'll want to install the MSI package first, and then unzip the C# solution.

The example doesn't show much in the way of actually working with a Project schedule. What it does show is just how amazing the SharePoint web services API is. Keep in mind that this is a client only install-- nothing is needed for the SharePoint server. (You can run this example against a hosted SharePoint server if you'd like). And yet you can do just about anything needed to move data back and forth. This means the door is wide open for integrating your project data with SharePoint services. We've tried to make the API as accessible as possible-- as easy and intuitive as the UI is-- but look forward to your feedback to see how well we've succeeded.

If you're curious about IntelliGantt's scheduling engine, you can do an Object Browse on the TDINETProjectModel assembly and see all it exposes. Most of the public names will make some sense. For our next API example, we will create a solution that highlights IntelliGantt's robust and feature rich scheduling engine, as well as templates, resources, assignments, filters, hyperlinks and task dependencies.

Finally, check out some of those enumerations to get an idea of what just might be coming down the road!

Viewing SharePoint Tasks in a Calendar

[April 2011 Update - Integrating SharePoint Task and Calendar Lists]

In the last week or two I've started fielding more and more questions about viewing tasks in a calendar. It's usually along the lines of 'Do you guys have a calendar web part for tasks?'. To which I answer, 'you already have one in SharePoint'.

I don't see many quizzical response, most likely because these conversations are taking place over phone, but the quizzy vibes come through loud and clear. So I thought a little step-by-step primar illustrating how you can enable a calendar view in a standard, ordinary, run-of-the-mill task list would be helpful.

First of all, a SharePoint Task List is made up of three things: 1) a list, 2) task-specific fields (like Start Date and Due Date) and 3) multiple views. By default, you always have a 'raw data' view of all the fields, which, while utilitarian, isn't visually compelling.

The most popular view for a Task List is the Gantt View. But, as these past weeks have made abundantly clear, not far behind is a Calendar View. Thankfully, SharePoint task lists support multiple views, and a calendar is one of them. It is a bit different than the calendar web part, but still very effective for viewing your tasks across months, weeks and days.

On to the steps. Here is a task list being shown in a pretty Gantt view.



To see the Calendar view, we must drop down the 'View' button on the top right of the web part and create it. The menu pick is even called 'Create View'. (These images are kind of small on the page, but you can click on them to see more detail)



Clicking on 'Create View' takes us to this page, where we can choose the view we'd like. With every service pack, and especially with every major release, its a good idea to check out this page and see if any new goodies.... er... views are available.




Clicking on the 'Calendar View' takes us to the next page which lets us name and configure it. First we'll think long and hard and give it an original name like 'Calendar View'. You see a few options as well. Whether you you want to make this public and even the default view is influenced by how you want to configure it, as we will see shortly. For now, we'll move to the next batch of options.



Most commonly you'll simply choose the start and due date fields of your tasks for your Time Interval options. But, if you use a product like IntelliGantt, which allows you to modify the SharePoint task list to contain Actual Start and Actual Finish, then this is how you could create an 'Actuals' calendar. That will be an excercise left to the reader as I'll choose the standard start and due dates.



Calendar Columns is the next useful group. If you're asking 'why so many options?' for this group, its because you're defining a view within a view. That is, a calendar view can toggle among a month layout, a week layout or a day layout. First I'll define the titles for these three 'mini-views'.



To be honest, I'm not sure how the sub headings are displayed. But I chose 'Status' anyway.




Finally, we can click OK and see the calendar. But before we do, take note of the Filter options. There are two powerful settings you can use to make the calendar view a bit more dynamic: [Me] and [Today]. Me resolves to the current user logged in to SharePoint and Today resolves to the days date. The following two screenshots show how they can be used.




This will be another exercise left to the reader as our Filter options will look like this:



So where's this magical calendar view we've been working on? Click 'OK' and...

The Month view




The Week view




The Day view




We're done. We've created a Calendar view of our Task List for everyone to use. However, one problem remains: how do I get all my tasks in to this Calendar? Do I have to add them one by one by hand?

That's where we come in. My company makes IntelliGantt and the IntelliGantt Add In for Microsoft Project. We make it so easy that its actually fewer steps to add all your tasks than it is to create this calendar view.

If you'd like to see them in action, we have IntelliGantt screencasts and Add In screencasts. Better yet, though, if you'd like to exercise IntelliGantt software yourself, we have 15-day fully functional free trial.

Summary Execution with Microsoft Project

After having explored the benefits of Master Projects / Sub Projects in Microsoft Project I thought I'd introduce a way to tackle a similar problem from a different angle. In the immortal words of Monty Python:

And now for something completely different.

While there are many master projects with embedded, self-contained sub-projects, there are just as many, if not more, really large projects that span the deliverable in its entirety but baffle the team members with its complexity. We designed the next version of IntelliGantt to not only manage large projects in its user interface, but to also help manage large projects using Microsoft Project as well.

Why?

Because-- and I'm happy to admit this-- you shouldn't use IntelliGantt to build a nuclear power plant. Or an advanced airplane with all carbon-composite parts. For these types of projects you need the power of Microsoft Project and its million features to aid in the billion permutations that will happen along the way.

However, with IntelliGantt you can apply one of the simplest, most effective strategies-- Divide and Conquer.

V3 IntelliGantt Plus introduced the concept of identifying a summary task in Microsoft Project and working the project in IntelliGantt Plus. This worked fairly well, but customers told us we needed even more integration so that results could be written back to Microsoft Project when needed. Furthermore, reading new input from Microsoft Project was required to support big change events in the over-arching project plan.

The result is probably the richest integration of Microsoft Project of any application on the planet. With version four of IntelliGantt you can ask MS Project to open a project plan, select a summary task as your scope of operations, work with just the pieces that you need for and, finally, update the orginal plan with your results.

This gives you and your team several benefits

1) You work with a limited set of information thereby reducing complexity
2) Your team works with only the information they need
3) Nobody sees information they don't, or shouldn't, need
4) You can increase througput by having multiple project managers execute their pieces and letting IntelliGantt coordinate the updates
5) IntelliGantt let's you share project data with people that wouldn't normally have access-- like consultants outside a firewall.

We most definitely like Microsoft Project to be responsible for the heavy lifting when working with large projects. But IntelliGantt's rich collaborative abilities along with its nonpareil MS Project integration let's you open up the pieces to your project plans in ways not possible before.

Instead of working with one giant project en masse, IntelliGantt lets you work with and complete task groups defined by summaries. The best part is the bigger the project, the more effective dividing and conquering can be.

And yes, we have an excellent screencast showing this cleverness in action.

Working with Master & Sub Projects

More than a few customers have let us know the importance of supporting Microsoft Project's Master Project / Sub Project configuration. It certainly makes sense because it gives you a nice rollup view and, more importantly, a convenient way to create and manage shared resource pools.

We're happy to introduce support for a Master Project / Sub Project scenario and, because the suggestions came from customers, we think folks will be pleased by the results.

As a brief overview, what we did was focus more on the sub projects and less on the master projects. By this I mean master projects really aren't 'updatable'. Rather, they are deriving their value from the collection of sub projects grouped in to the master view.

So what we did was make the behavior similar to if you were working on the sub project in its own window. That is, IntelliGantt recognizes when you have selected a sub project, or a task within a sub project, and adjusts its menus accordingly.

This lends itself to a very flexible way to share the pieces. That is, you could share all your sub projects in one SharePoint site. Or, if you really want to take advantage of IntelliGantt architecture, you could share every project to distinct SharePoint sites-- or even distinct SharePoint servers.

For example, one of the common use cases was a project manager with a master plan with two sub projects of completely different constituents. The first sub project might be for an in-house group whereas the second sub project might be with contractors who really don't need to know about everything (the life of a contractor :).

With IntelliGantt, you can share the first sub project to an internal server AND the second sub project to a distinct external host-- maybe even on the contractors own SharePoint server. Updates are scoped to the sub projects so the team members only see what they need. The project manager, on the other hand, can see everything together.

We think this matches the evolving needs of project managers to parcel out work for diverse teams.

But enough reading, check out the screencast and see IntelliGantt master the sub project landscape.

Overbooked Tasks and Overallocated Resources

My hats off to the engineering folks at TeamDirection for rethinking and reimplementing the 'Show Overbooked' filter in IntelliGantt. Very slick!

With my remaining hats, I doff them to our customers that took the time to give their feedback and help improve the product for everyone. Let's just say folks had a few ideas on how to better this feature.

The result plays very well with IntelliGantt's improved multi-project viewing architecture. In fact, touching on a the 'Sum is greater than the Parts' theme, it's really two different systems playing very well together-- Multi-Project View and Task Filtering. Each can be used by itself, but together these two systems solve two rather severe limitations the old product had in identifying overbooked tasks and overallocated resources:

1) In V3 only projects within a single folder could have the filter applied
2) In V3 the filter only went to 'day' granularity. That is, if a task was less than 1 day or a resource was less than 100% utilized... well... version 4 is here!

With IntelliGantt V4 you can select any combination of projects you want, which should be very helpful when verifying that all the places you put your 'best woman for the job' are still in the same space-time continuim.

And of course, since IntelliGantt 4 supports 'level of effort' per assignment, the filter also does a bit a match and recognizes that less than a day is ok.

Click on the image for the screencast and, if you really want to see IntelliGantt 4 in action, use this link to try it out yourself.

Warmer and More Efficient

We had to replace our natural gas furnace recently-- funny how that happens when a foot of snow falls-- and given that our old furnace was just a couple days under 20 we opted to go with a high efficiency replacement. I admit to being a tad skeptical by nature and all the claims of '95% Efficiency' seemed very much like EPA mileage estimates. But we did it anyway, deciding on a Trane 95XV which also has a variable two-speed fan.

I just happened to pay my gas bill today and happened to see last weeks gas usage on my online statement. It looks like this:



Guess which day last week we replaced the furnace? :)

And this is during our deep freeze when the temperature reached a cool (for the Pacific Northwest) 15 degrees Farenheit.

Export Microsoft Project Tasks to SharePoint

We covered importing tasks from SharePoint in to Microsoft Project. Now it's time to go the other way, as any flexible solution should-- exporting your tasks from Microsoft Project to SharePoint.

There are many benefits to this of course, from a high level benefit like keeping everyone on the same project page to a low level benefit like creating schedules in MS Project because it can simply be done faster than creating tasks in SharePoint. TeamDirection, and most likely Microsoft, thinks those desktop apps are still good for something!

In truth, sharing, importing and exporting are variations on a theme-- how best to 1) create and manage a schedule and 2) inform the team and solicit feedback. IntelliGantt's goal is to make it as easy as possible to move tasks to and from desktop products and collaborative products. In this case, with our IntelliGantt Add In, between Microsoft Project and SharePoint.

MS Project does at least one million great things-- but its not so good at being collaborative. SharePoint is an excellent collaborative environment-- but its not so good at creating project schedules.

One of our customers is a hospital that uses SharePoint extensively for exactly the right reasons. They want a common, known area for groups to view their important items of the day. They want individuals to be able to update those items and everyone to see the results.

The issue they were running in to was they needed a full time administrative assistant to merge the changes from MS Project and SharePoint together and keep the mpp file and the task list in sync. To do this would sometimes take up to one week!

With IntelliGantt, we brought it down to one click that the project manager could do on their own. The result was the administrative assistant's time was freed up, the project manager was empowered and the staff was confident that what they were seeing was up-to-date and that their changes were being captured.

We'd be happy to help your team too with our IntelliGantt Add In for Microsoft Project.

Importing SharePoint Tasks with MS Project

Which came first, the task in Microsoft Project or the task in SharePoint? We don't know either, so we made IntelliGantt just as smart importing tasks from SharePoint to MS Project as it is exporting and synchronzing them.

You can judge for yourself with the simple, informative screencast we made. The first question to ask is whether you want to just import tasks and be done with it, or if you want to import tasks AND remember where they came from. Thankfully, we don't know the answer once again, so IntelliGantt does both.

There's a compelling scenario for just importing tasks. For example, say you have 5 different task lists in SharePoint that have magically sprouted (these things happen!) and you'd like to consolidate them in to one SharePoint task list-- the fancy one with the Gantt chart. IntelliGantt can start from a single MS Project sheet and import many SharePoint task lists-- appending as they go. The result is those five SharePoint task lists of 10 items can turn in to a single MS Project plan of fifty tasks. Then you can then share it to a new task list with the permissions and features you need to manage the project.

The scenario for importing tasks in to MS Project and mainting the link to the SharePoint task list is straightforward-- that once simple SharePoint task list kept growing until it needed scheduling attention (your professional help). As you'll see in the demo, maintaining the link to SharePoint is as simple as clicking on a checkbox.

Given these two scenarios, there's really not a right answer or wrong answer-- just a both answer.

Project Managablement

I think we've all been on the project that takes 100% of our time and effort. How do you cope with the 10 others that require a mere 99%?

One of IntelliGantt's most popular features was multi-project view support. We've listened to your suggestions over the past year and have greatly improved the user experience. The end result is working with multiple projects is much more managable.

Before you had a free floating organizer with free floating windows for every project. This made it more difficult to keep track of everything. IntelliGantt has a new self-contained paradigm where all your projects are listed in a tree control on the left and your 'active projects' are on the right.

What's an active project? In the tree view, every project has a simple checkbox by it. If there's a check, its active and visible in the active view. If there's no check, its not active (ie. visible). Click a project to see it, click it again to make it disappear-- click the folder to bring all its children in to view.



In addition to making it very easy to flip in and out of projects, it also increases the power of our built-in filters. You can apply filters based on task properties and resources to many projects at once, make edits and turn the whole mishigosh in to a single, managable view.

IntelliGantt makes it easy. Check out the screencast for more.

Collaborating on Projects in a Cloud

Are projects in a cloud a good thing?

Most definitely.

Chances are very good you have a File Server handy to work on projects with colleagues. Your organization might even be lucky enough to have SharePoint available for rich collaboration and reporting. However, there are an awful lot of folks who need to communicate outside the corporate firewall (so no Local Workgroup) and don't have SharePoint available (either as an extranet or via a hosted provider).

In this case IntelliGantt helps a project manager work with a team across the internet by using Cloud Services (in our case, Amazon Simple Storage Solutions). Perhaps the coolest thing about this option is all you need is a client computer, an email address and an Internet connection. IntelliGantt (and Amazon) takes care of the rest.

After you create a project, schedule it and assign tasks, IntelliGantt let's you invite other people by a simple email. An IntelliGantt invitation invites them to the project. If they're a member, they can join and see the exact same view as other members in the project.

It's not done by smoke and mirrors-- it's a Cloud :)

This solution represents a realized vision of Software + Services. It's really no different than pointing a browser to a web site except for one important fact: The project data you are working with is on your machine.

This means you have a copy of it local, so you don't need to be connected to the internet in order to work. But more importantly, its really easy to integrate with your other Office applications.

If you're interested in seeing how IntelliGantt can connect team members with a cloud, you can try it out with a fully functional 15 day evaluation today.

What I Would Do With One Trillion Dollars

It seems to be the question of the day. Well, the very first question seems to be 'How much money do we need to solve the economic problem?' US$1,000,000,000,000 seems as good a starting place as any other amount.

So, should we:

a) Give a few large chunks to a few large companies that have failed because they are too big to fail?

b) Give many small chunks to many small companies, improve the odds that a number of small businesses can do a better job than a couple gigantic businesses and restart competition?

Its instructive to look at the last time a similar situation demanded evolutionary thinking. No, I'm not talking the 1930s.

I'm talking 63,000,000 BC, right before that meteor struck and nature had a choice: save the dinosaurs or give mammals a chance.

We've seen the financial meteor hit. Rather then pour US$1,000,000,000,000 into that impact crater, how about the Small Business Administration? Want US$10,000,000 to start a new bank? Great. And there would be money left over for 100,000 more. Think Tesla could use a few more dollars to bring its car to market? How about James Fallow's Day Jet ideal? Even my brother once looked in to starting his own credit card company.

Wasn't it a good thing that mammals got an opportunity?

Local Workgroup Screencast

Another day another screencast. They should be coming fast and happy now that the new version of IntelliGantt is coming in to shape.

This one focuses on the Local Workgroup option, which lets you use a simple Windows File Server as the collaboration hub for your collaborative projects. The configuration is usually a workgroup that has a shared drive or two. With IntelliGantt you just provide a UNC path and it handles the rest-- along with Windows User Account security of course.

I mentioned usually because we also have customers that use the Local Workgroup feature over their private high-speed fiber optic network connecting the US, India and Japan. It works great!

But if you can't afford your own line under the sea, I suggest you look at our Cloud Workspace. This takes advantage of all those 'cloud services' you've been hearing so much about and basically does the equivalent of that high-speed trans-continental fiber optic line for a fraction of the cost. But that's the next demo.

Check out this one as we show how the UI acts on multiple machines while collaborating on project. We also introduce the new Resource Pool and show how you can use the member lists in SharePoint and contact lists in Outlook to populate the IntelliGantt Resource Pool.

IntelliGantt Engineering Build

We've hit a milestone! TeamDirection has an engineering build available for everyone who's been curious what features the next release will have. I would definitely characterize this as pre-BETA, but some cool new features are working. Before I dive in, however, a word about our methodology.

IntelliGantt and IntelliGantt Plus have been shipping for about 18 months now and during that time we've received great feedback from our user base. We divided both the feature requests and the product direction we desired into three areas:

1. Must Have Features
2. UI Improvements
3. Technology Improvements

An example of a 'Must Have Feature?'. How about Level of Effort support for resource assignments and timesheets.

An example of a 'UI Improvement?'. How about an organized tree of projects on the left that, with a single click, adds or hides tasks in an active view. It's basically multi-project view at its most flexibile (and usable).

An example of a 'Technology Improvement'? How about building on the latest .NET 3.5 SP1 framework-- the one that really supports ClickOnce delployments for the internet!

We've actually been using ClickOnce with our IntelliGantt Add In for Microsoft Project and the results have been very good. When we receive bug reports from the field, we fix them, republish and everyone sees the new version automatically.

It's a great way to add features as well. Prior to ClickOnce, every release of IntelliGantt product would require some sort of notification for users to download the latest install package and reinstall.

No More!

It's given us the ability to do this early release so that a) we can incorporate real users earlier than ever in the loop and make a better product and b) users can see the results every week automatically-- both in terms of bug fixes, UI improvements AND new features. Philosphically speaking this is a huge advantage because in the past, the longer you develop in your engineering cocoon the further off the mark you may stray. Now our engineers will be primed to hit the marks you define.

With that, let us know what you think from the screencast, or better yet by downloading and trying the new UI out. We have an invitation page that doesn't require registering. We have a 'Top Ten' page that let's you know what our current working priorities are. We even have a purchase page that let's you buy at a steep discount as we move toward release. The idea is as the product gets better and better, the price should be revisited now and then. During this BETA period we will revisit the 'Go Live' price weekly. We figure its a great way to say thanks for your efforts.

A few housekeeping items on this release:

1) Not every single menu command is enabled right now. The core features that drive every menu pick are in, but we are curious which menu items are used more than others.

2) Everyone has manager privileges in this release.

3) Local and Cloud Workgroups are in and greatly improved from the last version.

4) SharePoint connectivity now requires WSS 3.0 or MOSS 2007.

5) MindManager 7 import/export is supported. MindManager 8 support coming within 30 days.

6) Reporting to the Bamboo Project Portofolio Dashboard is in.

7) Printing is fixed!

8) File associations are not quite in-- soon!

9) We have decided to consolidate IntelliGantt and IntelliGantt Plus in to one version-- IntelliGantt. It will have all the features (and more) of the old IntelliGantt Plus. The reason for this is everyone was buying IG+ so it really didn't make sense to have two versions going forward.

Thank you all for your feedback over the past few months. We look forward to the next phase and working with you to bring a great product!

IntelliGantt Add In for Microsoft Project Released

Just a note that the new version is now available on the TeamDirection site. The old version is also available for Microsoft Project 2003 and/or WSS 2.0/SharePoint 2003 users.

The new version is chalk full of goodies (more screencasts and case studies on the way!) and, because it supports ClickOnce technology, you'll see new features appear now and then as we listen and respond to our customer base. The best part is everyone will get these updates automatically without lifting a finger-- which is the way it should be.

Next up-- IntelliGantt Plus. We are targetting November 15th as the first beta of the new rich client. Because our experience with ClickOnce with the Add In has been so positive we will be making IntelliGantt Plus a ClickOnce application as well.

Also, we will be consolidating the two IntelliGantt rich clients (IntelliGantt and IntelliGantt Plus) in to one rich client, named ... (wait for it :)...

IntelliGantt

Thanks for everyone's help getting the Add In released. On to the rich client!

IntelliGantt Add In now supports ClickOnce

One of the hardest decisions to make as a software company is not only how to develop the bits but also how best to send them. I've long thought that web-based solutions are actually, from a user interaction perspective, a poorer experience than comparable rich client applications. The fundamental reason is HTML is a presentation environment with javascript and other 'glue' bolted on to aid user interaction whereas a rich client has the full power of your desktop to work with.

However, the delivery of a web-based solution has been so superior that it has tipped the balance in their favor. Given two equal applications, the web-based solution wins because the installation and update is as simple as a click (ideally).

Not that rich clients will ever go away-- after all, what is the browser itself? But they could certainly learn something from the efficiencies of web delivery. Thankfully, it looks like the latest incarnation of ClickOnce is on the right track.

Our 'old' IntelliGantt product suite (the IntelliGantt rich client and the Add Ins for Microsoft Project and Mindjet MindManager) were delivered with traditional installtion programs. However, rounding back to that initial 'delivery choice', we are using the very latest ClickOnce technology with .NET 3.5 SP1 to deliever the new releases.

Why?

1) Microsoft addressed the installation and security model to be on par with a web applications 'sandbox'.
2) They also built in automatic updating
3) They reduced the complextiy of actual installation (supporting frameworks, redistributables and such)
4) They're supporting a wider delivery path (Apache, Firefox, etc)

With the latest incarnation Microsoft also made a very wise choice-- support for servers other than IIS to ClickOnce distribution! This will have huge ramifications strategically (see OpEd below), but there are still a few hiccups we ran in to. Here's what we did to address them:

Make sure your web server supports the required mime types!

Our site runs on Apache and as such we had to add the following mime types in an .htaccess file in order for ClickOnce to download all the bits correctly:

AddType application/x-ms-application application
AddType application/x-ms-manifest manifest
AddType application/octet-stream deploy

These are described in detail on MSDN.


We also found out, by actually deploying our new Microsoft Project Add In to customers that the following mime type is needed for the VSTO file itself:

AddType application/x-ms-vsto vsto

With the possiblity that msu (microsoftupdate)and msp (microsoftpatch) are also needed.

We've been very pleased with the result as not only do users experience a seamless installation, but every update we make is automatically updated for all our clients as well. As a result, we've been able to respond just as quickly as a web-solution, download the bits just as easily and still take advantage of the tremendous power on everyone's desktop.



<OpEd>
Web solutions versus desktop solutions is really a battle between what will be the application container going forward-- to OS or the Browser. Didn't we go through this already with Microsoft and Netscape back in the late 90s? Yes, and Netscape lost. And so did Microsoft. Why? Because rather then answering the technology advantages of the web, Microsoft used their business advantage to carry the day. However, the door was still open in the weeks and months that followed. As a result, Google, among others, were able to walk through it and plant their flags.

Does ClickOnce finally start levelling the playing field? I think so, though in truth the lines will most likely totally blur between what is a desktop app and what is a web app. For instance, how different is a Flash package downloaded and run from cache in your web-browser than a .NET app downloaded and run in your OS?

Not much.

It's just nice to finally have some of the same tools that makes the web so successful. Good job to Microsoft's ClickOnce team!
</OpEd>

The Underappreciated SharePoint Issue List

Way back when we were first developing IntelliGantt we had to decide which SharePoint web part IntelliGantt would work with. Because it focuses on project management the obvious web part was (and still is) the Task List.

However, I still remember that day when someone from a theater group in Florida called and gave me an eye-opening demonstration of how they were using the Issues List to manage their day-to-day tasks. True, it may not have a Gantt (or does it? :), and it's not really for project management and heck, there's no difference between an issue and a task, right?

Right, there's not much difference between an issue and a task. So the question basically turned from us asking users 'how about using a task list' to users asking us 'how about using an issue list'? For instance, there's a great versioning feature with an Issue List that let's anyone see not just that an issue is resolved, but an accompanying history showing HOW it was resolved.

This is useful.

So we ehanced IntelliGantt to recognize the SharePoint Issue List and voila, here it is in action:




Perhaps you're thinking 'great, but I really like the Gantt Chart view that comes with the Task List'. Ah, we didn't forget about you. When you use IntelliGantt to work with an Issue List, IntelliGantt incorporates the same fields the Gantt Chart view native to WSS 3.0 and MOSS uses. For example, in the above demo you'll notice that IntelliGantt added a few fields to the Issue List-- most importantly a Start Date and % Complete-- to go along with the Due Date that was already there.

It turns out these are exactly the fields a Gantt View requires in order to display. So, after connecting with an Issue List, IntelliGantt prepares it for a Gantt View automatically. The end result, based on the demo above, looks like this:



I just have to take a moment to say 'That's pretty cool!'

You can download the new IntelliGantt Add In for Microsoft Project and try it out yourself.

What XML Parser Does Internet Explorer Use?

We came across an odd thing today. I'm not going to say its a bug because I don't know all the ins and outs. In the grand scheme of things I would rate it between the final coat of paint my railings are crying out for and the notion that I should cancel my newspaper since I read everything online these days.

HOWEVER

We had a bug report where IntelliGantt wasn't handling embedded objects within Microsoft Project fields correctly. The customer was kind enough to share their MPP file with us and we were able to work through the issue he was facing. (As an aside, providing the MPP file was a huge help for us. Thank you!)

We did eventually find we had a problem with a particular embedded OLE object within the Microsoft Project Task Notes field. But we were flummoxed after the fix because the project still bombed during the Sharing operation to SharePoint.

More debugging and additional enhancing of the log output led us to Task 98. Task 98 is certainly not as interesting as Hanger 18, but it did contain an alien of sorts-- an alien character code I hadn't seen since...

There in the rubble of text was a \v character, like that V miniseries back in the 80s.

Now the reason it took us so long to find this is we typically test our SharePoint XML packages with Internet Explorer. During our test, IE handled the XML just fine. However, when we created an XML document at runtime (for example. System.Xml.XmlDocument.LoadXml(string), it would throw an exception that it couldn't handle a \v.

Even though we are using .NET 3.5 SP1 (the very very latest) it looks the the System.XML parser is more or less unchanged from .NET 2.0. IE7, on the other hand, most likely is not using the .NET Xml parser and has something a bit newer.

It gets me wondering... Microsoft at this point really has two code bases: one for .NET and one for classic Win32. It's almost like two software development companies. I wonder how long this state of affairs can/will continue?

90,000 employees tells me as long as they want :)

Why I Love Customers

As much as you try, you can't think of everything.

But a customer base? They're much smarter than me and certainly able to point out what needs to be done.

Case in point: We just received feedback from two customers that were as powerful as they were blindingly obvious:

1) How about putting an Ordinal in to the SharePoint task lists so that I can quickly match the SharePoint task list ID with the MS Project task ID? This is great because it has the added benefit of sorting the SharePoint list so it matches the MS Project task order. Duh!

2) Synchronizing tasks is great, but why are you putting constraints on the tasks in MS Project. If a task has been completed early, the slack should be taken up. Obviously!

Our crack engineers were able to get these requests in to the BETA refresh we posted tonight along with feedback from other users.

Our request to you is keep that feedback coming!

Connecting Project, SharePoint and Outlook

A couple people asked about sending Microsoft Project tasks through SharePoint all the way to Microsoft Outlook. Because the Office suite is more or less ubiquitous in corporations, many people spend most of their day within their communication hub -- MS Outlook.

So is it easier to update a task via a web broswer pointing to a SharePoint task list? Or is it easier to update a task using Outlook? While we could commission a study on the subject and possiblity come up with a definitive answer, we think the better approach is to say 'yes, we do both'.

Here's a screencast showing:

1) Starting a new project, adding resources and (very important) giving those resources within MS Project an email address so that IntelliGantt can automatically match them with SharePoint members in the site collection.
2) Sending the project to a SharePoint task list
3) Using Outlook to work with the same SharePoint task list
4) Adding a filter to Outlook so that I only see my tasks (very important for projects that have hundreds of tasks)
5) Updating a task within Outlook
6) Getting that update all the way back to MS Project

It sounds (and reads) like a lot, but its only 26 frames in the screencast, and most of these slides handle creating a filter withing Outlook.

Whether your team members would like to work with their browsers in SharePoint, or work online/offline on their client with MS Outlook, IntelliGantt helps you tie MS Project, SharePoint and Outlook together in to a single project information mesh.

Here's the screencast:

Project Dashboards and SharePoint

If you're running more than one project at a time, you probably have more than one audience. IntelliGantt has already provided the best way for a project manager to communicate with the team, now its providing a great way to communicate with project stakeholders as well.

IntelliGantt now communicates with project dashboards from Microsoft (the Project List from the 'fabulous forty' SharePoint templates) and Bamboo Solutions (their newly released Project Portfolio Dashboard).

Here is a screencast of IntelliGantt and Bamboo in action.



What this demonstrates is the ability to use SharePoint both as a project execution tool and as a reporting tool. The real power with the reporting solution is that you don't need to be a member of the project to see the project summary.

As an example, say a company has 5 project managers each running 5 projects. With the IntelliGantt solution, each project manager can run their project with their teams AND report their progress to one central SharePoint site. When they report their progress, IntelliGantt will create a new entry in the dashboard if one doesn't exists, or update the entry that does exist. The overall goal is that once a week, those 5 project managers can keep project stake holders informed with 5 simple clicks.

We think this is a powerful solution and are happy to be working with Bamboo Solutions to bring it to you. And we expect the solution to only get better as Bamboo improves the web experience and TeamDirection improves the desktop.

IntelliGantt BETA Update

Thanks to everyone for their feedback on the inital BETA. We've tackled a lot of issues and put in our final feature-- reporting!

No screencast yet because its getting late (or early, depending on your point of view). Suffice to say if you install this release (4.0.0.101) you will see a new menu item called... wait for it... 'Report'.

IntelliGantt will initially recognize two SharePoint reporting web parts. The first one will be from Microsoft (part of that 'fabulous forty' template pack) and the second will be from Bamboo Solutions (their new Project Dashboard).

The idea is, as a project manager, you run a project with two constituents: 1) your team and 2) your management. IntelliGantt has always been great for the team, but now you have an additional 'share and update' capability-- you can describe where to create and update project reports.

Whether you synchronize your tasks or synchronize your reports, it can be done independently. The scenario is you may work with your team all week, synchronize every hour of every day, but at the end of the week you send the report data to a SharePoint web part so others can see the current state of things without getting bogged down in the details.

Speaking of details, check our latest release page for more information on the current BETA.

Screencast coming soon!

My One Comment on the Banking Fiasco

Apparently we like to privatize profits but socialize losses. Or maybe the management of these failed financial institutions I now own a part of returned their ill-gotten gains without notifying me yet.

On the other hand, maybe I can stay at their house during the holidays.

Nothing like a new BETA release

We've been burning the midnight oil to bring the major new version of the IntelliGantt Suite to market. First up is our IntelliGantt Add In for Microsoft Project 2007. The market has shown a tremendous response to product and as a result we had an enourmous number of suggesstions to sift through. I'm pleased to say we just about got all your requests!

The BETA for version 4 of the IntelliGantt Add In for Microsoft Project is now available (we'll be updating the TeamDirection site over the weekend, you just get to see it first). Among the improvements:

1) The basic Task List, the more advanced Project Task List and the Issue List can all be used. You can even supply a SharePoint template ID and use a web part list of your creation.

2) An easy, convenient way to reassign and/or remap Microsoft Project resources to SharePoint members.

3) An IntelliGantt resource pool to help you keep track of those SharePoint members for inviting them to projects.

4) A Dashboard that rolls all your shared tasks in to one view. You can filter this dashboard view by task properties (Late Tasks, Unread Data, etc) combined with resources (who is assigned to what).

5) Enahnced Workspace Settings (was Collaboration Settings) that describe what type of tasks you want to share in addition to what fields.

6) Significantly improve Estimates and Actuals support. You can report estimates to a specific baseline to aid in project tracking. You can also report actuals such that only tasks with values will be updated.

7) Enhanced synchronization reporting-- see exactly what is being changed when you update.

8) Awesome customization. Change any menu and most any label on every IntelliGantt UI form. This can be used for Localization as well. You can even share your customizations with others.

And many, many more. One in particular we will announce just before shipping :)

If you're curious what the new version looks like check out this screencast.




If you're really curious to see it in action, you can install it. This is a ClickOnce deployment which means you receive updates automatically. One thing to note, you must be using Microsoft Project 2007 at a minimum. We are taking advantage of new APIs in the Microsoft Project 2007 package that solve issues like storing the MPP file in SharePoint, for example.

The baseline requirements are:

Microsoft Project 2007 Standard or Professional
.NET 3.5 SP1 (included in install)
.NET VSTO 3.0 SP1 (included in install)
Version 9 of the C Runtimes (include in install)

If you decide to install the beta, please make use of our feedback menu items under 'Help' and let us know what you think!