Previously, I started part one of this article centered on project management and more, and on the first part, I dwelled on counting the cost of a project detailedly before starting and more about that. Maybe you missed it, but that's not an issue because I got you covered. You can just visit my blog to read through it or to save you the stress. Press the link below, and it will automatically direct you to the article so you can read.
@mrhive001/counting-the-cost-before-embarking-on-a-project-one-of-the-best-financial-rules
Part two of the continuation of this article dwells on the "editing aspect of project management.". A quick revisit or reminder to the previous article, I made mention of most of us in this hive blockchain space, or precisely subscribers of the Inleo community that continually engage or not; they have in one way or another handled a project, and it's of necessity that after counting the cost a project has, which is what the first article talked about, there is an edit to the project so as to make it easier going and fit for accomplishment.
Consequently, during the editing of a project, it is necessary to first of all know the core routes and points that serve as the foundational successes of the project being handled, and while editing or modifying it, the main structure would be retained. I have come across projects that, just by looking at them, I know that the project manager edited some parts of them; that's why it was this successful or this bad. A quick action should be taken on the employee means or editing done because some projects can be edited to the extent that the main form or set goals it would have achieved are knocked off and the desired success is not achieved.
While editing a project, the following must be considered:
(a)
During the editing of a project, a consideration of what the project is set to achieve is to be given the utmost importance, because if this is forgotten, the project should be nullified as if it never existed. What a project is is defined by what it is set to be achieved; if what it was set to be achieved is edited off, then, in the first place, it was given to a good project manager; secondly, it is not worth embarking on; it is just like salt that has already lost its taste; of what use would it be again?
(b)
The locality in which the project is to be executed should be of interest too. For example, there are some projects that can be done in the uptown, whereas others are to be done in the rural area. Regardless, their is a desired outcome to be gotten, as is the turnout too. Now, for one in a rural area, the consideration of recreating something that such a locality hasn't seen for such a long time or, to an extent, what they haven't seen before should be taken into optimum consideration because those living in such areas should be given a long-standing memory that is difficult to forget easily, and it should be done once during the course of the execution of the project, whereas in an uptown area, the segments of the project should be given a whole lot of view, worthy of being revisited often by people who wonder what actually happened. Such work wouldn't be done once, but segments by segments, and the mass turn-up is always different because it is in the uptown. A good project manager knows about this and, as such, while editing it, takes full cognizance of it because jobs might come from people that come across the project, both rural and uptown. To understand this more, an example would be given, and I expect someone to ask me that in the comment section.
(c)
While editing a project, a consideration of the time the project needs to be fully done is of great importance. The timing of a project is of great importance, and to some extent, this contributes to the great success a project has. If the timing isn't right, then expect an awful end.