So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n
4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n
So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n
AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
\n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
anand<\/a><\/p>\n","post_title":"Reign of emotions","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"reign-of-emotions","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:10","post_modified_gmt":"2024-01-24 11:16:10","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13067","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"4","filter":"raw"},{"ID":13022,"post_author":"7","post_date":"2019-06-12 21:09:50","post_date_gmt":"2019-06-12 15:39:50","post_content":"\n Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
So what, you may ask\u2026<\/strong> This post is merely some reflections from my work life and it highlighted the importance of emotional intelligence for a successful career. I hope it brought back a few memories from your own journey. Please do share them.<\/p>\n\n\n\n anand<\/a><\/p>\n","post_title":"Reign of emotions","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"reign-of-emotions","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:10","post_modified_gmt":"2024-01-24 11:16:10","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13067","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"4","filter":"raw"},{"ID":13022,"post_author":"7","post_date":"2019-06-12 21:09:50","post_date_gmt":"2019-06-12 15:39:50","post_content":"\n Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
It was 2011. I had a lot of successes under my belt and was in\na leadership role in the organization. Yet \u2013 a sense of insignificance clouded\nmy thoughts and behaviour. I had adequate management support and resources to\ncarry out my plans but it felt like no achievement would make a difference to\nthe organization. Strangely I lived through this feeling for nearly two years\nand unsurprisingly I achieved very little. I was mentally drained at the end of\nit. I don\u2019t know if you have experienced such a phase in your career when you\njust went through the motions for a long period.<\/p>\n\n\n\n So what, you may ask\u2026<\/strong> This post is merely some reflections from my work life and it highlighted the importance of emotional intelligence for a successful career. I hope it brought back a few memories from your own journey. Please do share them.<\/p>\n\n\n\n anand<\/a><\/p>\n","post_title":"Reign of emotions","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"reign-of-emotions","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:10","post_modified_gmt":"2024-01-24 11:16:10","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13067","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"4","filter":"raw"},{"ID":13022,"post_author":"7","post_date":"2019-06-12 21:09:50","post_date_gmt":"2019-06-12 15:39:50","post_content":"\n Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Debilitating feeling\nof insignificance<\/strong><\/p>\n\n\n\n It was 2011. I had a lot of successes under my belt and was in\na leadership role in the organization. Yet \u2013 a sense of insignificance clouded\nmy thoughts and behaviour. I had adequate management support and resources to\ncarry out my plans but it felt like no achievement would make a difference to\nthe organization. Strangely I lived through this feeling for nearly two years\nand unsurprisingly I achieved very little. I was mentally drained at the end of\nit. I don\u2019t know if you have experienced such a phase in your career when you\njust went through the motions for a long period.<\/p>\n\n\n\n So what, you may ask\u2026<\/strong> This post is merely some reflections from my work life and it highlighted the importance of emotional intelligence for a successful career. I hope it brought back a few memories from your own journey. Please do share them.<\/p>\n\n\n\n anand<\/a><\/p>\n","post_title":"Reign of emotions","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"reign-of-emotions","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:10","post_modified_gmt":"2024-01-24 11:16:10","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13067","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"4","filter":"raw"},{"ID":13022,"post_author":"7","post_date":"2019-06-12 21:09:50","post_date_gmt":"2019-06-12 15:39:50","post_content":"\n Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
It was 2000. E-commerce was the craze. I was with a\nstart-up. A young, inexperienced team was assigned the task of building a\nfashion portal. The team struggled with many new technologies and concepts.\nHowever, the aura around such development outside and inside the organization\nwas big. We had a dynamic team working on the supply chain, logistics and\nmarketing. The team was excited. With three weeks to go, the team was yet to\nfigure out how to get a few key components to work. The founder announced that\nthere will be hoardings and newspaper ads promoting the portal. I still\nremember what he said: \u2018I will wake up at 5:30am on the go-live day and sit\nwith my coffee and newspaper at 6am. I will see the half-page ad in the\nnewspaper, log into the portal and order a shirt\u2019. The visual really gave the\nteam much-needed boost. Don\u2019t know how \u2013 but everything fell in place. At\n5:30am that morning, the portal went live. It was a moment to cherish.<\/p>\n\n\n\n Debilitating feeling\nof insignificance<\/strong><\/p>\n\n\n\n It was 2011. I had a lot of successes under my belt and was in\na leadership role in the organization. Yet \u2013 a sense of insignificance clouded\nmy thoughts and behaviour. I had adequate management support and resources to\ncarry out my plans but it felt like no achievement would make a difference to\nthe organization. Strangely I lived through this feeling for nearly two years\nand unsurprisingly I achieved very little. I was mentally drained at the end of\nit. I don\u2019t know if you have experienced such a phase in your career when you\njust went through the motions for a long period.<\/p>\n\n\n\n So what, you may ask\u2026<\/strong> This post is merely some reflections from my work life and it highlighted the importance of emotional intelligence for a successful career. I hope it brought back a few memories from your own journey. Please do share them.<\/p>\n\n\n\n anand<\/a><\/p>\n","post_title":"Reign of emotions","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"reign-of-emotions","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:10","post_modified_gmt":"2024-01-24 11:16:10","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13067","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"4","filter":"raw"},{"ID":13022,"post_author":"7","post_date":"2019-06-12 21:09:50","post_date_gmt":"2019-06-12 15:39:50","post_content":"\n Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Wonders of passion<\/strong><\/p>\n\n\n\n It was 2000. E-commerce was the craze. I was with a\nstart-up. A young, inexperienced team was assigned the task of building a\nfashion portal. The team struggled with many new technologies and concepts.\nHowever, the aura around such development outside and inside the organization\nwas big. We had a dynamic team working on the supply chain, logistics and\nmarketing. The team was excited. With three weeks to go, the team was yet to\nfigure out how to get a few key components to work. The founder announced that\nthere will be hoardings and newspaper ads promoting the portal. I still\nremember what he said: \u2018I will wake up at 5:30am on the go-live day and sit\nwith my coffee and newspaper at 6am. I will see the half-page ad in the\nnewspaper, log into the portal and order a shirt\u2019. The visual really gave the\nteam much-needed boost. Don\u2019t know how \u2013 but everything fell in place. At\n5:30am that morning, the portal went live. It was a moment to cherish.<\/p>\n\n\n\n Debilitating feeling\nof insignificance<\/strong><\/p>\n\n\n\n It was 2011. I had a lot of successes under my belt and was in\na leadership role in the organization. Yet \u2013 a sense of insignificance clouded\nmy thoughts and behaviour. I had adequate management support and resources to\ncarry out my plans but it felt like no achievement would make a difference to\nthe organization. Strangely I lived through this feeling for nearly two years\nand unsurprisingly I achieved very little. I was mentally drained at the end of\nit. I don\u2019t know if you have experienced such a phase in your career when you\njust went through the motions for a long period.<\/p>\n\n\n\n So what, you may ask\u2026<\/strong> This post is merely some reflections from my work life and it highlighted the importance of emotional intelligence for a successful career. I hope it brought back a few memories from your own journey. Please do share them.<\/p>\n\n\n\n anand<\/a><\/p>\n","post_title":"Reign of emotions","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"reign-of-emotions","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:10","post_modified_gmt":"2024-01-24 11:16:10","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13067","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"4","filter":"raw"},{"ID":13022,"post_author":"7","post_date":"2019-06-12 21:09:50","post_date_gmt":"2019-06-12 15:39:50","post_content":"\n Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
It was 1992. I was in Australia working as a lead for a high\nprofile development project. I had joined the organization recently. I decided\nto start with a meeting with a senior director in the user organization. After\n30 minutes, I left the meeting in a state of daze \u2013 not knowing what\ntranspired. I guess I did not know how\nto interact with a senior leader \u2013 more so in a foreign culture. Next morning I\ngot some \u2018feedback\u2019 from my manager \u2013 there was a clear vote of no confidence\nin my ability! Fortunately, my manager decided to keep me on the project but\nthe seed of doubt had been sown. Doubt plagued me for the next one year \u2013 I\navoided interactions with this director and stayed focused on meeting the\nexpectations of the managers in the user group. It took almost two years for\nthe senior director to acknowledge my ability. Here is what I learnt \u2013 \u2018when in\ndoubt, get on with work!\u2019.<\/p>\n\n\n\n Wonders of passion<\/strong><\/p>\n\n\n\n It was 2000. E-commerce was the craze. I was with a\nstart-up. A young, inexperienced team was assigned the task of building a\nfashion portal. The team struggled with many new technologies and concepts.\nHowever, the aura around such development outside and inside the organization\nwas big. We had a dynamic team working on the supply chain, logistics and\nmarketing. The team was excited. With three weeks to go, the team was yet to\nfigure out how to get a few key components to work. The founder announced that\nthere will be hoardings and newspaper ads promoting the portal. I still\nremember what he said: \u2018I will wake up at 5:30am on the go-live day and sit\nwith my coffee and newspaper at 6am. I will see the half-page ad in the\nnewspaper, log into the portal and order a shirt\u2019. The visual really gave the\nteam much-needed boost. Don\u2019t know how \u2013 but everything fell in place. At\n5:30am that morning, the portal went live. It was a moment to cherish.<\/p>\n\n\n\n Debilitating feeling\nof insignificance<\/strong><\/p>\n\n\n\n It was 2011. I had a lot of successes under my belt and was in\na leadership role in the organization. Yet \u2013 a sense of insignificance clouded\nmy thoughts and behaviour. I had adequate management support and resources to\ncarry out my plans but it felt like no achievement would make a difference to\nthe organization. Strangely I lived through this feeling for nearly two years\nand unsurprisingly I achieved very little. I was mentally drained at the end of\nit. I don\u2019t know if you have experienced such a phase in your career when you\njust went through the motions for a long period.<\/p>\n\n\n\n So what, you may ask\u2026<\/strong> This post is merely some reflections from my work life and it highlighted the importance of emotional intelligence for a successful career. I hope it brought back a few memories from your own journey. Please do share them.<\/p>\n\n\n\n anand<\/a><\/p>\n","post_title":"Reign of emotions","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"reign-of-emotions","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:10","post_modified_gmt":"2024-01-24 11:16:10","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13067","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"4","filter":"raw"},{"ID":13022,"post_author":"7","post_date":"2019-06-12 21:09:50","post_date_gmt":"2019-06-12 15:39:50","post_content":"\n Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Seed of doubt<\/strong><\/p>\n\n\n\n It was 1992. I was in Australia working as a lead for a high\nprofile development project. I had joined the organization recently. I decided\nto start with a meeting with a senior director in the user organization. After\n30 minutes, I left the meeting in a state of daze \u2013 not knowing what\ntranspired. I guess I did not know how\nto interact with a senior leader \u2013 more so in a foreign culture. Next morning I\ngot some \u2018feedback\u2019 from my manager \u2013 there was a clear vote of no confidence\nin my ability! Fortunately, my manager decided to keep me on the project but\nthe seed of doubt had been sown. Doubt plagued me for the next one year \u2013 I\navoided interactions with this director and stayed focused on meeting the\nexpectations of the managers in the user group. It took almost two years for\nthe senior director to acknowledge my ability. Here is what I learnt \u2013 \u2018when in\ndoubt, get on with work!\u2019.<\/p>\n\n\n\n Wonders of passion<\/strong><\/p>\n\n\n\n It was 2000. E-commerce was the craze. I was with a\nstart-up. A young, inexperienced team was assigned the task of building a\nfashion portal. The team struggled with many new technologies and concepts.\nHowever, the aura around such development outside and inside the organization\nwas big. We had a dynamic team working on the supply chain, logistics and\nmarketing. The team was excited. With three weeks to go, the team was yet to\nfigure out how to get a few key components to work. The founder announced that\nthere will be hoardings and newspaper ads promoting the portal. I still\nremember what he said: \u2018I will wake up at 5:30am on the go-live day and sit\nwith my coffee and newspaper at 6am. I will see the half-page ad in the\nnewspaper, log into the portal and order a shirt\u2019. The visual really gave the\nteam much-needed boost. Don\u2019t know how \u2013 but everything fell in place. At\n5:30am that morning, the portal went live. It was a moment to cherish.<\/p>\n\n\n\n Debilitating feeling\nof insignificance<\/strong><\/p>\n\n\n\n It was 2011. I had a lot of successes under my belt and was in\na leadership role in the organization. Yet \u2013 a sense of insignificance clouded\nmy thoughts and behaviour. I had adequate management support and resources to\ncarry out my plans but it felt like no achievement would make a difference to\nthe organization. Strangely I lived through this feeling for nearly two years\nand unsurprisingly I achieved very little. I was mentally drained at the end of\nit. I don\u2019t know if you have experienced such a phase in your career when you\njust went through the motions for a long period.<\/p>\n\n\n\n So what, you may ask\u2026<\/strong> This post is merely some reflections from my work life and it highlighted the importance of emotional intelligence for a successful career. I hope it brought back a few memories from your own journey. Please do share them.<\/p>\n\n\n\n anand<\/a><\/p>\n","post_title":"Reign of emotions","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"reign-of-emotions","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:10","post_modified_gmt":"2024-01-24 11:16:10","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13067","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"4","filter":"raw"},{"ID":13022,"post_author":"7","post_date":"2019-06-12 21:09:50","post_date_gmt":"2019-06-12 15:39:50","post_content":"\n Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
It was 1984. Every now and then, I would notice managers\nwith a \u2018terror image\u2019. There was an operations manager who every operator\nfeared. As part of my production support role, I asked one of the computer\noperators to change a standard instruction given by the \u2018terror\u2019 manager.\nAlthough he did what I asked him to do, he warned me that there would be\nconsequences if the feared manager found out. For the next 10 days, I did not\nsleep properly \u2013 just the possibility of getting fired by this \u2018terror\u2019 was too\nmuch to cope. In hindsight, I realised that my fear was completely unfounded\nalthough very real. I wonder if you have gone through such situations.<\/p>\n\n\n\n Seed of doubt<\/strong><\/p>\n\n\n\n It was 1992. I was in Australia working as a lead for a high\nprofile development project. I had joined the organization recently. I decided\nto start with a meeting with a senior director in the user organization. After\n30 minutes, I left the meeting in a state of daze \u2013 not knowing what\ntranspired. I guess I did not know how\nto interact with a senior leader \u2013 more so in a foreign culture. Next morning I\ngot some \u2018feedback\u2019 from my manager \u2013 there was a clear vote of no confidence\nin my ability! Fortunately, my manager decided to keep me on the project but\nthe seed of doubt had been sown. Doubt plagued me for the next one year \u2013 I\navoided interactions with this director and stayed focused on meeting the\nexpectations of the managers in the user group. It took almost two years for\nthe senior director to acknowledge my ability. Here is what I learnt \u2013 \u2018when in\ndoubt, get on with work!\u2019.<\/p>\n\n\n\n Wonders of passion<\/strong><\/p>\n\n\n\n It was 2000. E-commerce was the craze. I was with a\nstart-up. A young, inexperienced team was assigned the task of building a\nfashion portal. The team struggled with many new technologies and concepts.\nHowever, the aura around such development outside and inside the organization\nwas big. We had a dynamic team working on the supply chain, logistics and\nmarketing. The team was excited. With three weeks to go, the team was yet to\nfigure out how to get a few key components to work. The founder announced that\nthere will be hoardings and newspaper ads promoting the portal. I still\nremember what he said: \u2018I will wake up at 5:30am on the go-live day and sit\nwith my coffee and newspaper at 6am. I will see the half-page ad in the\nnewspaper, log into the portal and order a shirt\u2019. The visual really gave the\nteam much-needed boost. Don\u2019t know how \u2013 but everything fell in place. At\n5:30am that morning, the portal went live. It was a moment to cherish.<\/p>\n\n\n\n Debilitating feeling\nof insignificance<\/strong><\/p>\n\n\n\n It was 2011. I had a lot of successes under my belt and was in\na leadership role in the organization. Yet \u2013 a sense of insignificance clouded\nmy thoughts and behaviour. I had adequate management support and resources to\ncarry out my plans but it felt like no achievement would make a difference to\nthe organization. Strangely I lived through this feeling for nearly two years\nand unsurprisingly I achieved very little. I was mentally drained at the end of\nit. I don\u2019t know if you have experienced such a phase in your career when you\njust went through the motions for a long period.<\/p>\n\n\n\n So what, you may ask\u2026<\/strong> This post is merely some reflections from my work life and it highlighted the importance of emotional intelligence for a successful career. I hope it brought back a few memories from your own journey. Please do share them.<\/p>\n\n\n\n anand<\/a><\/p>\n","post_title":"Reign of emotions","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"reign-of-emotions","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:10","post_modified_gmt":"2024-01-24 11:16:10","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13067","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"4","filter":"raw"},{"ID":13022,"post_author":"7","post_date":"2019-06-12 21:09:50","post_date_gmt":"2019-06-12 15:39:50","post_content":"\n Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Unfounded fear<\/strong><\/p>\n\n\n\n It was 1984. Every now and then, I would notice managers\nwith a \u2018terror image\u2019. There was an operations manager who every operator\nfeared. As part of my production support role, I asked one of the computer\noperators to change a standard instruction given by the \u2018terror\u2019 manager.\nAlthough he did what I asked him to do, he warned me that there would be\nconsequences if the feared manager found out. For the next 10 days, I did not\nsleep properly \u2013 just the possibility of getting fired by this \u2018terror\u2019 was too\nmuch to cope. In hindsight, I realised that my fear was completely unfounded\nalthough very real. I wonder if you have gone through such situations.<\/p>\n\n\n\n Seed of doubt<\/strong><\/p>\n\n\n\n It was 1992. I was in Australia working as a lead for a high\nprofile development project. I had joined the organization recently. I decided\nto start with a meeting with a senior director in the user organization. After\n30 minutes, I left the meeting in a state of daze \u2013 not knowing what\ntranspired. I guess I did not know how\nto interact with a senior leader \u2013 more so in a foreign culture. Next morning I\ngot some \u2018feedback\u2019 from my manager \u2013 there was a clear vote of no confidence\nin my ability! Fortunately, my manager decided to keep me on the project but\nthe seed of doubt had been sown. Doubt plagued me for the next one year \u2013 I\navoided interactions with this director and stayed focused on meeting the\nexpectations of the managers in the user group. It took almost two years for\nthe senior director to acknowledge my ability. Here is what I learnt \u2013 \u2018when in\ndoubt, get on with work!\u2019.<\/p>\n\n\n\n Wonders of passion<\/strong><\/p>\n\n\n\n It was 2000. E-commerce was the craze. I was with a\nstart-up. A young, inexperienced team was assigned the task of building a\nfashion portal. The team struggled with many new technologies and concepts.\nHowever, the aura around such development outside and inside the organization\nwas big. We had a dynamic team working on the supply chain, logistics and\nmarketing. The team was excited. With three weeks to go, the team was yet to\nfigure out how to get a few key components to work. The founder announced that\nthere will be hoardings and newspaper ads promoting the portal. I still\nremember what he said: \u2018I will wake up at 5:30am on the go-live day and sit\nwith my coffee and newspaper at 6am. I will see the half-page ad in the\nnewspaper, log into the portal and order a shirt\u2019. The visual really gave the\nteam much-needed boost. Don\u2019t know how \u2013 but everything fell in place. At\n5:30am that morning, the portal went live. It was a moment to cherish.<\/p>\n\n\n\n Debilitating feeling\nof insignificance<\/strong><\/p>\n\n\n\n It was 2011. I had a lot of successes under my belt and was in\na leadership role in the organization. Yet \u2013 a sense of insignificance clouded\nmy thoughts and behaviour. I had adequate management support and resources to\ncarry out my plans but it felt like no achievement would make a difference to\nthe organization. Strangely I lived through this feeling for nearly two years\nand unsurprisingly I achieved very little. I was mentally drained at the end of\nit. I don\u2019t know if you have experienced such a phase in your career when you\njust went through the motions for a long period.<\/p>\n\n\n\n So what, you may ask\u2026<\/strong> This post is merely some reflections from my work life and it highlighted the importance of emotional intelligence for a successful career. I hope it brought back a few memories from your own journey. Please do share them.<\/p>\n\n\n\n anand<\/a><\/p>\n","post_title":"Reign of emotions","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"reign-of-emotions","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:10","post_modified_gmt":"2024-01-24 11:16:10","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13067","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"4","filter":"raw"},{"ID":13022,"post_author":"7","post_date":"2019-06-12 21:09:50","post_date_gmt":"2019-06-12 15:39:50","post_content":"\n Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
It was 1981. Right at the start of my career as a trainee\nprogrammer, I found myself in the middle of this turbulent project in a\nmanufacturing organization. After four months into software development, there\nwas very little progress and accusations were flying in all directions. The CIO\ncalled for a special session to \u2018chat\u2019 with the team, the lead and the manager.\nAs a wide-eyed fresher, I could not believe how the meeting was proceeding.\nThere was a veil of calm and everyone was very impersonal. After listening for\n30 minutes, I just blurted out \u201ceveryone is a good person but they do not seem\nto trust each other. They are always complaining about each other\u2019s work\u201d. The CIO looked at me appreciatively and looked\naround the room seeking an explanation \u2013 veil lifted and floodgates opened.\nAfter 15 minutes of productive un-calmness, a few useful improvement actions\nwere identified. After the meeting, I thought \u2018a veil is a veil, good or bad,\nbut it needs to be lifted\u2019.<\/p>\n\n\n\n Unfounded fear<\/strong><\/p>\n\n\n\n It was 1984. Every now and then, I would notice managers\nwith a \u2018terror image\u2019. There was an operations manager who every operator\nfeared. As part of my production support role, I asked one of the computer\noperators to change a standard instruction given by the \u2018terror\u2019 manager.\nAlthough he did what I asked him to do, he warned me that there would be\nconsequences if the feared manager found out. For the next 10 days, I did not\nsleep properly \u2013 just the possibility of getting fired by this \u2018terror\u2019 was too\nmuch to cope. In hindsight, I realised that my fear was completely unfounded\nalthough very real. I wonder if you have gone through such situations.<\/p>\n\n\n\n Seed of doubt<\/strong><\/p>\n\n\n\n It was 1992. I was in Australia working as a lead for a high\nprofile development project. I had joined the organization recently. I decided\nto start with a meeting with a senior director in the user organization. After\n30 minutes, I left the meeting in a state of daze \u2013 not knowing what\ntranspired. I guess I did not know how\nto interact with a senior leader \u2013 more so in a foreign culture. Next morning I\ngot some \u2018feedback\u2019 from my manager \u2013 there was a clear vote of no confidence\nin my ability! Fortunately, my manager decided to keep me on the project but\nthe seed of doubt had been sown. Doubt plagued me for the next one year \u2013 I\navoided interactions with this director and stayed focused on meeting the\nexpectations of the managers in the user group. It took almost two years for\nthe senior director to acknowledge my ability. Here is what I learnt \u2013 \u2018when in\ndoubt, get on with work!\u2019.<\/p>\n\n\n\n Wonders of passion<\/strong><\/p>\n\n\n\n It was 2000. E-commerce was the craze. I was with a\nstart-up. A young, inexperienced team was assigned the task of building a\nfashion portal. The team struggled with many new technologies and concepts.\nHowever, the aura around such development outside and inside the organization\nwas big. We had a dynamic team working on the supply chain, logistics and\nmarketing. The team was excited. With three weeks to go, the team was yet to\nfigure out how to get a few key components to work. The founder announced that\nthere will be hoardings and newspaper ads promoting the portal. I still\nremember what he said: \u2018I will wake up at 5:30am on the go-live day and sit\nwith my coffee and newspaper at 6am. I will see the half-page ad in the\nnewspaper, log into the portal and order a shirt\u2019. The visual really gave the\nteam much-needed boost. Don\u2019t know how \u2013 but everything fell in place. At\n5:30am that morning, the portal went live. It was a moment to cherish.<\/p>\n\n\n\n Debilitating feeling\nof insignificance<\/strong><\/p>\n\n\n\n It was 2011. I had a lot of successes under my belt and was in\na leadership role in the organization. Yet \u2013 a sense of insignificance clouded\nmy thoughts and behaviour. I had adequate management support and resources to\ncarry out my plans but it felt like no achievement would make a difference to\nthe organization. Strangely I lived through this feeling for nearly two years\nand unsurprisingly I achieved very little. I was mentally drained at the end of\nit. I don\u2019t know if you have experienced such a phase in your career when you\njust went through the motions for a long period.<\/p>\n\n\n\n So what, you may ask\u2026<\/strong> This post is merely some reflections from my work life and it highlighted the importance of emotional intelligence for a successful career. I hope it brought back a few memories from your own journey. Please do share them.<\/p>\n\n\n\n anand<\/a><\/p>\n","post_title":"Reign of emotions","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"reign-of-emotions","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:10","post_modified_gmt":"2024-01-24 11:16:10","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13067","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"4","filter":"raw"},{"ID":13022,"post_author":"7","post_date":"2019-06-12 21:09:50","post_date_gmt":"2019-06-12 15:39:50","post_content":"\n Mancini is a Product Owner. Based on the average velocity of the previous release (13 units of work), he estimated a new release of the product to take 7 Sprints. Development is 3 Sprints underway. Product Backlog has been stable. Over these first Sprints, the Development Team reported an average velocity of 9, although not all functionality was fully tested. The Development Team estimates that the missing testing would have required 10% more time. Mancini considers the current functionality cohesive enough for her users and wants to release. What is the most effective way to proceed?<\/p>\n\n\n\n Suggested solution:<\/strong><\/p>\n\n\n\n Since the functionality is not fully tested, it is\nincomplete and not done. Since it is not done, it lacks feedback, transparency,\nempiricism and is not releasable.<\/p>\n\n\n\n The Scrum Master(SM) should enable the Development Team(DT)\nto come up with a clear Definition Of Done as it helps the Development\nTeam(DT), Product Owner(PO) and the stakeholders to :<\/p>\n\n\n\n \n\n\n\n With this\nthe PO , can be very clear on what is the quality level that he can expect from\nthe Development Team and then can take an informed decision on the release - if\nthe functionality is potentially releasable and adheres to the Scrum Team\u2019s\nDefinition Of Done.\n\n\n\n<\/p>\n","post_title":"Chow #152 - Are you done?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-152-are-you-done","to_ping":"","pinged":"","post_modified":"2024-01-24 11:16:28","post_modified_gmt":"2024-01-24 11:16:28","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=13022","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":12831,"post_author":"7","post_date":"2019-04-17 15:44:46","post_date_gmt":"2019-04-17 10:14:46","post_content":"\n Agilators is a team using Scrum for about six months now and Alan is the Scrum Master of the team. Alan has some experience as an SM for a little over a year. He has been able to coach the team to adopt the ceremonies quite well but few challenges which he finds difficult to handle. First of all the team is not able to complete stories for a large part of the Sprint and they keep adding tasks to stories during the Sprint which is affecting their estimation. Many stories are being picked at a time and wait time for a story is also getting a bit longer. He is trying several things every Sprint but has not found much improvement in the last quarter and is looking for some expert help. Can you help Alan?<\/p>\n\n\n\n Suggested Solution:<\/strong><\/p>\n\n\n\n Obviously Alan is picking too many areas to\nwork on at a time. Based on the challenges it looks like team is struggling in\nsome of the following areas:<\/p>\n\n\n\n 1. Stories are not small and unknown\ncomponent seems to be more in stories<\/p>\n\n\n\n 2. Planning may not be efficient and team\nmay be picking too many big items and estimating. Hence their understanding of\nthe stories and estimations might need improvement.<\/p>\n\n\n\n 3. Product Owner not focusing on writing\nstories as per INVEST guidelines.<\/p>\n\n\n\n 4. Collaboration within team while planning\nand developing stories might need to improve as wait time seems to be longer\nacross tasks of a story.<\/p>\n\n\n\n So Alan is keen on working on several of\nthese aspects at the same time and not able to make the team focus on\nimprovements in any area. It would be good if Alan can use the simplicity\nPrinciple and pick few priority items of work and further try to implement them\nin phases over few Sprints. For eg. INVEST of stories \u2013 focus on just writing\nthe story well with good clarity and acceptance criteria etc and making them\nsmaller. Pick few big stories and try these to start with and then focus on\nother aspects of INVEST, maybe one by one. Use the same principle in other\nareas as well.\n\nThis is just a tip and Alan needs to spend time\nand plan carefully to approach improvements in small steps.\n\n\n\n<\/p>\n\n\n\n AN<\/a><\/p>\n","post_title":"Chow #144 - Too many incomplete stories!","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"chow-144-too-many-incomplete-stories","to_ping":"","pinged":"","post_modified":"2024-01-24 11:18:36","post_modified_gmt":"2024-01-24 11:18:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=12831","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":3},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Veil of calm<\/strong><\/p>\n\n\n\n It was 1981. Right at the start of my career as a trainee\nprogrammer, I found myself in the middle of this turbulent project in a\nmanufacturing organization. After four months into software development, there\nwas very little progress and accusations were flying in all directions. The CIO\ncalled for a special session to \u2018chat\u2019 with the team, the lead and the manager.\nAs a wide-eyed fresher, I could not believe how the meeting was proceeding.\nThere was a veil of calm and everyone was very impersonal. After listening for\n30 minutes, I just blurted out \u201ceveryone is a good person but they do not seem\nto trust each other. They are always complaining about each other\u2019s work\u201d. The CIO looked at me appreciatively and looked\naround the room seeking an explanation \u2013 veil lifted and floodgates opened.\nAfter 15 minutes of productive un-calmness, a few useful improvement actions\nwere identified. After the meeting, I thought \u2018a veil is a veil, good or bad,\nbut it needs to be lifted\u2019.<\/p>\n\n\n\n Unfounded fear<\/strong><\/p>\n\n\n\n It was 1984. Every now and then, I would notice managers\nwith a \u2018terror image\u2019. There was an operations manager who every operator\nfeared. As part of my production support role, I asked one of the computer\noperators to change a standard instruction given by the \u2018terror\u2019 manager.\nAlthough he did what I asked him to do, he warned me that there would be\nconsequences if the feared manager found out. For the next 10 days, I did not\nsleep properly \u2013 just the possibility of getting fired by this \u2018terror\u2019 was too\nmuch to cope. In hindsight, I realised that my fear was completely unfounded\nalthough very real. I wonder if you have gone through such situations.<\/p>\n\n\n\n Seed of doubt<\/strong><\/p>\n\n\n\n It was 1992. I was in Australia working as a lead for a high\nprofile development project. I had joined the organization recently. I decided\nto start with a meeting with a senior director in the user organization. After\n30 minutes, I left the meeting in a state of daze \u2013 not knowing what\ntranspired. I guess I did not know how\nto interact with a senior leader \u2013 more so in a foreign culture. Next morning I\ngot some \u2018feedback\u2019 from my manager \u2013 there was a clear vote of no confidence\nin my ability! Fortunately, my manager decided to keep me on the project but\nthe seed of doubt had been sown. Doubt plagued me for the next one year \u2013 I\navoided interactions with this director and stayed focused on meeting the\nexpectations of the managers in the user group. It took almost two years for\nthe senior director to acknowledge my ability. Here is what I learnt \u2013 \u2018when in\ndoubt, get on with work!\u2019.<\/p>\n\n\n\n Wonders of passion<\/strong><\/p>\n\n\n\n It was 2000. E-commerce was the craze. I was with a\nstart-up. A young, inexperienced team was assigned the task of building a\nfashion portal. The team struggled with many new technologies and concepts.\nHowever, the aura around such development outside and inside the organization\nwas big. We had a dynamic team working on the supply chain, logistics and\nmarketing. The team was excited. With three weeks to go, the team was yet to\nfigure out how to get a few key components to work. The founder announced that\nthere will be hoardings and newspaper ads promoting the portal. I still\nremember what he said: \u2018I will wake up at 5:30am on the go-live day and sit\nwith my coffee and newspaper at 6am. I will see the half-page ad in the\nnewspaper, log into the portal and order a shirt\u2019. The visual really gave the\nteam much-needed boost. Don\u2019t know how \u2013 but everything fell in place. At\n5:30am that morning, the portal went live. It was a moment to cherish.<\/p>\n\n\n\n Debilitating feeling\nof insignificance<\/strong><\/p>\n\n\n\n It was 2011. I had a lot of successes under my belt and was in\na leadership role in the organization. Yet \u2013 a sense of insignificance clouded\nmy thoughts and behaviour. I had adequate management support and resources to\ncarry out my plans but it felt like no achievement would make a difference to\nthe organization. Strangely I lived through this feeling for nearly two years\nand unsurprisingly I achieved very little. I was mentally drained at the end of\nit. I don\u2019t know if you have experienced such a phase in your career when you\njust went through the motions for a long period.<\/p>\n\n\n\n
