How are people estimating efforts for developing and maintaining Helm chart based product releases?
This is a somewhat open ended question but I am looking for some real world, practical knowledge/experience about effort estimation for developing and maintaining Helm chart based products.
Helm3 is supposed to make deployment of applications to Kubernetes platform easy. The helm install/upgrade/rollback single commands to do the deployments on the surface make it sound easy. But this is slightly deceptive though. The actual process involves:
I am looking for information like what effort estimation/story points estimation strategies people are using.
Practically, how many people are working in your teams on the full development lifecycle discussed above. Of course this may vary from team to team and product to product. All aspects above may or may not apply to your projects.
I think how to estimate java, dotnet, frontend projects is relatively well as we have been developing those for some time.
Do you have any insights to share?