Microsoft Project Team Blog

Tips and Tricks: Modify the baseline in Project 2007

2009-12-18T22:22:52Z

Change is inevitable. Adding new tasks to a project that has already been approved and baselined can be troublesome—to you and stakeholders. But don’t fret. You don’t need to set a new baseline to take into account the new tasks. Just update the old baseline. To modify the baseline that has already been set, do the following:

Select the new tasks that have been added recently to the project. This is important.
On the Tools menu, point to Tracking, and click Set Baseline.
In the Set baseline list, select the previously set baseline. It will have a date associated with it.
Here’s the tricky part. Make sure you select the Selected Tasks option. Otherwise, you’ll reset the baseline for the entire project.
Click OK.

One more thing: Make sure you communicate these changes to stakeholders, if necessary. Some people just don’t like surprises.

Project 2010: Introducing Exchange Integration

2009-12-11T15:51:00Z

Exchange Integration provides the ability for team members on a project to view, update, delete and report status on their published tasks in Outlook, Outlook Web Access (OWA) or any other application that is capable of syncing tasks from Exchange Server.

This functionality replaces the Project 2007 Outlook add-in that allowed team member to report status on their tasks and report time against their timesheet. Even though the Exchange Integration feature does not provide the ability to report time against a timesheet, it provides a number of benefits over the Outlook add-in. A few examples of functionality that it provides over Outlook are:

Ability to report status from OWA
No add-on to deploy to the team member’s computer
Seamless integration with Outlook Tasks

One of the driving goals of this feature is to keep the task experience in Outlook the same for the team members. For us, this meant, that if a team member is familiar with working with Outlook tasks, they should easily transition to using tasks that are synchronized between Exchange and Project Server. Team members will find the same user interface used for Project tasks as they find with regular Outlook tasks, except for a custom Project Task ribbon which changes a few advanced options. Team members use the same interface to mark tasks complete, update their status and categorize their tasks as they would regular Outlook tasks. Also, all their tasks show up in their to-do lists, however, we sync the tasks into folders that are named by the project name the task belongs to, allowing the team member to quickly find tasks for a given project.

Lets walk through a simple example on how this feature works. Jack is a project manager and has a very simple plan, which involves myself to complete some tasks on his project plan. Just like Jack has previously assigned me work, he creates his plan and assigns me to the tasks that I need to complete, In this example, he has assigned me “Task A” and “Task B”. When Jack publishes the plan, the tasks show up in My Work, just like they do if we Exchange Integration is not enabled on the server. I can then go ahead and update my status on the My Work page in PWA, but in addition to the tasks being published to the My Work page, they also show up in Outlook and OWA because Exchange Integration is enabled for me:

From within Outlook or OWA, I am able to see the tasks assigned to me. They show up in my to-do list and in the calendar view:

In addition to showing up in these two places, I can also see a list of all the tasks I am assigned to for a given project:

I can easily go update properties on the task such as percent complete, actual/remaining work, and task name. All the tasks will sync to the team member’s mailbox, independent of the tracking mode. There is no way to enter time phased data in the Outlook task form, so users cannot enter the time phased data like they can in PWA, however the team member can still update the percent complete and actual/remaining work for the task and Project Server will make a best effort on updating the status on the task. When I make this changes, the tasks are automatically synchronized back to Project Server once the client connects back to Exchange Server. Updated tasks are automatically submitted for approval:

Next time Jack opens the project plan, he will see that I have made updates to the tasks assigned to me. At this point he can accept or reject update just like before. If the task update is accepted, the change is applied to the plan. If Jack chooses to reject the update, he can add a comment and it will show up in the notes field of the task for the team member to review.

In addition to updating properties on a task, the team member can create tasks for a project by creating a new task in the appropriate project folder or delete tasks. Both of these actions go through the approval process, just like the it would if the tasks were created or deleted from PWA.

