Gameplan is indeed a powerful tool for team communication and project organization, especially for remote teams. While it’s not directly integrated with ERPNext, you can use it alongside ERPNext to enhance collaboration and manage discussions related to your ERP project or other discussion.
and if I need to use it then I need to create two projects (for the same job) one for ERPNext and other for Gameplan, somehting which is against the philosophy of ERP.
At our company we have created a doctype timesheet , similar to projects and have integrated the same with game plan to track the hours charged, this is working out to be great to monitor progress and time utilization. This is how we integrated gameplan with erp next
In ERP there is a Projects module for managing rigid projects, and in this application, there is actually a module for managing flexible projects, i.e. development projects. For example, the standard set of statuses is actually a standard set of statuses for kanban.
Even now, the application and the module are linked together via the SSO, which makes it possible to use them together for cases when development tasks appear in classic (“rigid”) projects. From the description of the application, it is clear that this is justified by the prerequisites for creating the application. Since it was created specifically for the ERPNext team, which is engaged in software development.
I agree with the previous user, who reasonably pointed out the error of separating these modules for any other areas except development. For complex projects there is a need to integrate this application into the ERP (i.e. connect the Gameplan functions with the functions of the “ERP-Project” module).
Team communication tool is also needed for rigid proojects, though I am not very clear how to differentiate rigid and flexible projects.
Kanban statuses will also be useful rigid projets.
What is SSO?
It looks that different frappe teams are creating differet docType for the same purpose, like holiday | hd_holiday | crm_holiday, contact | crm_contact, task | crm_task and many more. The moment we think a doctype be used in two apps, then that should be moved to a core app, which might frappe, or an app pre-requiste for all such apps.