To hit pay dirt

Some of you know how hard could be to fix up with customer (especially in a large company) a lot of documents when they are part of your procurement. 

You have to correct them again and again...to have discuss them with a lot of people, which can have some different opinions about the same things, which can have some different interests. 

But how could you make this process working quickly?

I have developed a habit over the years of working in consulting to do the following things:

1. To form a working group of experts, decision-makers in the case of a large project we need to establish several working groups.
2. For each direction must be the person responsible for the direction and possessing powers of decision-making in contentious situations.
3. Prepare the first edition of documents, and send them to the customer for given feedback.
4. Give feedback from all of people which take part in the fix up.
5. Write records of all observations in the table, record the answers to all remarks and add comments, especially if you don't agree with observation.
6. Change documents and send them again to the customer.
7. Organize meeting and discuss the documents, try to make the positive decision. 
8. If the positive decision didn't find on meeting, you have to distinguish controversial aspects with description their solution ways.
9. All final decisions must be agreed by the management Committee of this project and approved by the responsible for the project from the customer.

This is easily done when you have professionals in the field of project management, project office, and very difficult when they are not.

But some organizations don't follow project management processes, and they don't have project management professionals, techniques. And what can we see?

I was convinced on own experience, doing projects for two different large organizations. In one of them the specialists have been trained in project management according to PMBOK, the other heard nothing about it. In the first case, it was not difficult to organize the work properly and perform it easily. In the second case, it took some time on the organization of work on the project from the customer, as it was necessary to actually teach the ideology of project management and operation, as well as to overcome resistance and reluctance to change work style. But and one, and in another case, in the end, the process of working on documents was reduced to the mentioned steps.

I'll be glad to get your feedback.

Thank you for reading this.

Success to all of you. 

Yesterday, passed away the Russian writer, Daniil Granin (1919-2017), who had written, for my oppinion, the fundamental book in the Russian time management "This strange life".

This book tells us about the Alexander Lubishchev, Soviet scientist. Alexander Lubishchev devoted his life to science, including the study of using time. Alexander Lyubischev had made a monitoring and accounting time during of all his life. It had allowed him to achieve greater productivity of his activities in various fields of philosophy, biology, and entomology.

Thanks to the book of Daniil Granin method of using time-keeping has been widespread, and nowadays many of the developing and implementing time management systems use it as their basis.

My personal experience of how to improve the own efficiency with timing, I had described in my blog (https://www.projectmanagement.com/blog-post/24731/-Its-a-magic-time---).

The rules of timekeeping in the company will help you to evaluate the work activities. It will also increase productivity, as well as the possibility of introducing an incentives and rewards system.

However, you should be careful with using these tools because people usually do not like when they don’t feel free.  That is why the most effective will be the introduction of timing as a work culture, and as a means for all employees to benefit from it.

If anyone had not read this book, I highly recommend to read.

https://www.litmir.me/br/?b=226757&p=1

If you need a translation, write about it in comments, I could post book here in parts.

Recently I was actually in a situation very tight deadline and a too brief time. Except my mains projects I was attracted to work as an analyst for a large Federal project. And I had had to develop subsystem decomposition, description of the components and modules, and clarification of details and preparation of the final document in the two days.

I knew I must calculate my power for doing all work in time and with a high quality, and also I knew I must don’t work at night, and leave a little time to rest. I was decided to count the time and monitor them during work. I must have had to create eighteen schemes and their descriptions.

I created one and write the begin time and the end time. Then I made the same with another, because they could have had the different complexity.

I must have had to create eighteen schemes and their descriptions.

Then I made the same with another, because they could have had the different complexity.

After that I knew average time. And I developed my plan, I calculated time worked on each scheme and on its description accordingly with the complexity of the schemes.  The remaining time was planned under the necessary things, including eating, taking some rest, and sleep.

At the end of the second day I was finished the whole job. The secret is, as I think, that in these two days I had not spent unnoticed, perhaps, not one minute, not what hours.

Of course, such strict regulations are not always needed, but it allows you to gather, concentrate and to complete the job.

Measurement time is necessary for management yourself, for work management. And there are different ways to use it for the different types of work.

The time is magic, if you want to do something you will do it.

At work I was being asked to say about differencies between Scrum, Kanban and eXtreme Programming. And I'd like to share my thoughts with you. 

So, there are different methodologies you can use to manage project.
I think the main weakness in all these methodologies is poor knowledge about product. And sometimes we are trying to develop existence products when we need to create new system.
We need to choose methodology or to combine methodology tools in depending from kind of project and its scope. We need to take cognisances of experience, qualifications and conditions.