NetworkNewb wrote: » Did anyone else read that title as "pimp" at first? !
datacomboss wrote: » The certification has plenty of value. In fact, it's the most valuable cert I have.
DatabaseHead wrote: » Anything waterfall, it actually can hurt you..... I've seen it, it's happened to me.
DatabaseHead wrote: » OP Sorry for partially being responsible for hijacking you thread, this will be my last post on this thread. There are a couple of different ways of looking at this. I'll retract my statement and reinstate it by saying: The PMP not as valuable as it once was and in the future will become even less valuable. Couple of points to be made why this is happening. The PMP was originally designed ~1980. It's an old methodology that for the most part has stolen operational, financial, risk, quality and a few other management disciplines. Anyone who went to a decent school will have some exposure to these. In fact anyone who reads a decent book on these individual management disciplines can gain enough knowledge. This discipline is really all about physical projects. Building bridges over massive rivers, new casino, and large physical infrastructure projects. Once the concrete is poured for these buildings its realllllly expensive to redo that work. Same with electrical contractors etc.... These need massive planning cycles, you can't half ass a bridge and expect thousands of people to drive over it everyday, the business is assuming way to much risk. For these types of projects it's great. I would even bucket data center build outs, with generators and all supporting infrastructure falling into the category. So it has value but....... Most IT / Business projects don't align or require that type of project management style. In fact most of you aren't project managers, you are project coordinators or leads with some responsibilities. Even if your title says PM. The business / IT / BI pretty much all verticals are using agile methodologies to manage their projects. Usually have a charter or scope document with some light planning and heavy execution cycles with a major focus on iterative mindset and encouraging scope change to better suit the business. This methodology has flaws but is far superior to Waterfall. That's why you see agile tools being used over the traditional tools. I can't tell you the last I saw a GANTT chart, they don't exist and if they do they are generally high level fluff on a PowerPoint with some artificial time lines. Companies have elected to go with Kanban boards, backlogs with grooming sessions, daily stand ups, sometimes just weekly and a whole host of other techniques. This is reality you can face or not, I don't care to be honest. Over the course of 3 years I have interviewed and had casual conversations with recruiters in regards to positions that require a certain element of project coordination. To be blunt, they want agile, period. What they don't care about MS Project / Gantt charts Bloated project documentation (Risk registers, supplier scorecards etc.......) Anything waterfall, it actually can hurt you..... I've seen it, it's happened to me. What they want Are you comfortable working in team rooms? Are you comfortable dealing with 15 minute SCRUMS in the morning? Can provide reporting to senior leadership out of JIRA, using Epics, stories, sub stories while managing your project deliverables? Do you have understanding of backlogs and why they exist? Kanban boards Moving scope I honestly don't care if you think my advice is crap or not. Bottom line is your post was relevant in 2008, not 2018.....