Agile development is human development
With traditional development methods, the client and IT partner are not constantly in conversation with each other. And with two branches that are so far apart, that is asking for misunderstandings. With scrum, that is different. This development method is based on the agile way of thinking. The agile manifesto describes four main ideas. Two of these four pillars clearly put the human aspect before the technical and process-related.
'People and interactions over processes and tools'
People and interactions always take priority in agile development processes. That does not mean that (fixed) processes and the tools you use to develop are unimportant. But if in practice it turns out that a process does not work for developers or end users, then you adjust that process. Because people come first. For example, you can imagine that a product owner (more on that later) is the only one who has contact with the end user. But if the developers do not understand what is needed to really help that end user, the process does not work. So you have to revise the process.
Of course, as an IT agency, you need a contract with your client. But working together with the client is much more important. Together, you look for the best solution within the agreed budget. When hospital email database problems arise, you do not point fingers at each other, but look for a solution together. In short, the IT agency and the client are in the same boat.
Human principles
In addition to the main pillars, there are also twelve principles. I would like to highlight four of these twelve principles below, because they clearly show how agile development gives IT a more human face.
1. Teams are self-organizing
It is not the manager who directs the team, but the team itself. Motivated specialists know very well how to do their work, this applies to both healthcare specialists and IT specialists. Therefore, do not give them a task, but a goal. And let them decide for themselves how to achieve that goal. In this way, you give people more responsibility and that ensures more motivation.
2. Give motivated people the confidence that the work will get done
Assume that people have intrinsic motivation to do their work well and on time. Give developers the confidence that they are building the right thing and that their work will be done quickly enough. You don't have to constantly chase them for that.