In this release we have also added a new feature called Single Entry Mode (SEM). Patrick Conlan briefly described it in the blog post entitled “Time Tracking in Project Server 2010”. When SEM is enabled the task update data automatically flows into the Timesheet and onto the project plan wherever it is edited, until such time as the timesheet is sent for final timesheet manager approval. It is important to know that Exchange Integration continues to work when SEM is enabled.

This feature is available in the beta release of Project Server 2010 and the setup documentation for the Project Server 2010 describes how to set it up. Give it a try and let us know how it works for you!

Chris Boyd

Tips and Tricks: Get the scoop quickly

2009-12-09T20:23:25Z

The biggest question in project management is: How is my project going? The quickest way to learn this is to take a look at the Project Statistics dialog box in Project 2007. To get to this, on the Project Menu, click Project Information, and then click the Statistics button.

At a glance, you can find the following:

At the top, you can review start and finish dates for the currently estimated, baseline, and actual dates, as well as the variances.
At the bottom, you can review the current, baseline, actual, and remaining values for duration, work, and cost.

Now, wouldn’t it nice if doing your taxes and balancing your checkbook were this easy?

Project 2010: Introducing AutoFilter

2009-12-04T22:56:04Z

In Project 2010, we made a big update to AutoFilter in the client. Now from the column header you can sort, filter on, and group by the field. Essentially there are four zones:

Sorting: Depending on the type of field, you can sort alphabetically, numerically, or chronologically.

Group By: You can select to group explicitly on the field, or group on an interval specific to the field type. For example, for date fields this looks like:
If you aren’t sure why to use group by, check out this post.

Filters: While you can easily use the checkboxes to select which values to display, the filter flyout allows you to do this more quickly based on the selected criteria.

Date Fields: Duration Fields:

Checkboxes: These allow you to select which values to display by simply checking/un-checking the values. For example, if I uncheck October then none of the task that start in October will be displayed.

AutoFilter is on by default in Project 2010. If you aren’t seeing it, you can turn it on by going to View tab – Filter dropdown – and selecting Display AutoFilter.

You can tell an AutoFilter is applied since the column header displays the funnel shape . Additionally, the Status Bar displays “AutoFilter Applied” and if you hover over it, you can see which fields are affected:

Project 2010 Webcast: Project 2010 Overview

2009-12-02T20:15:53Z

Would you like to see the forthcoming Microsoft Project 2010 release
demonstrated live?

Keshav Puttaswamy, Group Program Manager, Microsoft, will discuss and demonstrate core capabilities and features of the upcoming release – Microsoft Project 2010. The webcast will cover the key bets of unifying project & portfolio management, improving execution with effective collaboration, enhancing user experience & appeal, and simplifying deployment & interoperability.

Join us to learn how you can utilize the powerful capabilities included in Project 2010. Obtain unique insights into how the next release will continue to support your business during the first in a 3 part series, delivered by Microsoft engineers and product managers.

Microsoft Project 2010 Webcast: Project 2010 Overview

Presenter: Keshav Puttaswamy, Group Program Manager, Microsoft

Date: Wednesday, December 16, 2009

Times: 7:00am – 8:00am PST and 6:00pm – 7:00pm PST

Register now for this session or one of these upcoming complimentary sessions:

Video: Project 2010 – Editing Very Large Projects

2009-12-01T20:10:11Z

As promised in our post where we introduced Web Based Editing, we now have a video to demonstrate the speed with which you can edit a large project in Project Web Access. This project has 6,300 tasks and, as you can see from the video, in just a few short seconds you can load the project and make edits to the plan. Just one of the many new features to look forward to in Project 2010.

Early Project 2010 Feedback and Issues

2009-11-25T17:40:16Z

It’s been great to see how many people have downloaded the Project 2010 Beta so far! Keep the feedback coming in the forums and through Send a Smile. I wanted to post to clarify a few of the most common issues people have been hitting so far.

