A small project is one that is more likely to be conducted in a less formal manner than larger projects that are more difficult, dangerous, huge in scope, or that will take a long time to complete. For the latter, formal decision-making organization, a considerable number of individuals on the project team, maybe numerous phases each followed by a 'go' or 'no-go' decision, and, of course, a greater budget are usually required. To avoid making the mistake of tossing away all of the good sense that has developed around formalized projects, keep in mind that what you will need for small projects is likely to be a simplified, leaner version of project best practice.
A little project is much more likely to be an assignment that is difficult to complete because of the following reasons:
Duration
Objective(s)
Scope
Requirements in terms of resources (probable project size in person-days)
Risks to your company's operations
There are a large number of stakeholders.
Budget\sDependencies
The level of simplicity falls below the threshold at which an organization would require more formal project management, methods, methodologies, and organizational structure to function properly. However, it makes sense, particularly in these difficult economic times, for even minor project expenditures to be authorized, monitored, and reported. This kind of management is referred to as 'Light Touch' management.
Small projects offer an additional 'hidden' value in that they serve as excellent training for future project managers, which is something that is often overlooked. This is why you should consider incorporating small parts of "best practice" into your daily routine to create habits that will serve you well in the future. Following the idea of only doing things after you have planned them, no matter how basic the plan may be, should be among them. To begin, learn about the small project's objectives, scope, restrictions, and any assumptions that have been made, as well as "who needs to know what" as you move forward in your planning.
Once you've gathered this basic but critical information, you might want to build a dated 'to-do' list that contains easy prompts to help you get things done. What information must be submitted, and by when? How much will it set you back? A basic way of documenting progress and expense information, such as a journal or notebook, should also be in place; however, you should be conscious that others may need to refer to it in the event that you are gone from the project for whatever reason. The use of such records is beneficial both during the course of a project and afterwards, when you can compare what really happened to what you anticipated to happen and draw important conclusions from any deviations from the plan.
Even if the project may be modest in scale, a professional approach taken by the person or small team will assist to guarantee that it delivers exactly what the organization requires in terms of results.