The new certified project manager in the team shares management practices

The new certified project manager in the team shares management practices
The new certified project manager in the team shares management practices

I am the new certified project manager for this project. I am the main person for communication, exchange of information, advice, and needs regarding the project.

I am a responsible person with very good time management and multitasking skills, who insists on good communication and teamwork. I regularly monitor the time worked on the project in order to comply with the pre-approved plan and the invoicing of the work done on it. I follow closely and I am clear with the current status and available resources of a project.

The certified project manager helps the team

I could help the teams in the distribution of tasks and the time period for their implementation, as well as in the product documentation. I am there for advice and need help. For me, working together is a key factor for success.

That is why I would like to know what your requirements and priorities are. Would you help me with the contacts of other people who are involved in the project?

Or other countries you work with that would be useful. What way of communication do you prefer? The budget, the necessary resources, possible subcontractors, the frequency of invoicing, the ways and terms of payments under the project, etc. should be discussed. Projects require constant and timely communication. I leave a contact phone for a faster way to communicate.

Mutual assistance is important to me. I believe that the provision of information and the status of the project from the very beginning is a guaranteed success for a project. It is important to see if the objectives at each stage have been achieved if the budget that has been set in advance is being followed.
You can count on me! For me, your regular feedback is extremely important. Reference: Qualities of the certified project manager,

Presentation of the project manager to the organization

Thank you for the opportunity to work in this organization. It is a pleasure for me to be a Project Manager in your company.
During the week I am here, I think I have demonstrated some of my strengths and skills, namely, proper coordination of people and processes, developing a detailed project plan, taking into account the resources. Read more: Certified project manager for their training,

I believe that the key to the success of a good Project Manager is to communicate and coordinate the people in his team to create a comfortable and promising environment for product development. From this point of view, the experience I have as a teacher helps me not only to communicate with different people but also to prioritize tasks, organize my time properly, and be creative.

What will also be useful to me, being in this position are the following qualities that I possess: responsibility, orderliness, and critical thinking.
The in-depth knowledge I have in development would be useful in communicating with external clients of the organization and you can always count on my support and assistance.

What way of communication would you prefer to lead? Online or through conversations? I can present your documents and reports initially on the assignments and packages, and subsequently on the movement and development of the project itself. Do you want me to send you detailed information (documents, plans) regarding the development of the project every week?

I believe that through communication, responsibility, and support we will achieve success in product development. You can count on me. Read more: Presentation of the project manager to stakeholders, clients and project teams

Waterfall and Agile project management methodologies

I prepared a description of the “Waterfall” and “Agile” methodologies, as well as a detailed comparison of their main characteristics. I hope the information below is helpful.


“Waterfall” is a sequential process of steps that includes the following phases:

  • Analysis
  • Design
  • Development
  • Testing
  • Installation
  • Subsequent maintenance

Everything is simple and consistent. An analysis is made first. Then a prototype is designed and developed. When we have a finished product, testing is performed. Detected bugs and problems are fixed later. The product is implemented after fulfilling the initially set quality criteria. The last phase includes all product maintenance activities. Reference: How to Become a Project Manager,

Many people prefer the “Waterfall” methodology because everything seems simple and logical compared to “Scrum”, for example, where you have to deal with all these “sprints”, daily meetings, etc.


“Agile” is like many waterfalls performed in successive cycles. While with Waterfall you build the whole product from the bottom up in one cycle, with Agile the product is broken down to be developed into smaller parts or functionalities, all of which go through a process similar to Waterfall. PM.MBA  strictly inspects both classic project management certifications and Agile practices so our team needs to follow transparent guidelines.

In this way, each part of the product goes through the cycle of the waterfall, gradually creating the final product. The individual cycles (repetitions) are called “sprints” and usually last from one to several weeks. Each sprint must include testing before moving on to the next sprint.

Comparison of the main characteristics

Important features of any software development methodology include:

  • Flexibility
  • Ease of entering and meeting deadlines
  • Testing
  • Predictability
  • Documentation
  • QA
  • Customer and consumer participation


It is important to know how flexible your chosen model is, ie. how easy it is to change requirements on the go in the development process. With “Waterfall” there is almost no flexibility if the development phase has already started.

In comparison, Agile offers much more flexibility. If the requirements change suddenly, you can apply them to the next iteration, in most cases. There are many software tools for project management using Agile practices like Scrum. We can use such technologies to become faster. Reference:

If the product owner suddenly changes his mind and decides he wants something completely new, then developers will probably have to start over, regardless of the methodology used.

Ease of entering and meeting deadlines

With “Waterfall” all deadlines are clearly defined. This does not necessarily mean that they are always followed, but there is definitely much more predictability than with Agile.

If it is not clear how long the project will last or there is a high probability that additional functionality will be included for development in the meantime, then “Agile” would be the better choice. Reference:


With “Waterfall” testing is performed at a later stage in a separate phase. This often leads to a delay in the final release, as many errors and problems are identified at this stage, which requires long-term correction and leads to delays.

With Agile, testing is performed in each sprint, which allows much faster identification and resolution of technical problems.


With Waterfall, it’s much easier to set deadlines and estimate the resources needed than with Agile.

In most cases, it is impossible to calculate exactly the total amount of resources needed for a flexible project.


Documentation is an important part of any software project. The documentation is done before and during the project implementation. The waterfall project management approch provides much more documentation than Agile, due to the specifics of the work.

QA (Quality Assurance)

Agile usually provides much better design quality, as each functionality or a significant part of the product goes through a full cycle of development, testing, etc. This ensures that each part of the product works perfectly.

Customer and consumer participation

Both models offer different levels of consumer and customer engagement. With Waterfall, the customer participates to a large extent before the start of development and after its deployment. Users usually participate only after the first release.

At Agile, both stakeholders are actively involved in the whole process. This allows achieving better quality, which satisfies both the owner of the product and the end-user.

Published by

George Brown

George Brown is a lecturer in project management and Agile practices and is the author of the articles on this educational website.

Leave a Reply

Your email address will not be published. Required fields are marked *