Connecting Project 2010 client to Project 2007 Server – This is not supported. Project 2010 client can only connect to Project 2010 Server. You can connect the Project 2007 client to a Project 2010 server if the server is running in Compatibility Mode.

Unable to connect Project 2007 client to a 2007 server after installing Project 2010 client – This is an issue in the Beta. To fix this issue, go to the Control Panel – Add/Remove Programs and repair your installation of Project 2007.

Where is the Pert Add-in – This was removed from Project. Brian Kennemer has blogged about a macro he wrote to replace this functionality. Check that post out here.

Where is Copy Picture – It is on the Home tab – Copy dropdown.

Remember, if you are using Send a Smile, please include your email address and put the text “Project” in your comments. This way we can find your feedback and follow up.

Time Tracking in Project Server 2010

2009-11-23T16:45:59Z

As you might imagine we are all very excited to be able to talk about the new features coming in Project Server 2010. One of the areas where we’ve made huge investments is in Time Tracking where we’ve had a huge amount of feedback from our customers. The feedback has been immensely valuable in helping us deliver a richer experience and I hope that you’ll be as excited by the upcoming features as we are.

Given the size of the investment we’ve made it’s is going to be hard to squeeze a full description into a single blog entry so I’m going to point out the highlights and then we’ll follow up with some more detailed posts over the next few weeks, specifically:

1. Task Statusing and the new Grid (Pat Malatack will do the honors)

2. Timesheets and Single Entry Mode (my next article)

3. Approval Center for integrated approvals (Pat Malatack and Nicolae Rusan)

4. Exchange and Outlook Integration (Chris Boyd)

5. Why Track Time? (my final (planned) article in this series)

We’ll also be posting on the new Administration Blog, with a deep dive into the rich Time Tracking configuration options (my 4th article); and on the Programmability Blog, with two posts: one on extending the UI (Pat’s 3rd) and the other on reading/writing data in single entry mode (my 5th).

As we post each article I’ll update this entry with links so you can quickly navigate around all of the posts

Finally, as ever, if you have time tracking questions feel free to post them in response to our blog entries and we’ll do our best to get you an answer.

Overview

I’m going to talk briefly about each of the areas above to give you a taste of what is coming over the next few weeks. Before I start with the new grid I just want to point out that we’ve deliberately minimized the changes we’ve made to our back end api (the Timesheet and Statusing Web Services), so those of you with customizations can relax!

The screenshots below are from a post Beta2 build, so you may notice one or two differences from the Beta – let us know if you can spot them!

Task Statusing and the Grid

One of the areas of feedback was that the move away from Project Server 2003’s ActiveX grid was a good thing (no install on to Team Member’s desktops) but that the replacement grid had some missing functionality. The good news is that we have a spiffy new grid that makes the Team Member experience richer than ever, here is a screen shot:

Figure 1 - Tasks Page

Pat will talk more about this in the next post but first notice the client-like ribbon, we’ve done a lot of work to make the experience more document-centric than in the past, it tested well in the usability labs and I hope you’ll find it easy as well.

Now notice the clean left navigation menu, again we’ve reworked the grouping a little (and this isn’t the final version, we expect the “Business Intelligence” option to move soon) to balance

In the grid itself we’ve brought back the ‘splitter bar’ (so the right “pivot” grid can be pulled over the left grid’s fields) which will really help folks with lots of columns to add to the grid but who have smaller screen resolutions make better use of their real estate.

The left grid is also a lot smarter, with the ability to reorder columns, hide/reveal columns and do custom sorts – and the bonus is that we remember these settings across sessions for each view that you select! There are many other improvements here that I’ll leave to Pat’s post where he’ll really exercise the grid’s capabilities for you.

Timesheets and Single Entry Mode

The first thing you’ll notice is that we’ve moved the old “Timesheet Center” down to “Manage Timesheets”, so when you navigate to the Timesheet page we’ll create/load the timesheet for the period for the current date, allowing you to get in and out with a minimum of clicks.

