As a project manager, if you are given a project how to classify the project into Small,Medium and Large.Please help me to define .Please post details and parameters tondecide. Saving Changes...
these are subjective terms, and if used, would usually be defined by a governing body of some kind as part of your organization's project management policies or standards.
Different criteria to consider are:
- Cost
- Duration
- Work effort (usually ties back to cost)
- Magnitude of impact or benefits
- Number of impacted stakeholders
- Magnitude of requirements/"Size"
- Complexity - this would usually need to be derived based on a number of other criteria
Yeah I would say cost, duration and # of stakeholders are a good guide for classification of size. Saving Changes...
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Kiron shared good points. And if your organization does not have this set, then you can help to create it!
Question, what is the purpose of the classification? Generally, it's to provide a mapping of documentation requirements or method of prioritization and resource allocation.
Could you provide additional information? Saving Changes...
I would add to Kiron criteria the industry or kind of project.
1 million in one industry might be large for an industry and small in an other. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
The point is: it does not matter. Or let me put it into other words: which is the objective or reason to classify the project? That is what matter. For example, into the organization I am working today, we use a combination of three factors. The classification is done as a matter to have a first impression about our whole portfolio. No more than that.
...
1 reply by Vincent Guerard
Nov 23, 2017 6:33 PM
Vincent Guerard
...
Agree in the end you use it to classified your portfolio.
You just need to determine the criteria’s that apply to your organization portfolio.
The point is: it does not matter. Or let me put it into other words: which is the objective or reason to classify the project? That is what matter. For example, into the organization I am working today, we use a combination of three factors. The classification is done as a matter to have a first impression about our whole portfolio. No more than that.
Agree in the end you use it to classified your portfolio.
You just need to determine the criteria’s that apply to your organization portfolio. Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
Classification can also be driven by the level of Project Governance required .
Small :- Doesn't need Governance by other external departments if it's a project driven by the ICT department . for example, replacement of technology components like Hardware that do not directly or significantly impact a business process.
- Could also mean the budget is pretty small
- Could also mean that the team itself is from one department
- Could also mean that the project can be completed within a short period of time
Medium :- will need a representation from another business unit on the steering committee, if ICT is building a software or doing a data migration project for another business unit
- Could also mean there are more stakeholders
- Could need Subject Matter Expertise from another department apart from the ICT resources
- Could need a vendor if there is legacy software from a niche market
- Could also mean the project could be more time consuming than a small project
Large - Enterprise Wide project like implementing a CRM or an ERP solution .
- May require multiple steering committees and governing bodies.
- Changes the entire business process of the company .
- Will need significant stakeholder engagement and communication management plans
- Will run into millions of dollars
- Will be executed in phases
- Will be executed over a number of years
- Will require collaboration with multiple vendors Saving Changes...
Mostly Time , a project's size can be defined based on the following points:
1-Total financial resources available
2-Number of team members involved
3-Number and size of deliverables to be produced
4-Complexity of deliverables to be produced
5-Timeframes involved in delivery Saving Changes...
Markus KopkoAI Enabler for Project & Program Mgmt | Founder PMotion.ai / The PM
AI Coach| PMotion.aiHamburg, Hamburg, Germany
you can find a classification table as an example in this project charter template I have conducted: