5.04. Assign work only after taking into account appropriate contributions of education and experience tempered with a desire to further that education and experience.

 After the we accepts the project idea to do, we gather and talk about how do this this project. In the first steps we want to identify the every and each member skills. To do that we use skills vs knowledge allocation diagram. All the members marks there skills and knowledge areas. Using that diagram all the work were separated and categorized into groups like requirement gathering, system design, developing, testing and etc. It will make work easy for all of them and work will be faster as a result of that. So we assign the development activities to the people who are good at programming and requirement gathering to people who have good analytically skills.

5.01 Ensure good management for any project on which they work, including effective procedures for promotion of quality and reduction of risk. 

Before we stat the project we do some kind of activities to motivate our group members and get full attention for the project. one of thing is, give chance to team members to learn new technologies. we’re happiest when we’re learning new skills or challenging old ones. Realistic deadlines are a huge part of being set up to succeed.Building something great is fun, but it’s much more fun when someone’s. Most developers enjoy hearing praise and receiving recognition for hard work. Clear the clarified the goals and objectives well. If the team members don't have clear idea about the goals and objectives, hard to accomplish that and we give clear idea to each member team expect this kind of effort.We show all the team members respect for each other and believe what they do.