You’ll be pleased to discover that the Timesheet page has adopted the same grid technology as the Tasks page, so you get all the benefits of efficient use of screen real estate and more. The two grids behave a little differently due to the nature of the data:

- Timesheet shows only late tasks and tasks with work planned in the period;

- Tasks shows all of a Team Member’s tasks plus those tasks where they are the assignment owner.

They also behave differently due to the differences in workflow between task update approval and timesheet approval. Despite these difference we hope that they will behave closely enough for the Team Member to move easily between them.

Here is a screenshot of the Timesheet:

Figure 2 - Timesheet Page

Notice the Status Bar (the blue bar below the Ribbon) – this is where we tell the team Member what to do next as well as displaying some global state such as the total hours and the period range.

The big functional change is the introduction of “Single Entry Mode” (SEM) – it can be set on or off by the Administrator and governs the integration between timesheet and project task assignment data. When SEM is on the task update data automatically flows into the Timesheet and onto the Project wherever it is edited, until such time as the timesheet is sent for final timesheet manager approval.

If SEM is on, then changes to task assignments are sent for approval to the Task Status Manager, and you can optionally hold back timesheet approval until all task updates are approved.

There is a lot more to talk about that I’ll cover in the Timesheet post.

Approval Center

We reviewed how people did approvals in Project Server 2003 and 2007 and decided that we would make the process faster if we presented all the approvals in a single dialog, this is shown below:

Figure 3 - Approval Center

Note that there is a Timesheet approval mixed in with task updates. Again we’re using the new grid technology for a familiar look and feel as well as the splitter bar to make the page more scalable. We didn’t get round to integrating Workflow Approvals in this release, and this will be a separate menu option for those using Demand Management workflows.

Pat will take more time to show you around the grid and to show you the history pages in a future post.

Exchange and Outlook Integration

In previous releases we shipped an Outlook add-in that collected timesheet data – this was nice but had limitations including the need to install client-side code as well as functional limitations that meant that Team Members had to head to PWA to do many things.

We’ve now focused on connecting through to Microsoft Exchange™ and for our first revision we’ve targeted basic task assignment updates – using % complete or total work/remaining work – so it’s ideal for customers with basic progress tracking requirements.

The Team Member uses an Exchange client (Outlook or Outlook Web Access) and updates their tasks – any work entered is auto-submitted to the Task Status Manager, making this the simplest of the Time Tracking options.

Using Import or Single Entry Mode the data will arrive in the timesheet where it can be tidied up and then sent for approval.

Chris will talk about this more in an upcoming post.

Why Track Time?

This will be our final post in in the initial series where I’ll take some time to guide you through the reasons for choosing each time tracking method, with the aim of helping you be successful from the get go.

I know that the whole team is excited about sharing the new functionality in public for the first time and we are all looking forward to your feedback on what we did well (and what we may have missed)

Patrick Conlan
Project Development Team, Redmond.

Calling all Admins – There’s a New Blog for You

2009-11-19T23:06:00Z

Announcing the Admin Blog! Coinciding with the release of Public Beta, we are aggregating all Project Administrator / Implementer content into a TechNet blog located at http://blogs.technet.com/projectadministration

The content of this blog will cover setup, upgrade, performance, backup/restore and planning topics for Project Server 2010/Project Client 2010. We will also have Project Server 2007/Project Client 2007 and Project Portfolio Server 2007 related topics as needed. We will also use this blog to announce patches, administration best practices and temporary issues with installs/upgrades.

Now Available – Project 2010 Beta!!!

2009-11-18T18:09:00Z

You’ve heard the buzz, seen the posts, now check it out for yourself – the Project 2010 Beta is now available!!!

To download: Click here for Project. You can download the other Office applications from here

