Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Contributing factors<\/strong> need to be supported by data: Code Review effectiveness, requirements understanding, robust unit testing, etc. As a PM, you facilitate by asking your team questions like: \u201cWhat influences good quality deliverable in our project? What are the reasons for poor quality in the past? What can we infer from past data? What did we do right when we had delivered good quality?\u201d<\/p>\n\n\n\n Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Quality goal<\/strong> is your vision for the project. It is very powerful when connected to business goals that the team can easily relate to. Responsibility, for articulating the vision and ensuring that the team gets it, is definitely with you as the project manager.<\/p>\n\n\n\n Contributing factors<\/strong> need to be supported by data: Code Review effectiveness, requirements understanding, robust unit testing, etc. As a PM, you facilitate by asking your team questions like: \u201cWhat influences good quality deliverable in our project? What are the reasons for poor quality in the past? What can we infer from past data? What did we do right when we had delivered good quality?\u201d<\/p>\n\n\n\n Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Quality goal<\/strong> is your vision for the project. It is very powerful when connected to business goals that the team can easily relate to. Responsibility, for articulating the vision and ensuring that the team gets it, is definitely with you as the project manager.<\/p>\n\n\n\n Contributing factors<\/strong> need to be supported by data: Code Review effectiveness, requirements understanding, robust unit testing, etc. As a PM, you facilitate by asking your team questions like: \u201cWhat influences good quality deliverable in our project? What are the reasons for poor quality in the past? What can we infer from past data? What did we do right when we had delivered good quality?\u201d<\/p>\n\n\n\n Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
These are practical steps that you can apply as a Project Manager. The magic is not so much the steps by themselves but it is about how you facilitate the process for your team.<\/p>\n\n\n\n Quality goal<\/strong> is your vision for the project. It is very powerful when connected to business goals that the team can easily relate to. Responsibility, for articulating the vision and ensuring that the team gets it, is definitely with you as the project manager.<\/p>\n\n\n\n Contributing factors<\/strong> need to be supported by data: Code Review effectiveness, requirements understanding, robust unit testing, etc. As a PM, you facilitate by asking your team questions like: \u201cWhat influences good quality deliverable in our project? What are the reasons for poor quality in the past? What can we infer from past data? What did we do right when we had delivered good quality?\u201d<\/p>\n\n\n\n Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
These are practical steps that you can apply as a Project Manager. The magic is not so much the steps by themselves but it is about how you facilitate the process for your team.<\/p>\n\n\n\n Quality goal<\/strong> is your vision for the project. It is very powerful when connected to business goals that the team can easily relate to. Responsibility, for articulating the vision and ensuring that the team gets it, is definitely with you as the project manager.<\/p>\n\n\n\n Contributing factors<\/strong> need to be supported by data: Code Review effectiveness, requirements understanding, robust unit testing, etc. As a PM, you facilitate by asking your team questions like: \u201cWhat influences good quality deliverable in our project? What are the reasons for poor quality in the past? What can we infer from past data? What did we do right when we had delivered good quality?\u201d<\/p>\n\n\n\n Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
These are practical steps that you can apply as a Project Manager. The magic is not so much the steps by themselves but it is about how you facilitate the process for your team.<\/p>\n\n\n\n Quality goal<\/strong> is your vision for the project. It is very powerful when connected to business goals that the team can easily relate to. Responsibility, for articulating the vision and ensuring that the team gets it, is definitely with you as the project manager.<\/p>\n\n\n\n Contributing factors<\/strong> need to be supported by data: Code Review effectiveness, requirements understanding, robust unit testing, etc. As a PM, you facilitate by asking your team questions like: \u201cWhat influences good quality deliverable in our project? What are the reasons for poor quality in the past? What can we infer from past data? What did we do right when we had delivered good quality?\u201d<\/p>\n\n\n\n Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
These are practical steps that you can apply as a Project Manager. The magic is not so much the steps by themselves but it is about how you facilitate the process for your team.<\/p>\n\n\n\n Quality goal<\/strong> is your vision for the project. It is very powerful when connected to business goals that the team can easily relate to. Responsibility, for articulating the vision and ensuring that the team gets it, is definitely with you as the project manager.<\/p>\n\n\n\n Contributing factors<\/strong> need to be supported by data: Code Review effectiveness, requirements understanding, robust unit testing, etc. As a PM, you facilitate by asking your team questions like: \u201cWhat influences good quality deliverable in our project? What are the reasons for poor quality in the past? What can we infer from past data? What did we do right when we had delivered good quality?\u201d<\/p>\n\n\n\n Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
These are practical steps that you can apply as a Project Manager. The magic is not so much the steps by themselves but it is about how you facilitate the process for your team.<\/p>\n\n\n\n Quality goal<\/strong> is your vision for the project. It is very powerful when connected to business goals that the team can easily relate to. Responsibility, for articulating the vision and ensuring that the team gets it, is definitely with you as the project manager.<\/p>\n\n\n\n Contributing factors<\/strong> need to be supported by data: Code Review effectiveness, requirements understanding, robust unit testing, etc. As a PM, you facilitate by asking your team questions like: \u201cWhat influences good quality deliverable in our project? What are the reasons for poor quality in the past? What can we infer from past data? What did we do right when we had delivered good quality?\u201d<\/p>\n\n\n\n Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Here is an approach that may make more sense in today\u2019s software world. Before we look at the steps, a few key principles to internalize:<\/p>\n\n\n\n These are practical steps that you can apply as a Project Manager. The magic is not so much the steps by themselves but it is about how you facilitate the process for your team.<\/p>\n\n\n\n Quality goal<\/strong> is your vision for the project. It is very powerful when connected to business goals that the team can easily relate to. Responsibility, for articulating the vision and ensuring that the team gets it, is definitely with you as the project manager.<\/p>\n\n\n\n Contributing factors<\/strong> need to be supported by data: Code Review effectiveness, requirements understanding, robust unit testing, etc. As a PM, you facilitate by asking your team questions like: \u201cWhat influences good quality deliverable in our project? What are the reasons for poor quality in the past? What can we infer from past data? What did we do right when we had delivered good quality?\u201d<\/p>\n\n\n\n Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Project Managers are accountable for meeting the customer commitments and quality is undeniably one thing that no customer would compromise with. When a project encounters quality issues, the Project Manager is in the firing line. Often Project Managers feel compelled to intervene: they roll up their sleeves, try to get to the bottom of the problem, look for solutions and tell the team what to do. Well, there are times a manager may need to do that but every time one does that, the team loses a bit more of its sense of ownership. Is that what we want as Project Managers?<\/p>\n\n\n\n Here is an approach that may make more sense in today\u2019s software world. Before we look at the steps, a few key principles to internalize:<\/p>\n\n\n\n These are practical steps that you can apply as a Project Manager. The magic is not so much the steps by themselves but it is about how you facilitate the process for your team.<\/p>\n\n\n\n Quality goal<\/strong> is your vision for the project. It is very powerful when connected to business goals that the team can easily relate to. Responsibility, for articulating the vision and ensuring that the team gets it, is definitely with you as the project manager.<\/p>\n\n\n\n Contributing factors<\/strong> need to be supported by data: Code Review effectiveness, requirements understanding, robust unit testing, etc. As a PM, you facilitate by asking your team questions like: \u201cWhat influences good quality deliverable in our project? What are the reasons for poor quality in the past? What can we infer from past data? What did we do right when we had delivered good quality?\u201d<\/p>\n\n\n\n Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Seek relief from customer (schedule)<\/p>\n","post_title":"CHOW #4\u2013 What are the risks in a project managed by a first-time Project Manager?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"first-time-project-manager","to_ping":"","pinged":"","post_modified":"2024-01-24 11:59:36","post_modified_gmt":"2024-01-24 11:59:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7203","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2913,"post_author":"7","post_date":"2015-03-06 14:02:11","post_date_gmt":"2015-03-06 08:32:11","post_content":"\n Project Managers are accountable for meeting the customer commitments and quality is undeniably one thing that no customer would compromise with. When a project encounters quality issues, the Project Manager is in the firing line. Often Project Managers feel compelled to intervene: they roll up their sleeves, try to get to the bottom of the problem, look for solutions and tell the team what to do. Well, there are times a manager may need to do that but every time one does that, the team loses a bit more of its sense of ownership. Is that what we want as Project Managers?<\/p>\n\n\n\n Here is an approach that may make more sense in today\u2019s software world. Before we look at the steps, a few key principles to internalize:<\/p>\n\n\n\n These are practical steps that you can apply as a Project Manager. The magic is not so much the steps by themselves but it is about how you facilitate the process for your team.<\/p>\n\n\n\n Quality goal<\/strong> is your vision for the project. It is very powerful when connected to business goals that the team can easily relate to. Responsibility, for articulating the vision and ensuring that the team gets it, is definitely with you as the project manager.<\/p>\n\n\n\n Contributing factors<\/strong> need to be supported by data: Code Review effectiveness, requirements understanding, robust unit testing, etc. As a PM, you facilitate by asking your team questions like: \u201cWhat influences good quality deliverable in our project? What are the reasons for poor quality in the past? What can we infer from past data? What did we do right when we had delivered good quality?\u201d<\/p>\n\n\n\n Improvements<\/strong> need to be identified & prioritized by the team; Again Questions are your best tool: \u201cWhat can we do better? What should we stop doing? If I make this change in the process, how will that affect the quality of the final deliverable? Will this improvement predictably take us towards our Quality Goal? Which improvement action will have maximum influence over a quality outcome?\u201d As a PM, you can make suggestions for improvement after the team has exhausted their ideas.<\/p>\n\n\n\n Implementing the improvement actions<\/strong> is where most teams come unstuck. This step often demands change in habits and requires conviction in the team. If your team had identified the actions, they would have greater ownership and they would do it! Your role is to provide adequate resources and remove any roadblocks.<\/p>\n\n\n\n Measure the effectiveness<\/strong> of the actions in an objective manner. These metrics are your lead indicators. You know that if you move the needle on these, you can influence your Quality goal predictably. For example, if your quality goal is related to Reliability of the delivered product, improvement in Code Quality metrics during Coding phase will predictably influence the Reliability of the final product.<\/em> Please remember to facilitate identification of these measures and enable the team to measure and review them regularly. Celebrate any positive movement in these lead indicators!<\/p>\n\n\n\n Is the Quality Goal met? <\/strong>If your team does not meet the Quality goal in the first attempt, that\u2019s fine. The team would have learnt from the experience. They are now equipped and can find other ways to improve.<\/p>\n\n\n\n Always remember the principle: \u201cThe best people to improve the quality are the team members themselves\u201d. Have faith!<\/p>\n","post_title":"Improving Software Quality","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"improving-software-quality","to_ping":"","pinged":"","post_modified":"2024-01-24 12:03:00","post_modified_gmt":"2024-01-24 12:03:00","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/blogs\/?p=2913","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"}],"next":false,"prev":true,"total_page":6},"paged":1,"column_class":"jeg_col_3o3","class":"epic_block_11"};
Seek relief from customer (schedule)<\/p>\n","post_title":"CHOW #4\u2013 What are the risks in a project managed by a first-time Project Manager?","post_excerpt":"","post_status":"publish","comment_status":"open","ping_status":"open","post_password":"","post_name":"first-time-project-manager","to_ping":"","pinged":"","post_modified":"2024-01-24 11:59:36","post_modified_gmt":"2024-01-24 11:59:36","post_content_filtered":"","post_parent":0,"guid":"http:\/\/pm-powerconsulting.com\/?p=7203","menu_order":0,"post_type":"post","post_mime_type":"","comment_count":"0","filter":"raw"},{"ID":2913,"post_author":"7","post_date":"2015-03-06 14:02:11","post_date_gmt":"2015-03-06 08:32:11","post_content":"\n Project Managers are accountable for meeting the customer commitments and quality is undeniably one thing that no customer would compromise with. When a project encounters quality issues, the Project Manager is in the firing line. Often Project Managers feel compelled to intervene: they roll up their sleeves, try to get to the bottom of the problem, look for solutions and tell the team what to do. Well, there are times a manager may need to do that but every time one does that, the team loses a bit more of its sense of ownership. Is that what we want as Project Managers?<\/p>\n\n\n\n Here is an approach that may make more sense in today\u2019s software world. Before we look at the steps, a few key principles to internalize:<\/p>\n\n\n\n![\"Quality\"](\"https:\/\/pm-powerconsulting.com\/wp-content\/uploads\/2015\/03\/Quality.jpg\")
<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n<\/a><\/figure>\n\n\n\n\n
<\/a><\/figure>\n\n\n\n\n
<\/a><\/figure>\n\n\n\n\n
<\/a><\/figure>\n\n\n\n\n
<\/a><\/figure>\n\n\n\n\n
