Looking for idea of a structured exercice to identify/highlight dependencies between multiple projects in an organization?
Thinking of post-it with different colors for projects and putting phases/milestones, and some other arrow stickers to visualise the dependencies.
Not looking for software at the moment, but a way to map these dependencies in an exercice.
Thanks. Saving Changes...
Sort By:
Drew CraigSr. Agile & Product Coach| VanguardPhiladelphia, Pa, United States
Try something along these lines...
- Build a least of all application owners
- Require a request submission prior to work beginning on a new initiative
- Request includes questions that will succinctly describe the goal
- Submission spawns email notification to group
- Each member required to review and sign-off - noting whether their group is impacted.
This provides wide visibility and a record of review/sign-off. Best if the process is within a system of record. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
First of all you need to identify the item that will determine because projects are related. With this on hand using post-it is the tools that give me the best results. Saving Changes...
Stéphane ParentSelf Employed / Semi-retired| Leader MakerPrince Edward Island, Canada
Unless you are integrating cross-project dependencies, I have found the use of external milestones sufficient to the task. I colour the external milestones so I can quickly identify them and keep on my list to verify. Saving Changes...
