3 key qualities that are a must if you want to succeed with project management

Project management is no easy task. It could cause you to scratch your hair, want to rip out your eyeballs and throw tables out of anger. Due to the nature of project management, there are 3 key qualities you need to succeed. Do you tick all 3 boxes?

3 key qualities:


Communication is the number 1 quality every project manager needs, for definite. There is no way around it. Without this vital quality, prepare for a shock. If you don’t communicate effectively to your team, then chances are, your team won’t have a solid idea of what you are trying to achieve with a certain task. This could lead to many issues including a failed project, relationships turned sour, and more baggage.

Communicating with all stakeholders is also very important and should not be left until the last minute. Stakeholders play a massive role in the success of an organization so involving them each step of the way can benefit projects in many ways.


This word isn’t thrown around a lot in the project management industry but in my honest opinion, it is one that should get a lot more attention. Going into a project knowing there’s a possibility that the project is going to fail and not go the way its planned is critical. This is because it allows you to learn from your mistakes and find alternative routes and methods to achieve your goals


Learning humility not only enables you to improve your morale within your team but also allows you to adapt to new changes within the business a lot faster, which is much more important now than ever due to the new changes in Article 50

Being respectful of the needs of the business stakeholders is another way to show humility as these stakeholders may not understand the limitations that come with using the system. This means they won’t know exactly what’s possible and what isn’t as well as the level of risk associated with performing certain tasks for the project.


Linking back to the previous point, having respect for your team can help your project in terms of getting it done at a higher quality and a faster efficiency.  One good mindset to have always is that your team works WITH you and not FOR you. Many people use the wrong mindset when creating and planning projects and this leads to projects failing before it already begins. Always maintain a friendly tone with your team and let them know that you’re there to help. This helps boost morale and help productivity.

Having these 3 key qualities is a must if you want to succeed in the world of project management. If you don’t have any of the above or just a few, focus on trying to learn the other qualities and try implementing them with your projects. You’ll notice a huge difference in terms of work ethic, quality, and morale.

Do you tick all 3 boxes?

Send us a comment below with your experience on using these 3 qualities to enhance your projects.

, ,

New to Agile?

In short, agile and lean are general concepts, the former basing on Agile Manifesto and the latter on Toyota Production System. Then we have Scrum or XP, built over agile, and Kanban, built over lean, which are specific methods teams can implement, like Prince2.

Personally, I don’t treat agile and lean movements in a very orthodox way — they base on the same principles. So, to some point, they’re overlapping. Also, you will find teams mixing methods from both houses, Scrumban (a combination of Scrum and Kanban) being probably the most common.

If you wanted to position agile/lean methods somehow I’d say that:

  • Scrum is the closest to the old-school project management methods, although it doesn’t really deal with formal side of project management.
  • XP focuses on engineering practices and is generally programmer-centered.
  • Kanban is often dubbed change management framework as it doesn’t change the way team works on the day 1 and lets the process evolve over time.
  • As all three focuses on different things, it isn’t uncommon to see them, or their parts, used jointly.

If you want to learn more I’d start with such set of materials:

  • Introduction to Scrum on Mike Cohn’s site. If you want more on Scrum Mike Cohn’s site is a good place to find also more advanced stuff on Scrum.
  • Once you know what Scrum is I’d strongly recommend Henrik Kniberg’s and Mattias Skarin’s minibook Kanban and Scrum – Making most of both which is great in terms of describing Kanban but has a lot of referrals to Scrum.
  • For more advanced stuff on Kanban I’d recommend Limited WIP Society articles (topic for my next blog).
  • Good kick start on XP can be found on Ron Jeffries’ site.

In terms of books as a kick start, I’d recommend:

  • Mike Cohn’s Succeeding with Agile for Scrum
  • Kent Beck’s Extreme Programming Explained for XP
  • David Anderson’s Kanban for Kanban

If it is too much of a hassle to read these books and digest then contact us and we may be able to help you.