Conduct a dependency mapping session

Begin by welcoming the team and explaining what each section of the template (listed below) entails.

Processes Impacted: The aim of this section is to be as comprehensive as possible as you brainstorm processes, both upstream (input) and downstream (output), that will affect or will be affected by your work. You will continue to use this dependency mapping document throughout the project, so write down details as to how each system will be affected.

Risks and Mitigations: Make a plan of potential risks to ensure they don't derail your project.

Feedback Loops: Consider this the action plan for managing the dependencies and risks you've just articulated. Make sure each major risk has an owner within the project and a communication channel to ensure information is flowing and being shared with relevant teams.

Begin with Processes Impacted, and as a team, brainstorm all the systems that are affected by your work. Once you have an exhaustive list for each process articulate:

• Owner – the team and/or main point of contact for the process.
• Type of impact – how does your work relate to this process?
• Description of impact – include enough detail to build a shared understanding among team members and stakeholders.

Move on to section two, Risks and Mitigations, and give everyone 3-5 minutes to independently brainstorm risks. Share back to the group and document the agreed upon risks in a table with the following information:

• Risk – describe what could potentially derail the project.
• Level of impact – high, medium, or low.
• Mitigation plan – how you will respond if this risk becomes reality.
• Owner – which member of your project team is leading the mitigation plan?

Now that the complex web of dependencies around your project is clearer, it's time to get proactive about management. In the last section, Feedback Loops, you will look back at all the risks and dependencies highlighted. For those that need to be actively managed throughout the project, name a stakeholder with whom you can partner to ensure alignment. For each stakeholder, complete the following information:

• Stakeholder – name the person with whom you will partner.
• Review frequency – weekly, monthly, or quarterly.
• Feedback notes & actions – use this space to share updates after your weekly/monthly/quarterly stakeholder conversations.

Materials on this website were produced and/or compiled for the purpose of providing Canadians with access to information about the programs and services offered by the Government of Canada. It is subject to the following Terms and conditions.

This work is a derivative of “Dependency Mapping” by Atlassian and used under a Creative Commons Attribution 4.0 International Public License (CC BY-SA 4.0).