How to monitor and control projects

Monitoring and Controlling is the largest and continuous part of the project management. It keeps eye on everything that’s happing in/out of the project and adjusts as needed.  
A good project manager is constantly monitoring every single thing happing in the project. If you find the problem latter it’s hard and more expensive to solve it.
The below practices need to be followed by a project manager for an effective monitor and control of the project:

Soft Skills in Agile Projects

Soft skills are personal attributes that enhance an individual's interactions, job performance and career prospects. Unlike hard skills, which are about a person's skill set and ability to perform a certain type of task or activity, soft skills are interpersonal and broadly applicable.

A set of skills that influence how we interact with each other, it includes such abilities as effective communication, creativity, analytical thinking, diplomacy, flexibility, change readiness, problem solving, leadership, team building and listening skills.

Negative Stakeholder Management

There are positive and negative stakeholders in every project (according to PMBOK). Positive ones will benefit from project implementation, for example their work will become more effective, more automated, easier, and more fun. At the same time negative stakeholders will have problems once the project is implemented. For example, they will be fired because their job will be done by new software.

Type of Project Reports

Most of the organizations have their own template for reports, in addition to that the Project Manager and your team has their own format.

Each report takes own time to collect information, write, read, maintain and act on the action items.

Based on my experience, come up with the important reports required in the project, purpose and the important aspects needs to be covered in the report.

Importance of Non Functional Requirements

The functional requirements are day-to-day requirements which business users and stakeholders needs in the product.

It is important to consider the other requirements also; these are called “Non-Functional Requirements” and fits into the organization's operational environment. This is the obvious requirements that your business users may not think about it.