A way to use BMAD with multiple human team members?

[RationalSolutions]

Alright, so I have been using BMAD on a side project and it has been phenomenal. I am trying to figure out how I can use it with my enterprise team for my day job. How can I adapt BMAD to work with multiple humans working across a large number of repos?

My initial thinking is that we would set up a repository for all of our BMAD artifacts, workflows, and agents, utilize the JIRA MCP for creating stories etc from the planning docs.

Has anyone else gone through this exercise? What has your experience been? How have you set it up?

[dickymoore]

Great question and I'm keen to hear the answer too. I think the first step is intelligent sharding etc and then using an external board like Jira for managing the tickets. But I do wonder how it all works together especially for git conflicts etc, and whether teams can only collaborate on the Implementation phase or you can also do it through Analysis, Planning and Solutioning, as that's when it'd be great to delegate to the UX experts etc.

The whole makeup of an Agile team is going to be transformed by swarm technology like BMAD, IMHO, but I don't know what to. Will be watching this thread keenly.

[rdalfonso]

I had the same exact question! In an Enterprise environment at large companies: shouldn't each agent persona (architecture, PM, front-end) be created and used by that specific human in that role, using the unique available commands, to refine each area of the application for the final spec?

[64dude]

I've been working on both intra and inter team collaboration for BMad since v6 beta, and testing it in enterprise scenario. I've draft a playbook. Consider attached?
bmad-git-playbook.docx

[AquaticAlpaca]

Several generated documents store absolute paths (including the user's home directory) which would break multiuser setups. For example, epics.md and ux-design-specification.md include "inputDocuments:" in their frontmatter which contain the absolute path of documents such as prd.md.

inputDocuments:
  - /home/username/dev/project-name/_bmad-output/planning-artifacts/prd.md

Anyone not named 'username' is going to have trouble working on the project, not to mention the fact that it seems problematic to commit those details to git.

Ideally, bmad-method would make robust use of placeholders (ie {project_root}) instead of absolute paths, but this doesn't seem to work across the board yet.

[64dude]

Let me review where this is in v6.7.1.