To send feedback: Use Send-a-Smile. When you install Project 2010, you’ll notice that a smiley face and frown now appear in your taskbar. You can use these to send feedback on your experience with Project. To help us out make sure to use the word “Project” in the comments section and include your email address so we can follow up with you if we have any questions.

To get help: Visit the Project 2010 forums

Tips and Tricks: Contour your work

2009-11-14T00:17:33Z

A typical work week is rarely typical. Yet, you can plan for this with a Project 2007 feature called “work contours.” If you discover that there is a consistent work pattern in your organization where people are assigned to work more hours at the beginning of a task than at the end, you can have Project account for this using assignment contours. Or, perhaps a task requires more work in the middle of it than at the beginning to account for ramp-up time.

No problem. After assigning a person to a task, switch to the Task Usage view from the Tools menu. The tricky part is double-clicking the person’s name assigned to a task and not the task itself. This brings up the Assignment Information dialog box (which is what you want since you’ll be adjusting an assignment and not the task itself).

In the Work Contour list, select the type of work assignment pattern that makes sense for the work that will be performed on the task. Now, in the list of patterns, you may not know the difference between a “Turtle” and “Bell” contour, so it’s best just to apply different contours and see how the hours automatically “shape” themselves in the timesheet portion of the Task Usage view. The view should now look like this:

In the image above, two different contours are used: a “Bell” contour and a “Front-loaded” contour, as you can tell by the icon on the left.

On the right side of the view, Tom has his work hours shaped, or “contoured,” to reflect a front-loaded work pattern.

Project 2010: Introducing Demand Management

2009-11-13T21:50:28Z

Demand Management is about capturing all work proposals in one single place, taking these proposals through a multi-stage governance process, making decisions on which proposals to approve and tracking progress on their execution until the work is completed. A key component within Demand Management is the Workflow governance model we have now implemented within Microsoft Project Server 2010.

The "Proposals" feature in Microsoft Office Project Server 2007 helps capture demand in one place, but is not flexible enough and does not have a full-fledged governance workflow behind it. The "Builder" module in Project Portfolio Server 2007 is a flexible demand management paradigm, but does not have a familiar Project Server/Office SharePoint Server look and feel and also has some usability, scalability problems. The Demand management functionality in Microsoft Project Server 2010 is designed to be both flexible and usable.

In project portfolio management (PPM), a project lifecycle is a long-running process that spans various governance phases. Typical demand management phases are create, select, plan, and manage (customers can create their own).

The "Plan" phase is accomplished by the more familiar project management processes using Project Professional and Project Web Access. Workflow models the governance processes and provides a structured way for projects to proceed through the phases. Workflows, along with other key concepts, are captured and integrated within the demand management feature set, providing a rich and dynamic platform on which customers and partners can build custom solutions.

The figure below shows the four typical phases of demand management and how they fit together. Within each phase are stages such as propose idea and initial review. Each stage can have an associated project detail page (PDP) in Project Web Access (PWA). The entire collection of stages represents a single workflow that can be linked to an enterprise project template (EPT). More details about these concepts given below.

Governance Workflow

A governance workflow is all about creating a rich life cycle for any proposal/demand that comes into the system. It includes defining the various stages through which the project goes in its lifecycle (for example, Proposal Creation, Proposal Initial Approval, etc), determining what information is required or locked at what stage (for example, budget cost should be locked down after the project is approved), including any manual approval/notifications steps as necessary and adding any business logic to update other Line Of Business Systems (for example, update the SAP system when the proposal budget gets approved).

The Project Server workflow platform is built on the Windows SharePoint Services 2010 workflow platform, which in turn is based on the Windows Workflow Foundation. Workflow is a key component of demand management.

A Project Server workflow runs on a Project Web Access site and helps to manage a sequence of activities or alternate sets of activities related to project management such as Check Project Custom Field Value and Publish Project.

Project Server 2010 workflows use the Site workflow paradigm, which removes the restriction that a Windows SharePoint Services 2010 workflow can be started only on a list item. Project Server workflows are deployed to Project Web Access, and workflow instances can be run only as a project entity.

