I have worked in large job environments with Primivera or MS Project maintained by dedicated resources. The overhead they add make sense for a wide view of mul

I have worked in large job environments with Primivera or MS Project maintained by dedicated resources. The overhead they add make sense for a wide view of multiple department swimlanes across a complete effort life cycle. My experience here is your WBS should keep the activity line items way above the level of anything in a Github issue. A L5 WBS plan might go [PROJECT_A > PHASE_2 > DATA CENTER > COMMON_SVC > SINGLE SIGNON {5d Duration | 3 Engineers x 10 Hours}] -- SSO itself might be a 30 point todo list for 5 people but those will be managed separately closer to the ground as the work approaches and runs through using a sharper tool - and if the team is ok with GitHub issues then fine there are a hundred ways to do it and none of them perfect; but it would get messy fast using a full blown PMO Software package for backlog type issues. If you had to add another level to WBS it would be generic milestone activity like Prototype/Test/Deploy dates.