Agile Process

In keeping with Agile best practice, Shinetech adopts short iteration development which enables continuous improvement. Requirement analysis, designing, implementing, testing are repeated during each iteration. Each project is developed incrementally. This process reduces the impact of interpretation errors and supports prompt plan adjustments based on early feedback.

The result of each iteration is a tested build which represents real progress and improved quality. It also facilitates user feedback helping to keep both client and supplier focused on the business objectives.

Shinetech has elected to major in Agile development practices, because they can immediately impact on development performance over traditional waterfall methods in 2 key areas; project process and engineering.

Process Practices

• Frequent delivery – Helpful in maintaining client and supplier engagement / commitment, ensuring transparency and revealing true progress of the project.
• Continuous integration – Helpful in early identification of build defects and measuring project quality.
• Quick demo – Helpful in verifying requirements promptly and facilitating new iterative development with the client's considered feedback.
• Empowered team members – Encourages them to do everything they can to produce the highest quality deliverables.
• Maximum business value – Agile teams with a lean mindset care more about producing software that delivers maximum business value to clients.
• Adaptable to change – Most projects experience some changes during the development process. A context-driven approach allows for necessary changes, including requirements change to meet the client's evolving business goals.
• Everyone is responsible to quality - Highest quality software and service aren't simply a result of test processes. It's the result of everyone's engaged involvement throughout the whole project period.
• 100% visibility of project process – transparency facilitates synergy; we expect our clients to become actively involved at any time they choose.
• Share project roadmap – All participants can see the impact of their individual contribution to the progress and quality of the project.

Engineering Practices

In the development process, we emphasize:

• Simple cost effective designs – Try always to avoid over-engineering when delivering to the client's business value.
• Peer to peer involvement - All team members are expected to participate and share in requirement analysis, design and other team activities.
• Anticipate non functional requirements – Deliver usability, performance, reliability, maintainability, security and scalability for evolving future requirements.