The figure below shows the high-level processes for workflow creation, administration, and use.

Note: Project Server workflows must be created in Microsoft Visual Studio 2010. Project Server workflows cannot be created from Microsoft SharePoint Designer 2010.

The administration of Project Server workflows is identical to managing any other Windows SharePoint Services 2010 workflow, thereby providing more consistency between Project Server and Windows SharePoint Services 2010 and reducing redundant work. Workflow instances are created when a project is created and are deleted when the project is deleted/completed/rejected.

Unlike in Windows SharePoint Services 2010, a user does not start a workflow instance from the administration page that lists all the Project Server workflows.

Enterprise Project Type

An enterprise project type (EPT) represents a wrapper that encapsulates phases, stages, a single workflow, and PDPs. Each EPT represents a single project type. Normally, project types are aligned with individual departments, for example, marketing projects, IT projects, HR projects, and so forth. Using project types helps to categorize projects within the same organization that have a similar project life cycle. For a user, the EPTs appear in a drop-down list of project types when the user clicks New Project in Project Web Access.

Phases

Phases represent a collection of stages grouped together to identify a common set of activities in the project life cycle. Examples of phases are project creation, project selection, and project management. Phases do not have any direct technical impact on the behavior of an EPT. That is, changing the order of phases does not affect how the system reacts. The primary purpose of demand management phases is to provide a smoother user experience where users have the option of organizing stages into logical groups.

Stages

A stage represents one step within a project lifecycle. A stage is composed of one or more project detail pages (PDPs) linked by common logic or theme. Stages at a user level appear as steps within a project. At each step, data must be entered, modified, reviewed, or processed.

At a technical level, each stage represents a step where data is manipulated before the workflow can move to the next step. For a single-stage workflow, very little programming is involved. The user enters all of the data in one PDP, and can then work on the project as she normally would. For a multi-stage workflow, each stage is separated by an activity (SetProjectStage) within a Visual Studio workflow diagram. The actual SetProjectStage activity acts as a marker between stages and sets default properties of the next stage. The activities that follow SetProjectStage outline the actions that must take place within the next stage.

Note The actual stage itself is not created within Visual Studio. The stage must first be created in Project Web Access. After the stage is created, you can link to that stage within Visual Studio.

Project Detail Pages in Stages

A PDP represents a single Web Part Page in Project Web Access. PDPs can be used to display or collect information from the user. You can create PDPs in much the same way you create any Web Part Page in a SharePoint site, where you can add Web Parts that provide the experience you want. You can add individual Web Parts from the standard Web Part galleries to create custom Web Parts.

Project Server Web Parts and custom Web Parts used in demand management all contain custom fields. Web Parts can make calls to the PSI, query the reporting database, or integrate with external systems.

The figure below shows the general hierarchy of the parts of demand management in Project Server 2010.

Workflows are associated with the stages. From a programming standpoint, PDPs are not actually referenced within the workflow. The PDPs simply act as containers to hold or display data. The workflow can however, references custom fields in the Web Parts.

Project 2010: Introducing Portfolio Analysis

2009-11-11T01:02:40Z

In Project Server 2010, a rich set of new Portfolio Strategy features are now available in the core Project Server product serving to more closely unify project and portfolio management. Those familiar with Portfolio Server 2007 will recognize many of these features, but will appreciate the enhancements made possible by rebuilding them on the Project Server platform. Highlights include:

· UI is now SharePoint-based, making these features easier to use and provides visual consistency with the rest of the app

· A gateway linking the Portfolio Server product is no longer required, everything resides with one product

· Full API support now available for these features via the Project Server Interface (PSI), and some integration with the Reporting Database (RDB).

