Posted on: May 03, 2023 12:55 AM
| 
.png)
Guessing is not a strategy: How to build decision velocity with AI and real-time data
June 10, 2026 | Live Webinar
Rethinking Project Leadership in a Dynamic World
Categories:
PMO
Categories: PMO
| Dear Friends, I’m delighted to share a glimpse from one of my recent presentations. The key message revolves around rethinking our approach to Project Management. It emphasizes the evolving role of Project Managers—not just as executors of projects, but as leaders who influence business outcomes and create lasting impact. |
Posted on: August 18, 2025 11:33 AM
| Permalink |
Comments (1)
Software Product Upgrades
Categories:
Software Products
Categories: Software Products
| Software Product Upgrade Upgrades to the Software products are a regular process and almost everyone in Software Product Development must do it. As this is a regular process and everyone must do it, then what is so important to talk about here. Software upgrades require replacing the existing running product, establishing the compatibility of existing customer data, allowing users to get into the system and helping users to continue the product without any disruption. This makes this obvious process more critical than it looks. Here are some of the tips and checklist items to ensure a smooth upgrade event: Preparations Arrange everything in the order you need for an upgrade, scripts, code, installable and release notes. Get the package signed off by QA/DevOps. Backing Up Reserve the space to back up your DB, Application, and any important information you may touch during upgrade. If you do not have privileges to customer environment, ask customer IT to perform back up of key components. Executions and Confirmation However, this is a onetime step, but I recommend executing a couple of times at local and resolving if conflicts arise. For trial, you may ask the replica of production system to validate the execution and confirmation of steps. You may want to do any migration in this step. Validating the package over production look alike environment will surface the issues you may get at the last minute. Do not bypass or overlook any minor errors. Data Integrity Run the scripts/routine to establish the integrity of data after the upgrade. However, you have a very controlled environment, while you do not want to interrupt the business at the last minute. Count the key entities pre and post upgrade. Go Live Declare the go-live if your integrity test is confirmed and shows no impact on existing data.
For most of us 2021 too was as impacting as 2020. Covid, Attrition, Delivery challenges and more! We are reaching towards an end and hope 2022 will be more eventful and brings normalcy in life and business. Closing day asked following questions to my team - Q1: What are the three achievements in the year 2021? Q2: What are the three important lessons learnt in 2021? Q3: What are the three things you want to change in yourself in 2022? Receiving feedback and happy to say some summary in new! Stay Safe.. Wish you all a very Happy New Year! Welcome 2022! Some results and trends - The present scenario developed, where every industry, business, and individual is suffering due to the Corona virus 2019 threat. Governments are doing locked downs/shutdowns. People are restricted to their homes. Offices are closed. Those who are not in the profession of saving lives are closed. We all have to support this as there is nothing important then saving lives. A tough scenario, definitely not going to be forever for sure but organizations are making sure to pass this time and trying to minimize the risk of financial impacts. Projects are at risk. Everyone is sent to work from home incurred additional challenges to companies. In this situation, forcing some challenges to organizations as given below but not limited to: The organizations, who are more to work from office culture, having challenges in coordinating, implementing and adopting the new culture work from home, however, there is no other option. Managers need to ensure to minimize these challenges using some of the basic steps from project management or PMBOK. Let’s keep to the basics of setting weekly targets, breaking them into daily and tracking religiously. Set some ground rules to have a daily stand up (for those still not Agile) and end of the day have a Daily work summary. Once you have the consolidated daily work summary spend some time reviewing the output and highlight the common issues. The common issues could be requirements, support, network or it could be the availability of resources. Set the resolution plan for issues and plan for the next day. Speak to your team daily keep them motivated to praise the good work and do not forget to give input to improve. I hope to see things better soon till then lets work towards mitigating the business risks and ensure minimal impact on deliveries. Working in Software development environment as leaders, all of us faced the issue of defects, which are Reopen by Testing and Quality teams. Why it is important to address the reopen defects? Being in Software development everyone comes across the reappearing of the defects declared fixed by the development team. It is important to address the reasons behind reopen as quickly as possible to avoid more defects appear in this category. Fixing of Reopen defects always takes extra effort and cost. It is called Rework. Reopen defects may cause: While considering the reason to address Re-open defects. One of the most important exercises, which is very essential to target reopen defects, this exercise is called a causal analysis of re-open defects. Root cause analysis gives the idea about where improvements needed while looking into possible reasons for reopening. Root cause analysis without corrective actions is a futile exercise. The below table gives a more pictorial representation of linking root causes and action items. ===================================================================================== "In youth we learn; in age we understand." - Marie von Ebner-Eschenbach |