Search Results

You can't. The 3d bars went away with the introduction of MSP 2013; it's not an option. If 3d bars are really important to you, then you could "downgrade" back to MSP 2010, or try to make pretty cha …

Beyond the excellent article on the subject by Daryl Deffler over at MPUG.com (which it appears you've read), there's not a good answer. The leveling calculations (and the rules themselves) in MSP ar …

You need more resources. Restating your problem, you have two laborers to perform 650 person-days of effort. At perfect productivity, this effort will take 325 days of duration, which, using the sta …

Start with a well developed, logic driven schedule network. Assign the manager as a resource to the required tasks. Assign the "Review" tasks a higher priority than other competing tasks. In leveling …

An elapsed month (emon) is always 30 elapsed days long (i.e. 30x24 = 720 ehours). Since 12 emons = 360 days, not 365, your schedule will fall 5 days behind each year. There is no unit of duration in …

Be sure to clear all leveling before implementing the Update Project dialog. Tasks whose start dates are already beyond your "reschedule uncompleted work to start after:" date - including those dela …

These are the same behaviors as in MSP 2010. Assuming you've created Fixed-Units or Fixed-Work tasks, then the durations of these tasks are 4 hours, 8 hours, and 4 hours - corresponding to the effec …

As noted in the comments, neither SF links nor ALAP constraints generally satisfy the need for scheduling just-in-time work. This figure shows a new readiness milestone linking to a new lead-time act …

The Dates in print settings only affect the timescale. Use the built-in "Date Range" filter (in the Data group of the View ribbon) to show only tasks that start or finish within a certain range. (It …

The default progress bar in the Gantt chart depicts (duration) % Complete, which is Actual Duration / Duration * 100. Percent Work Complete, on the other hand, is Actual Work / Work * 100 (this is di …

The simplest and most repeatable way to do this is with a macro/vba procedure. Here's some code that John - Project created and shared on msdn some years ago (VBA Macro Help - Cost Rate Tables). Opti …

The “Actual Duration” of an in-progress summary task (including a project summary task) in MSP is NOT the same as – nor even closely related to – the elapsed work days from the start of the summary to …

It is normally considered best practice to include explicitly-defined contract dates in the project schedule network, with due impact on schedule slack and critical path calculations. If you want to …