No doubts that construction needs creativity, commitment, and skills to have something that someone can use and make value of. And when it comes to constructing software we can stick to the same concepts, but unfortunately, it’s not a simple equation as it looks. As it’s observed and as some studies showed, 68% of IT projects fails! This is a very high rate, but why? What are the failure causes?
People are the first and most essential part of any software project, people design, develop, sell, and manage the digital product. Understanding this factor will play a major role in your project’s destiny. The focus of the organization or the team should take this factor as a non-negotiable precondition to any successful digital product. I’ve seen places where people are the least important factor in the organization priorities, which I believe is diseatric and big indication of short-sighted vision. But, is it really that easy to consider and handle this factor?
The challenge in working with people in software project is that humans are different than machines, if human and machine interacted there is 2 scenarios: either they agree, or one party misses something. If 2 humans interacted with each other, there’s a spectrum of possible scenarios can happen. That’s why as a part of a team, you should be more flexible and how to build the deal with different people.
Tech people need to be grouped together based on the same vision (which is part of one of the key success factors: Process) and the team needs to be visible about what’s needed and how this need will be met.
The 3 reasons for software projects failure.
According to the American computer scientist, Gerald Weinberg, there are 3 reasons for software projects failure: People, people, and people!People are the first and most essential part of any software project, people design, develop, sell, and manage the digital product. Understanding this factor will play a major role in your project’s destiny. The focus of the organization or the team should take this factor as a non-negotiable precondition to any successful digital product. I’ve seen places where people are the least important factor in the organization priorities, which I believe is diseatric and big indication of short-sighted vision. But, is it really that easy to consider and handle this factor?
Why it’s hard to work with people in software projects?
Unsurprisingly, the atmosphere is a bit more technical in software projects/organizations. People are used to work with machines, digits, facts, and most of the time a binary method of evaluating the output (it worked/it’s a bug). Here’s where the problem arises, people dynamics is a bit different here, designers and developers are (on average) curious and smart, which makes the work environment way more creative and fun, yet, challenging and sometimes hard to handle.The challenge in working with people in software project is that humans are different than machines, if human and machine interacted there is 2 scenarios: either they agree, or one party misses something. If 2 humans interacted with each other, there’s a spectrum of possible scenarios can happen. That’s why as a part of a team, you should be more flexible and how to build the deal with different people.
Tech people need to be grouped together based on the same vision (which is part of one of the key success factors: Process) and the team needs to be visible about what’s needed and how this need will be met.
Great but actually I think that before people we should build a right vision so those people can follow if there's no vision of why and how, people will not be the only issue I think the last part is the most important point you pointed out
ReplyDeleteYou're right, and this call is for business people to engage the team and put them clear about what's needed to be achieved and why.
Delete