Skip to main content

Corona Virus Thoughts and Leadership

This is really week one of the US being impacted by Corona Virus.  3/16.  Many schools, churches and business are closed and many others are work remote.  All sports are on hold.

There are two categories of people speaking out. 
1. What is the big deal?
2. We need to shut everything down.

I am not going to rant on either one of these because generally the right spot is somewhere in the middle.

As leaders we should see were things are going and be ahead of the curve for our people.  Last week it was clear that things were about to get worse.  Many people are returning from business trips and vacations.  The community spread was going to start.

This was an opportunity for leaders to show people they matter with out increasing fear.

Leaders should be communicating how this virus is affecting or going to affect the business.

Those that could work from home should been made to go virtual. This was a simple step to show you are important and we trust you to do good work.

As new information came out, they should be adapting and creating plans that show they are thinking ahead of what others are doing but also seeing what similar industries are doing and following them too.

Small business and service industry are going to be impacted the most.  I already know companies that have done layoffs.  This is very unfortunate and I hope the business is prepared to help those people that can't continue to work. 

The key points are stay in tune with your people, be ahead of the curve and communicate to your people, even if it is bad news.

Comments

Popular posts from this blog

2020 State of DevSecOps by Accurics

 This is an excellent report for all IT Pros and Engineers.   Highlights: Storage is most impacted solution Open security groups or network configuration Secrets are not so secret Unused resources are not secure. Take a look at these.  Look again.  These are not highly skilled problems.  They just need guidelines and proactive management.  The article uses policy as code as a solution for many of the problems.  I will drill into each of these more in the future.  I wanted to get the awareness out first and then, come back to solutions.  

Manage IT by Johanna Rothman

I just completed this book. I think it is a really good book which covers a whole lot of software development. This book could possibly be the best book for first time project managers. I believe many of the PMs understand PMM but do not understand software development. This book gives a view of each project role. The only one that it does not cover is Business Analyst or requirements documentation. It does cover QC, development and of course PMs. It gives a PM a view into development processes like TDD, CI and estimation. Many PMs that are new to SD can read this book and get a great start to manager an SD project. If you are a PM or know some, read this book. http://www.jrothman.com/

Matrix Organizations are bad for Software Dev

Development teams need to be teams first and company people second. What happens when your team wants to start using user stories and index cards, but your analyst team manager thinks Use Cases are the best way to document requirements? How about when your QA process is not mature and you keep releasing with defects but the QA manager does not do anything about it? How about your project manager never buys into the team and only cares about being on time and on budget because their review is based on it. Maybe the tech lead wants requirements that never change and never lets the client change their mind. The technical manager taught your tech lead and agrees with everything the tech lead says. Agile or what I like to call "Successful Teams" are teams. They do what it takes to do what the customer wants, deliver features. I am not saying only agile teams are successful but successful teams are agile. If your organization is matrix, get your leadership buy in to override...