Update

Merce is now Remiges

From being a vendor to a partner to a collaborator to a symbiotic part of growth - Merce has grown to Remiges. With Product Engineering, Modern Applications, Cloud-first Business Applications & Modern Databases - Merce has modernised, grown and upgraded.

23rd Aug '23

STP: Standards, Tools & Processes

Processes set standards. Tools help maintain those standards. Standards build reputation. Reputation attracts talent. Talent build projects. Projects need processes. We are focused on building all to eliminate friction and maximise productivity.

Technical

Reinventing the processes and standards which we follow to deliver maintainable, clean code.
  • Code analysis tools and coding standards: adopt static code analysers and linters as our standard across all teams.

  • Automated build and deploy stack for reliable deployment in UAT and production environments.

  • Automated testing, with test suites integrated with the build and deploy toolchain.

  • Code reviews: manual (peer reviews) and automated (static code analysers

  • Documentation: technical and functional: kept on our project management system’s wiki, updated continuously whenever specs change

  • Repository: use Git, standardise on a branch-merge process, and integrate into our release management workflow.

Governance

Adopting well designed project management practices to maximize the productivity and efficiency of the team.

The Project Manager focuses on various aspects like:

  • What are the project's deliverables?

  • What is the ultimate objective of the project which will benefit the client?

  • How do you define "success" for the project?

  • Better understanding of contracts

  • Are there any risks & issues to be aware of?

  • What are the project budget, time, and performance constraints?

  • What governance (communication) processes are to be used by the team and with the client?

  • Are we in a position to offer advanced solutions and expand our business?

Product Engineering

Product engg builds on good development standands and processes to take the game to the next level:

  • Build configurability into the system to such an extent that it can practically do yoga back-bends without code change, just by setting the right parameters

  • Build support for the widest variety of users and organisations who will use it, and will want to tweak business rules, workflow, etc, to their own needs

  • Allow UI to change by replacing one set of files with another, without any code re-build. Support themes and plug-ins.

  • Build features for debugging, diagnosis, discrepancy traceback, reconciliation, inconsistency detection, change logs, to satisfy the most demanding users and stubborn auditors

  • Follow super-clean design and development processes to maximise modularisation and maintainability.

  • Factor in automated testing and build test suites in parallel with the code build.

  • Support multiple time zones, languages, currencies, versions of Android and iOS.

  • And do all this from Day One, not as an afterthought.

Scrum: Agile Development

Redesigning project management processes to deliver tighter teams and better projects.

Scrum for fixed-scope projects, where sprint teams work through a burndown chart

  • Any fixed-scope project starts with a detailed, well-crafted WBS, which then becomes the burndown chart.

  • The project manager structures the burndown chart into sprints

  • The team organises itself under a very low-overhead daily stand-up call, which keeps everyone in sync once a day.

  • All code is checked in daily into Git, and issue updates in the task control system make all progress visible.

  • Peer review of code spreads the ownership of each code segment from the individual to the whole team.

  • Sprints are run as watertight mini-projects and the output of each sprint is given to the client for UAT.

  • The entire sprint structure works with the governance processes for good client engagement..