All of us have been involved in many various software projects. There are plenty of concepts available for any sort of problems that we are facing to in software engineering. Such as methodologies, modeling, languages, patterns, architecture approaches and etc.
In most of experiences, I was trying to implement a good and standard methodology in a exactly way which is defined by minimum customization. Most of the times, I was facing to the different issues which the most outstanding one is: lack of knowledge of people (including myself). Therefore I get familiar with BSC and one of its magnificent perspectives, Learning and Growth. Hence I focused on it and I planned in a way that my team members and myself we reached to a good assimilation.
Nonetheless, we had a good knowledge and even either experienced or skilled people among my team, still I believe our performance was not that much decent. If I want to represent my complication, I need to have two layers: (a) software methodologies and (b) organization (or developers)’s culture.
I am not trying to make a new paradigm, but I believe if we provide some methodologies which first of all help to each developer to know himself better; each developer be able to do presencing, then later on carrying any software engineering will be simple.
