I am SM/PM on an internal project. Internal project X is technically and architecturally complex and demands high skill developers to work on. It has huge backlog.
However the project considered to be low priority comparing to external projects, and serves as a temporary shelter for developers waiting for assignment to other projects. Team changes during a sprint is a common problem. Team size varies from 1 to 20 near every day.
When i came to a project it was SCRUM based. Now we switched to Kanban board as sprint backlog and velocity becomes totally non-sense.
There is no possibility to change the company approach to X, i have tried. There can be no "core team" that remains constant except PO and me.
Problems encountered so far:
- Developer can leave a team any time dropping the story undone.
- Each developer has his own understanding of how to do things depending on a skill set and level which leading to a mess.
- There is a huge technical debt because of constant switching.
- Nobody can predict release date.
- You can have 3 QA no Dev's or vise versa. Or FE only or BE only.
- Management understands problem, however demands fixed release dates.
- There is no fresh stable version on demand.
- Story points of yesterdays team are not story points of today's team. Well at least when comparing issues.
- Dev can spend few weeks for getting into and than moved to another project.
- There is no good user documentation. You can check only comments on git, story's on Jira and wiki full of tech staff. There is no resources to create good documentation for it.
Action's taken so far:
- Fathers of a project making a code review of a critical components from time to time.
- Developers documenting what's done, what's need to be done for each dropped issue.
- Story's atomized to a level where no business value added but at least it could be done.
- We have automated where possible staging and local environment deploys.
Any advice's on how to make it less deteriorating?