Advice on reporting project experience

Submitted by txhobbes on Thu, 11/15/2012 - 18:06

 Much of my project experience is in overseeing releasing applications from start to finish (i.e., justifying a release, planning a release, ..., EOL'ing a release). Each release is a project, with resources, goals, etc, changing each time. But in another sense, it's an ongoing thing. 

When entering my project experience, is it advisable to combine these into one entry (with a note that I handle each release as a project - in which case I have a handful of entries), or to have an entry for every release I've shipped (in which case, I'd have around 20 projects to list)?

Thanks for your help. 

Forums: 
General Discussion
  • Log in to post comments
  • 533 reads

1stChoicePMtraining

Thu, 11/15/2012 - 22:45

Best to just group it all as a single project (or few projects). Listing 20+ projects with identical descriptions not only takes hours to enter but also adds no value to your application. Especially if you have the same supervisor who will sign off if you get audited. PMI are perfectly ok with grouping them together.

saket_pmp

Fri, 11/16/2012 - 05:21

You can combine multiple projects into 3-4 and show that to PMI. Different project can fit in a big project and this way you can cover all process groups in each project.
If you are caught in audit, getting the audit formalities for 3-4 project is much easier than 20+ projects.
Good Luck!


Saket, PMP