What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nWhat has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nWhat has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nWhat has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nTo summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nTo summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nTo summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nTo summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nSome tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nWith many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nEach person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIn the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nWhile one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIn order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nThese, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIf the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIf the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIf the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIf the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nWhen we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n
If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIn my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n
When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n
If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIn many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n
In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n
When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n
If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nSo, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n
In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n
In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n
When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n
If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nIn some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n
So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n
In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n
In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n
When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n
If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nMost of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n
In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n
So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n
In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n
In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n
When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n
If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nI wish it was as simple.<\/p>\n\n\n\n
Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n
In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n
So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n
In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n
In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n
When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n
If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nOn the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n
I wish it was as simple.<\/p>\n\n\n\n
Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n
In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n
So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n
In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n
In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n
When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n
If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\nOne question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n
On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n
I wish it was as simple.<\/p>\n\n\n\n
Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n
In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n
So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n
In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n
In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n
When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n
If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n
These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n
In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n
While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n
In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n
Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n
With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n
Some tips to make this work well:<\/p>\n\n\n\n
To summarize:<\/p>\n\n\n\n
What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n
I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\n<\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Suggested solution:<\/p>\n\n\n\n <\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
What would be your advice?<\/p>\n\n\n\n Suggested solution:<\/p>\n\n\n\n <\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
That is to ask you<\/strong>, what they should do.<\/p>\n\n\n\n What would be your advice?<\/p>\n\n\n\n Suggested solution:<\/p>\n\n\n\n <\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
In order to avoid another long \u2013 potentially inconclusive \u2013 meeting, they chose option two.<\/p>\n\n\n\n That is to ask you<\/strong>, what they should do.<\/p>\n\n\n\n What would be your advice?<\/p>\n\n\n\n Suggested solution:<\/p>\n\n\n\n <\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
One \u2013 toss a coin and decide? But how to pick from three options with a coin? Someone suggested the throw of dice..<\/p>\n\n\n\n In order to avoid another long \u2013 potentially inconclusive \u2013 meeting, they chose option two.<\/p>\n\n\n\n That is to ask you<\/strong>, what they should do.<\/p>\n\n\n\n What would be your advice?<\/p>\n\n\n\n Suggested solution:<\/p>\n\n\n\n <\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
After a 3 hour discussion, the leaders had two choices before them.<\/p>\n\n\n\n One \u2013 toss a coin and decide? But how to pick from three options with a coin? Someone suggested the throw of dice..<\/p>\n\n\n\n In order to avoid another long \u2013 potentially inconclusive \u2013 meeting, they chose option two.<\/p>\n\n\n\n That is to ask you<\/strong>, what they should do.<\/p>\n\n\n\n What would be your advice?<\/p>\n\n\n\n Suggested solution:<\/p>\n\n\n\n <\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The marketing team felt that they are in the best position to give direction to this feature, as they are closest to the customers and would know how best to prioritize and scope the requirements.<\/p>\n\n\n\n After a 3 hour discussion, the leaders had two choices before them.<\/p>\n\n\n\n One \u2013 toss a coin and decide? But how to pick from three options with a coin? Someone suggested the throw of dice..<\/p>\n\n\n\n In order to avoid another long \u2013 potentially inconclusive \u2013 meeting, they chose option two.<\/p>\n\n\n\n That is to ask you<\/strong>, what they should do.<\/p>\n\n\n\n What would be your advice?<\/p>\n\n\n\n Suggested solution:<\/p>\n\n\n\n <\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The engineering team, however, was skeptical. They felt that there is a significant amount of work in interfacing with the sensors, the cloud based knowledge hub and the need for a driver override meant a responsive, effective UI \u2013 and so, the Product Owner must be from the engineering team.<\/p>\n\n\n\n The marketing team felt that they are in the best position to give direction to this feature, as they are closest to the customers and would know how best to prioritize and scope the requirements.<\/p>\n\n\n\n After a 3 hour discussion, the leaders had two choices before them.<\/p>\n\n\n\n One \u2013 toss a coin and decide? But how to pick from three options with a coin? Someone suggested the throw of dice..<\/p>\n\n\n\n In order to avoid another long \u2013 potentially inconclusive \u2013 meeting, they chose option two.<\/p>\n\n\n\n That is to ask you<\/strong>, what they should do.<\/p>\n\n\n\n What would be your advice?<\/p>\n\n\n\n Suggested solution:<\/p>\n\n\n\n <\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
This was considered an ideal project for the data sciences team, as it would involve a lot of modeling, analysis and inferencing. The first thought was to have the Product Owner from the Data Sciences team,<\/p>\n\n\n\n The engineering team, however, was skeptical. They felt that there is a significant amount of work in interfacing with the sensors, the cloud based knowledge hub and the need for a driver override meant a responsive, effective UI \u2013 and so, the Product Owner must be from the engineering team.<\/p>\n\n\n\n The marketing team felt that they are in the best position to give direction to this feature, as they are closest to the customers and would know how best to prioritize and scope the requirements.<\/p>\n\n\n\n After a 3 hour discussion, the leaders had two choices before them.<\/p>\n\n\n\n One \u2013 toss a coin and decide? But how to pick from three options with a coin? Someone suggested the throw of dice..<\/p>\n\n\n\n In order to avoid another long \u2013 potentially inconclusive \u2013 meeting, they chose option two.<\/p>\n\n\n\n That is to ask you<\/strong>, what they should do.<\/p>\n\n\n\n What would be your advice?<\/p>\n\n\n\n Suggested solution:<\/p>\n\n\n\n <\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
As the expectations of long range performance and superfast charging started increasing from customers, Commutronix launched a new initiative to incorporate real time analytics of vehicle performance by monitoring critical parameters and also adjust key parameters for various subsystems to achieve the goals considering the driving styles also in addition to the physical and mechanical parameters.<\/p>\n\n\n\n This was considered an ideal project for the data sciences team, as it would involve a lot of modeling, analysis and inferencing. The first thought was to have the Product Owner from the Data Sciences team,<\/p>\n\n\n\n The engineering team, however, was skeptical. They felt that there is a significant amount of work in interfacing with the sensors, the cloud based knowledge hub and the need for a driver override meant a responsive, effective UI \u2013 and so, the Product Owner must be from the engineering team.<\/p>\n\n\n\n The marketing team felt that they are in the best position to give direction to this feature, as they are closest to the customers and would know how best to prioritize and scope the requirements.<\/p>\n\n\n\n After a 3 hour discussion, the leaders had two choices before them.<\/p>\n\n\n\n One \u2013 toss a coin and decide? But how to pick from three options with a coin? Someone suggested the throw of dice..<\/p>\n\n\n\n In order to avoid another long \u2013 potentially inconclusive \u2013 meeting, they chose option two.<\/p>\n\n\n\n That is to ask you<\/strong>, what they should do.<\/p>\n\n\n\n What would be your advice?<\/p>\n\n\n\n Suggested solution:<\/p>\n\n\n\n <\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Commutronix is a highly watched startup, starting to disrupt the electric vehicle technology space. Commutronix does not manufacture vehicles. Rather they almost dominate the EV space by providing core technologies to OEMs and almost all EV manufacturers have incorporated their solutions into their product lines.<\/p>\n\n\n\n As the expectations of long range performance and superfast charging started increasing from customers, Commutronix launched a new initiative to incorporate real time analytics of vehicle performance by monitoring critical parameters and also adjust key parameters for various subsystems to achieve the goals considering the driving styles also in addition to the physical and mechanical parameters.<\/p>\n\n\n\n This was considered an ideal project for the data sciences team, as it would involve a lot of modeling, analysis and inferencing. The first thought was to have the Product Owner from the Data Sciences team,<\/p>\n\n\n\n The engineering team, however, was skeptical. They felt that there is a significant amount of work in interfacing with the sensors, the cloud based knowledge hub and the need for a driver override meant a responsive, effective UI \u2013 and so, the Product Owner must be from the engineering team.<\/p>\n\n\n\n The marketing team felt that they are in the best position to give direction to this feature, as they are closest to the customers and would know how best to prioritize and scope the requirements.<\/p>\n\n\n\n After a 3 hour discussion, the leaders had two choices before them.<\/p>\n\n\n\n One \u2013 toss a coin and decide? But how to pick from three options with a coin? Someone suggested the throw of dice..<\/p>\n\n\n\n In order to avoid another long \u2013 potentially inconclusive \u2013 meeting, they chose option two.<\/p>\n\n\n\n That is to ask you<\/strong>, what they should do.<\/p>\n\n\n\n What would be your advice?<\/p>\n\n\n\n Suggested solution:<\/p>\n\n\n\n <\/span> One question that I get regularly from most teams and organizations that I have coached in their Agility journeys, is related to choosing the persons to play the 'new' roles of scrum master of product owner.<\/p>\n\n\n\n On the face of it, such questions seem simple to answer. One could say, just refer to the documentation related to the model being adopted and pick people to fill those roles.<\/p>\n\n\n\n I wish it was as simple.<\/p>\n\n\n\n Most of the time, re-designating a person does not change the style or way of working.<\/p>\n\n\n\n In some organizations, transformation exercises list the new roles and drop some old roles [typically, those that may have a 'manager' prefix or suffix].<\/p>\n\n\n\n So, many managers want to become Scrum Masters or Product Owners.<\/p>\n\n\n\n In many such instances, the persons continue to function the way they used to, with just new titles.<\/p>\n\n\n\n In my sessions with teams, one of the important topics that I stress on is role clarity.<\/p>\n\n\n\n When we talk of Agile teams \u2013 the essential characteristics include<\/p>\n\n\n\n If the re-designated managers are not able to re-calibrate themselves to effectively enable these aspects, the tendency to continue to adopt a directive style or expect a manager-subordinate reporting relationship will continue.<\/p>\n\n\n\n These, one would appreciate, are not just anti-patterns, but are seeds for dysfunctions at a team level.<\/p>\n\n\n\n In order to become or enable teams to become high performing, what is expected of the Scrum Master role is to be a facilitator.<\/p>\n\n\n\n While one may carry a title or designation of a Manager \u2013 that could be more for organizational hierarchy and managing spans of control.<\/p>\n\n\n\n In the context of a team, there are activities to be owned and performed by all members. In that sense, a neutral title for everyone part of a team could be just 'member'.<\/p>\n\n\n\n Each person may play one or more roles. A Developer could also be a Reviewer. A tester could also be an automation programmer. A team lead could also be an architect .. and so on..<\/p>\n\n\n\n With many teams preferring to have 'full stack developers', every member would have the flexibility of playing different roles, based on the need of the hour, to meet the team goals \u2013 for an iteration or release.<\/p>\n\n\n\n Some tips to make this work well:<\/p>\n\n\n\n To summarize:<\/p>\n\n\n\n What has been your approach and experience with identifying or playing roles vis-\u00e0-vis titles?<\/p>\n\n\n\n I am eager to know<\/p>\n","post_title":"Role and Title \u2013 what is the difference?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"role-and-title-what-is-the-difference","to_ping":"","pinged":"","post_modified":"2024-01-29 11:36:36","post_modified_gmt":"2024-01-29 11:36:36","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19138","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":false,"total_page":1},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n
<\/span><\/span><\/p>\n","post_title":"Chow # 265 - Which functional organization should a Product Owner be from?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-265-which-functional-organization-should-a-product-owner-be-from","to_ping":"","pinged":"","post_modified":"2024-01-30 05:48:16","post_modified_gmt":"2024-01-30 05:48:16","post_content_filtered":"","post_parent":0,"guid":"https:\/\/pm-powerconsulting.com\/?p=19142","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":19138,"post_author":"30","post_date":"2021-09-12 15:01:47","post_date_gmt":"2021-09-12 09:31:47","post_content":"\n\n
\n
\n