i want to hear your story.
i want to hear about how your schedule was a nightmare from the start – but you pulled through in the end; about how this one trick saved your butt in a crunch or even about how things went completely wrong and you would never do that again.
these are stories we all want to hear.
we want to hear your story about project controls, primavera p6, your team’s unique project and what you accomplished.
last year i played a part in organizing collaborate14, where i and others were inspired by presentations from primavera users; users who were willing to stand up and share their experiences with primavera – the good, the bad and the ugly.
some inspiring talks i attended at collaborate14:
ivan rincon’s excellent presentation on implementing an integrated primavera p6 eppm at bc ferries. ivan told bc ferries’ story from an organizational standpoint, discussing challenges with training, user adoption, having proper technical skills in-house as well as technology challenges.
it was not your typical “here’s how mapped this field to that field in p6” sort of talk. (here’s a link to ivan’s presentation and his whitepaper on the opsig website.)
ivan discussed how the organization had to adapt to enterprise project management, and how people reacted to these changes. the kind of invaluable “how we toughed it out” information i heard about you will not find in any oracle brochures or white papers.
trevor watt of epcm solutions sort of blew me away with “30% / 60% / 90% ifc engineering: what is the project progress?” (link to presentation).
he showed us how ifc engineering project schedules are usually built at a fairly high-level in p3 or p6. this high-level approach didn’t allow him to accurately progress his activities using rules of credit.
his solution?
ditch the high-level schedule and go for a detailed schedule that allowed him to increase his progress accuracy by a factor of 10.
and he used just about every primavera p6 feature to build and track his schedule – resource curves, leveling, financial periods, global changes…. he used them all.
why bother with the detail?
his words “the bottom line is what ever happens during the engineering phase, can affect construction two fold.” smart stuff. his audience was impressed and had a flurry of questions for him afterwards.
as an organizer for next year’s collaborate15 conference, i’m on a mission to find more inspiring and motivating user stories. technical presentations are great and really helpful. but a successful user conference relies on users to get involved.
i’m on a mission to find more inspiring and motivating user stories.
collaborate15 call for presentations – open until oct 31st
the call for papers for collaborate15 is open, but only until oct 31st. get going and submit an abstract….it only takes a few minutes.
the conference will be in las vegas in april 12-16, 2015 at mandelay bay, a great venue. if you do submit and are selected to speak, conference attendance fees are waived (for 1 speaker)….yes, you can attend for free!
if you aren’t able to speak or don’t feel the pull despite my nudging, then consider attending and block out april 12-16 in your calendar. i’ll see you there.
