We need to identify sets of epics, features, stories and/or tasks that could be applicable across engagements. We could have them in separate templates (e.g. ci-cd-backlogItems.json could have things like setting up linting, build and test gates, general.json could have something like creating, agreeing upon and documenting a working agreement, etc.)
Ideally it would be something we could keep in a repo independent of the CLI itself (i.e. the playbook repo) so the content can be updated independent of CLI versioning.
This issue is meant to be a conversation starter and, if we get traction, will probably be a more widely discussed part of this whole project. Would be cool to see what each of the fundamentals champions groups could come up with
We need to identify sets of epics, features, stories and/or tasks that could be applicable across engagements. We could have them in separate templates (e.g.
ci-cd-backlogItems.jsoncould have things like setting up linting, build and test gates,general.jsoncould have something like creating, agreeing upon and documenting a working agreement, etc.)Ideally it would be something we could keep in a repo independent of the CLI itself (i.e. the playbook repo) so the content can be updated independent of CLI versioning.
This issue is meant to be a conversation starter and, if we get traction, will probably be a more widely discussed part of this whole project. Would be cool to see what each of the fundamentals champions groups could come up with