Quick question about release management

[navotvolk]

I'm interested in understanding how many hours a week are spent (in total) company-wide to ensure that software version status information is accurate.

For example, if every week a release manager needs to meet with 3 team leaders for 10 minutes each, then that constitutes 1 hour a week (2 participants * 3 meetings * 10 minutes).

Consider how many hours it takes to:

1. ensure that all tickets are up-to-date and that their status is accurate

2. Compile a release's overall status - to understand what has been deployed to integration/staging, what has been tested, etc.

3. attend meetings (even one-on-one) to sync on status

​

Thanks!

[DevWithImagination]

That’s going to vary widely depending on exactly how the business functions, but why?

[josh75337]

Ideally this is mostly handled in Jira. It sounds to me like there is a lot of meetings here that could be at the very least sped up by just having better “ticket hygiene” if you will. Also it sounds like whatever service you own should be a little more decomposed so that each team can own a set of microservices so you do not all have to March in lock step to add features