pmNERDS Community: Login

  • Innovation_e_Publication
  • Integrated_PM_Feedback_Blog
  • Job_Board
  • pmNERDS_Center_of_Excelence
  • Research_and_Development_Journal
  • Community_Blog
A+ A A-
  1. Robert Goodhand
  2. Portfolio Management
  3. Tuesday, 10 October 2017
  4.  Subscribe via email
What are some reasons why or why not it’s important to label a new work request a “project" or not?

Some of my clients have spent months arguing over this.

The “big" work efforts don’t seem to demand a judgment call. But the “small” ones usually do.

So is work effort size the determining factor here?

After acknowledging the standard PMBOK definition of project as a “...temporary endeavor undertaken to create a unique product, service, or result”, what are your recommendations to solve this mystery in your work worlds?
Rate this post:
Comment
IMO the small work request must have dependencies on other groups, and obviously a structured start/finish to require them to be classified as a project. Having worked on the operations teams, it was often the case that the small work requests would get started and not complete due to the dependence on other groups/resources and their priorities being set on prioritized projects.
  1. Kristie Parnell
  2. 2 months ago
There are no comments made yet.


There are no replies made for this post yet.
However, you are not allowed to reply to this post.