Second, ideally you don't have all the management you allude to. You might have a portfolio owner to whom the PO and ScrumMaster "report."
But given an organization in transition that still has all that middle management - and if I had to pick from your list - I'd pick product management. A key to Scrum success is having cross-function teams. I want a reporting structure that discourages silo thinking and facilitate cross-functional collaboration.
Tim
> The worst one I know of: reports to PO
> The best one I've heard of: reports to the Team
+1.
Also ideally, the ScrumMaster is *chosen* by the Team and PO.
--mj
Defining the proper hierarchy for Team and Scrum Master is important. I know Scrum works in flat hierarchy, but hierarchy plays major role.In my organisation Scrum masters reports to VP Software Engineering, with other Team members. Release Management is a separate tower and same with Product Management and QA. But, all reports to SVP.So, at any point of time I found Tean keeps commitements of VP Software Engineer over Release Management. That always creates odd situation for Release Management and Scrum Master who is commiting to Release Management.VP Software Engineering keeps his priorities and defines their way of working, and that leaves Release Management in odd situations.I believe Scrum Master with whole (at lease development team) should come under Release Management and Release Management should come under Product Management. VP Software Engineering should be a sub function of Release Management.
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.To post to this group, send email to scruma...@googlegroups.com.
To unsubscribe from this group, send email to scrumallianc...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scrumalliance?hl=en.
Defining the proper hierarchy for Team and Scrum Master is important. I know Scrum works in flat hierarchy, but hierarchy plays major role.In my organisation Scrum masters reports to VP Software Engineering, with other Team members. Release Management is a separate tower and same with Product Management and QA. But, all reports to SVP.So, at any point of time I found Tean keeps commitements of VP Software Engineer over Release Management. That always creates odd situation for Release Management and Scrum Master who is commiting to Release Management.VP Software Engineering keeps his priorities and defines their way of working, and that leaves Release Management in odd situations.I believe Scrum Master with whole (at lease development team) should come under Release Management and Release Management should come under Product Management. VP Software Engineering should be a sub function of Release Management.
--
You received this message because you are subscribed to the Google Groups "Scrum Alliance - transforming the world of work." group.
To view this discussion on the web visit https://groups.google.com/d/msg/scrumalliance/-/sgjcyOpBNJwJ.