This seamless unification of two products into one consolidated offering makes end-to-end project and portfolio management easier than ever. In addition to the core platform integration highlights, we’ve adding a brand new Resource Analysis feature that enables portfolio-level project scheduling and analysis based on organizational resource availability.

For those of you unfamiliar with the Portfolio Strategy feature set, it essentially allows organizations to methodically select projects that will yield the most value for their dollar. By adding intelligent structure to how project investment decisions are reached, executives can minimize the irrationality and fog that comes from making “gut feel” disposition decisions based on limited data and analysis, or based on unqualified or unclear business goals. At a high-level, the feature set works as follows:

· Organizations define and prioritize their strategic objectives, or business drivers.

Drivers can be prioritized using the pair-wise comparison method to reinforce objectivity.

· Costs and resource requirements are assigned to each project proposal, and a proposal’s impact on each business driver is rated, generating relative project value/priority score across a portfolio.

The Resource Plan feature can be used to specify high-level project resource requirements to be fed into the new Resource Analysis feature.

Portfolio analysts can review the project-to-driver impact ratings assessed by the project owners and make adjustments if necessary.

· Portfolios are constrained by cost categories, time-phased resources requirements, and project schedule. The Portfolio Cost Constraint Analysis engine selects projects that yield the most value with the lowest cost, while the Resource Constraint Analysis feature chooses higher priority projects based on resource availability within a planning period’s timeline.

Given a limited budget, the Cost Analysis algorithm will select a portfolio that maximizes strategic value while minimizing cost.

The new Resource Analysis feature helps you identify gaps in demand vs. availability, favoring higher priority projects for selection.

· Portfolio analysts can override the software’s decisions, and pull a variety of constraint levers to maximize value based on a given organizational reality. Projects can be forced in, cost reduced, dates moved, resources hired, etc., all in an effort to achieve a plan that maximizes strategic value based on dollars/resources consumed.

The tool suggests project selection, but ultimately you are in control and can force in projects for specific user-defined purposes.

One of the way the Resource Analysis feature allows you to resolve resource availability gaps is by moving project dates.

· Final project investment decisions are reached and communicated to stakeholders via reports or through the web interface.

New “Committed” fields help communicate the results of selection decisions to stakeholders.

Again, all of this is done on the shared extensible Project Server/SharePoint platform in the 2010 version, and integrates seamlessly with the rest of the Project features, including the Demand Management feature set and project scheduling/execution.

From strategy, to selection, to project planning and execution, Project Server 2010 unifies the end-to-end Project and Portfolio Management experience.

Ask a Project PM: Timesheets and Task Status

2009-11-10T16:14:43Z

Thanks all for your insightful questions on timesheets and task status in Project Server 2007! Project PM Patrick Conlan has some answers for you in this video:

Ask a Project PM: Timesheets and Task Status

Many thanks to Patrick for a well-versed interview. Watch for another topic next week!

Microsoft Project 2010 Session at Tech Ed Europe 2009

2009-11-04T23:53:44Z

Please find below the list of Project 2010 sessions that will be delivered at Tech Ed Europe 2009 in Berlin in November. We will also have a Microsoft Project 2010 booth staffed by product experts in the Microsoft Product Pavilion so please drop by and ask plenty of questions!

Session	Description	Code	Speaker	Date/Location
Microsoft Project 2010 Overview	This session provides an overview of the key investment areas and capabilities of Project Server 2010 and Project Professional 2010, including demand management, portfolio analysis, time tracking, and reporting.	OFS214	Jan Kalis, Christophe Fiessinger	11/9/2009 13:30-14:45 New York 3 - Hall 7-1a
Microsoft Project Server 2010 for IT Professionals and Developers	This session provides details of what Project Server 2010 offers IT professionals and developers, including new features for easier deployment and management, and developer-related enhancements across Server and Client.	OFS206	Jan Kalis, Christophe Fiessinger	11/13/2009 10:45-12:00 London 3 - Hall 7-1b

Additionally, if you have not done so yet register for these: