Prev: Maintain formatting of sub project when inserted into master proje
Next: P6 Web vs. Project Server
From: Doug on 4 Feb 2010 08:43 Hello group, I've been using Primavera for a couple of years, I'm no expert, but have gotten used to the way P6 does things. Me and a couple guys in my group are being asked to do a few relatively small projects (not even worried about resources etc now, just schedule) Is there a website or document that might spell out the things one needs to know to move from Primavera to Project? I'm not talking about converting a file, just understanding what things I should expect to be done differently in Project than the way it was done in Primavera. It seems that Project leans heavily on the relationships and can't except that sometimes things don't start when they were supposed to. In the case of updating status date past when an activity was supposed to start, it appears Project thinks it's more likeley that we will travel back in time to start the activity on time than it is that we'll start the activiy on or after the status date.
From: Andrew Lavinsky on 4 Feb 2010 09:00 You're probably best served attending an MS Project training class. I work with a bunch of ex-Primavera schedulers, and I can tell you that it's entirely feasible to transition to Project. We ended up developing a couple of macros to emulate how they expected the tool to work coming from a Primavera background, but it wasn't a huge amount of effort. - Andrew Lavinsky Blog: http://blogs.catapultsystems.com/epm > Project leans heavily on the relationships and can't except >
From: Doug on 4 Feb 2010 16:58 Thanks Andrew Maybe there's hope for me.. But it's the little things that can drive you crazy. For example.. one of the things I actually like about Project is the way you can indent and outdent to group activities into groups, and how I can add blank rows to make the schedule more readable especially during the development stage. Just now I filtered a schedule to hid ethe completed activities by using the filter called "incomplete tasks". In addition to hiding the completed tasks, this filter also hides every blank row and makes my schedule very hard to read. Arg! Doug
From: Trevor Rabey on 4 Feb 2010 19:11 Doug, Drop the blank lines idea. It is appealing at first and all beginners try it, but old hands know that blank lines are more of a problem than a help. They actually make the plan harder to read instead of easier, and they make indenting/outdenting confusing because you don't know where the blank is indented to. I keep my data "tight". No white space. Mike says use gridlines. Go with that. -- Trevor Rabey 0407213955 61 8 92727485 PERFECT PROJECT PLANNING www.perfectproject.com.au "Doug" <Doug(a)discussions.microsoft.com> wrote in message news:C2FBA0A1-12E9-4FC3-8F6D-3475ACB042CB(a)microsoft.com... > Thanks Andrew > > Maybe there's hope for me.. > > But it's the little things that can drive you crazy. > > For example.. one of the things I actually like about Project is the way > you > can indent and outdent to group activities into groups, and how I can add > blank rows to make the schedule more readable especially during the > development stage. Just now I filtered a schedule to hid ethe completed > activities by using the filter called "incomplete tasks". In addition to > hiding the completed tasks, this filter also hides every blank row and > makes > my schedule very hard to read. > > Arg! > > Doug
From: Trevor Rabey on 4 Feb 2010 19:28 Doug, Re your last paragraph, it reads confused and wrong. This line of thinking, where you concoct a theory about what's happening, will get you confused worse. Avoid assumptions and hypotheticals. Always test. Get real clear about the tracking. It works, ie MSP works, and makes sense (unlike your explanation) but not if you don't know what you are doing. -- Trevor Rabey 0407213955 61 8 92727485 PERFECT PROJECT PLANNING www.perfectproject.com.au "Doug" <Doug(a)discussions.microsoft.com> wrote in message news:01B9FA92-9F82-4A53-A17D-A404CB2F69D0(a)microsoft.com... > Hello group, > > I've been using Primavera for a couple of years, I'm no expert, but have > gotten used to the way P6 does things. > > Me and a couple guys in my group are being asked to do a few relatively > small projects (not even worried about resources etc now, just schedule) > > Is there a website or document that might spell out the things one needs > to > know to move from Primavera to Project? I'm not talking about converting > a > file, just understanding what things I should expect to be done > differently > in Project than the way it was done in Primavera. > > It seems that Project leans heavily on the relationships and can't except > that sometimes things don't start when they were supposed to. In the case > of > updating status date past when an activity was supposed to start, it > appears > Project thinks it's more likeley that we will travel back in time to start > the activity on time than it is that we'll start the activiy on or after > the > status date.
|
Next
|
Last
Pages: 1 2 Prev: Maintain formatting of sub project when inserted into master proje Next: P6 Web vs. Project Server |