agile - Building PHP Competencies in an organization -
This is not really a technical programming question, but it is more with best practices and programming / project management processes. Here are some background information:
I am a consultant with an agile software development company which specializes in Java, J2EE, Flex Technology Stack.
Here generally it is believed that many people are not marked with the quality of PHP people, compared to Java, etc. compared to projects. When I often face that claim, I believe that there is an overall constraint to enter PHP, which sometimes attracts low-quality people who do low-quality jobs.
For us, the quality comes first. During the next few quarters we are also looking to develop a high level of qualification in PHP. And we want to achieve the highest level of quality and our process should be such that we are continuously improving all the time while starting at a higher level.
Our new recruiter is going through a rigorous selection process where technical assignments have a lot of hands. We evaluate how they do code, how we evaluate them, how they test their code. We do, we evaluate our skills with the industry's standard framework (Zend, KPHP, Code Igniter / Koha, Symphony).
We have a two-monthly (two-month-month) knowledge exchange program where individuals are encouraged to present. We have hands on events too.
I request you to share your experiences, how can we develop good PHP development methods as individuals and a flat, tight, relatively small organization and continuously improve ourselves You can. / P>
Thank you, Mr.
The best way to get better is to ensure that you Only people want to rent better then you should support those people when they make a mistake in looking for better. In this way they are not afraid to try new things.
It has been said that I have heard in the United States: "Fare people with GPA less than 3.9 (out of 4.0)"; Which shows the goal of appointing those who have not done completely (i.e., they have learned how to not be correct).
One of the best ways to become better is the "lean" mentality, which led to playful methods, as well as a significant success story in the manufacturing sector.
The general idea is to consistently involve itself in the repetition process of evaluation and is never wasting resources or interrupting its workflow. Obviously, care needs to be treated with: Research projects are so ill defined that they can not be put in almost an assembly line, and software development is research.
For a language, your developers need to be aware of the latest security questions, their establishments need to be kept up to date by IT staff, the company should play some learning material, they Curriculum, books, conferences, or what-you
In general, the broad idea is that quality is the business of all, and it is OK to take the time to correct it .
Comments
Post a Comment