Principle 5: MANAGEMENT

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

Following facts can be pointed out from the management perspective.

• Maintaining the proper processes for the project tasks.
• Allocate specific resources for their specialized domain.
• Following best practices throughout the project.
• Documenting to the depth as possible.
• Conduct unit testing before a committing to the repository.
• Testing under practical conditions.

5.02. Ensure that software engineers are informed of standards before being held to them.

We are agreed to follow certain standards regarding the technologies to be used from the beginning.

Successful PhoneGap conversion required specific coding patterns to be followed. We could easily learn them from the community. We tried to use the latest HTML5 components which can be replaced old ones. New features of CSS3 were really helpful to avoid scripts for certain UI modules.

All the application designs are done by following the modern mobile healthy patterns which could make the process efficient as well as extensible.

5.03. Ensure that software engineers know the employer's policies and procedures for protecting passwords, files and information that is confidential to the employer or confidential to others.

Since there are no any user authentication or session authentication, that burden is not upon so far. Android application may use credentials with the device which is managed by the android system itself.

All the other information are guaranteed to be okay to disclose with the full awareness of the whole scenario. 

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.

There are few resources in the project team and it inspire us to manage resources in a proper way. We knew from the star that we have all the technologies in the team but there were some specialties in us.

That led to divide tasks in the way of getting more effective outcome in a short time.

5.11. Not ask a software engineer to do anything inconsistent with this Code.

Developer have practiced the best ways to do their job by experience. It may cause conflicts with the other members when they are up to address the solutions in a business perspective. 

In those cases, developers are invited to use the best recognized practices for coding without any hesitation. Business process diversion can be done when the code works with its best performance.

5.12. Not punish anyone for expressing ethical concerns about a project.

Each and every member has their own perspective of looking into a problem. In that case we mentioned some sensitive issues that should solved as ethical issues.

Those are not sounded in a technical matter, but we serve them as important and every time someone emphasis something like that others are about to give the respect.