Skip to main content

Why are leaders critical in Software Development

Software development is becoming harder and harder to deliver up to customer satisfaction. We all know the Standish reports from the past. I do not need to repeat them here.

Agile development has been around for over 10 years now and waterfall, well I imagine the pyramids were built by a waterfall project plan. Projects today are hard to deliver either way. Clients want everything cheap and fast. Project managers do not like things to change. Developers want to build a space shuttle when an airplane will do. Analysis want customers to make up their mind. Product managers want everything faster. Then, there are testers, designers, server teams, DBA and best of all customers.

All of these team members have tasks to be completed to delivery a feature, iteration, release or a complete project. Managers will ask all kinds of questions about these tasks. "How much more time will that feature take?" "You are over you estimate on that ticket, why? "How many bugs were opened yesterday?"

Managers will focus on all the things these people do. Projects need a leader to focus on the people that are doing things. I feel leaders are the next evolution to software development. Leaders will ask questions like: "We seem to go over a lot of our estimates, why do you think this happens?" "Is there something or someone that is holding you up?" "What can we change this iteration that will improve our product or process?" Leaders focus on people and processes that create impacting change hopefully for the better. (Not all decisions are correct.)

Comments

Post a Comment

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.  
Post a Comment
Read more

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/
3 comments
Read more

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...
3 comments
Read more