Aleshia WardExhibits Manager| American Society of Plastic SurgeonsChicago, Il, United States
My organization is implementing a new project management system and we are looking to set some clear guidelines as to what defines a project vs. a task, etc. Saving Changes...
Sort By:
Dinah YoungProject Manager / Software Asset Manager| Prince William CountySpringfield, Va, United States
We used a time and cost measurement. If it takes more than 2 weeks or will cost more than $5000 it is a project. Saving Changes...
1. Duration, e.g. 2 weeks to complete
2. Effort, e.g. 20 days to complete
3. Cost, e.g. $20,000 to complete
4. Risk, e.g. 2 High Risk items (however you assess risk)
5. Teams e.g. 2 teams involved
6. Complexity e.g. 20 tasks to be performed
7. Significance, e.g. high visibility or importance to the company
8. Criticality, e.g. must meet externally imposed dates, compliance, etc.
9. Impact, e.g. 20 users impacted Saving Changes...
Greg GithensAuthor, "How to Think Strategically." Executive & Leadership Coach| Catalyst & Cadre LLCLakewood Ranch, Fl, United States
A project (versus a task) is something that can benefit from the use of project management tools (WBS, network logic diagram). A task is something that you can keep straight in your head or with a few notes. Projects are more complicated, and project management tools help to manage the complicated-ness.
I know this logic is a bit circular, but it provides benefits in that you don't start expecting a bunch of non-value adding methodology. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
It does not matter. What matter is it will be an endeavor to achieve strategical objectives (at minimum to survive, growth and develop) by creating a solution and resources must be assigned to it. Saving Changes...
Marcelo Martinez CarreonTechnical Project Manager| Lululemon AthleticaVancouver, British Columbia, Canada
I had a similar implementation for a PM system at my company recently. I work in a central technology department team that offers internal support to TV animated productions. The internal tech resources are always split between support and projects. Projects and daily maintenance and support operations always had a blurry line.
What we concluded is, it will be a project if:
-The process is unique. E.g setting up a TV show folder structure each time is a daily task. Standardizing a show setup workflow is a project.
-The process has a clear end date.
-The process is cross-team dependent.
-The process affects/benefits productions and/or external vendors and stakeholders.
Hope this helps.
Cheers. Saving Changes...
Tamer Zeyad SadiqAssistant Cost Manager| Turner & TownsendRiyadh, Ar Riyad, Saudi Arabia
There are already mentioned in appendix of PMBOK!!!! Saving Changes...
MOHAMED ANSARI M AIndependent Consultant| FreelanceKozhikode, Kerala, India
I would use Sergio's word as the benchmark in all cases. Also going by all other advices listed above, anything bigger than a single task would qualify well for the "project" tag. Also every Project is unique in itself but the Tasks are not Saving Changes...
Nicholas TufaroCEO| Tufaro Information SystemsHudson, Fl, United States
In addition to using the guidelines and definitions that are set by the PMBOK, you may want to conduct a survey of all past projects/tasks/efforts for the past 2 years. Log them into a spreadsheet giving each one a name that would be logged in each row of the spreadsheet. Then for each column, have headings named Scope, Schedule/Time, Cost, Stakeholders, Quality, Risks and any other item that you think might be helpful as defined in the PMBOK.
As you log these characteristics of each of these efforts, you will see a trend that will help define what a project is versus a task is. This may be your baseline or your metrics in determining how future efforts are categorized. Saving Changes...
