1] Deploying project management princples with Asana

Many of us using Asana are actively involved with project management - in one form or another.
I thought I would share a few tips and techniques that you can implement to put your project management principles into action.

I follow the Project Management Book of Knowledge (PMBOK) by the Project Management Institute (PMI). I won’t share the different approaches to project management, but I will talk about the domains or knowledge areas (older PMBOK guides), and managing a project on Asana, makes it really easy to cover all those domains.

Grab your coffee :coffee: and hopefully(?!) enjoy!

These are the domains you need to be mindful of when managing a project:

  • Stakeholders
  • Team
  • Development Approach
  • Planning
  • Project Work
  • Delivery
  • Measurement
  • Uncertainty

Screenshot 2024-04-09 at 14.02.56
Figure 1.0 Project Performance Domains (PMBOK Guide, PMI 2020)

So how can Asana help you adhere to your project management domains for a better successful outcome?

In this post, I will share two domains: Development Approach and Stakeholders.

Development Approach:
Whether you use predictive, Agile or Hybrid Asana has you covered. The simple approach is to build your project with a view in mind.
For predictive, make your project list view. You can benefit from the Gannt chart view as well as the calendar view.
For Agile, make it a board view.
For hybrid, use a combination of list view and timeline. The intention of the timeline is to give you the high-level progress and dependencies of the tasks. I find it useful when the project has sections/custom fields that differentiate work between agile and predictive. For example, project action items vs product development sprints.

Stakeholders
With stakeholder management, you need to consider the following activities:

  • Identifying stakeholders
  • Gathering Stakeholders’ Expectations
  • Managing Stakeholders

Identifying Stakeholders: If you run exploration meetings with your team at the start of the project, or if you are given your stakeholders at the start of the project, Asana overview tab allows you to add the project stakeholders and identify their roles. This is very helpful for the life of the project, especially if the team grows/evolves with the life of the project

Screenshot 2024-04-09 at 15.17.46
Figure 2.0 Project Members and their Roles on the Overview Tab

Gathering Stakeholders’ Expectations:
Understanding their expectations spans from what they expect the outcome of the project to be to their expectations from the communication of status updates and risk escalation.

Depending on the size of your stakeholders, you can either use:

  1. Forms: These help you ask specific questions, and your stakeholders will submit their details. These will be captured in tasks. If the project has many stakeholders, I would suggest creating a project for stakeholders where you use it as a reference and keep a record of all expectations.

  2. Assign tasks to the stakeholders. Use custom fields and questions in descriptions for them to populate. This will be stored directly and easy for you to work with.

  3. Managing Stakeholders: The most effective way to do so is through the status update feature that is embedded within the project. You can now also access ‘draft with AI’ for a more efficient process. The status update allows you to provide information on what was achieved, what’s blocked and what is next in the plan.

:bulb:if your stakeholders are only interested in being informed, make sure you go to project permissions and notifications and untick all types of notifications for these stakeholders other than status updates. Keep it ticked. In the example below, Ginger is a stakeholder who only needs to be informed of the status update.
Screenshot 2024-04-09 at 15.26.35
Figure 3.0 Example of Project Notifications being managed

:bulb::bulb:If your project has risks identified, make sure you communicate the risk with relevant stakeholders before you issue the status update. So, for example, if someone needs to be informed first, add them as a collaborator to the ‘risk’ task for a heads-up before you issue your status update to the entire audience.

If you are interested in finding out more about what these features can do, here are the links to their section from the guide:

I hope you have enjoyed your coffee. Any specific domain you are interested in me exploring next, please let me know.

15 Likes

Thanks for this! Can you do uncertainty next?

2 Likes

Thanks @Carol_Morley
I am nearly done with my next two domains (Teams and planning).
I will aim to do uncertainty after that. :slight_smile:

2 Likes

If you enjoyed this post, the second one tackles Teams domain and it is out:

1 Like

Hi, @Rashad_Issa This is very good content.

Asana is advertised as being useful for project management, but I didn’t really get it.
Your advice was very easy to understand, and I’m thinking of using Asana for project management again.

1 Like

Thank you @Ka_Nishiyama I am glad you find it useful. :pray:

1 Like