SOFTWARE PRODUCT ENGINEERING

When we build an application, we approach it as if it were a product. This means we prefer configuration over customization. This approach helps us:

• Progress in uncertain requirements
• Build flexibility into the behavior of the software
• Reduce ownership cost by reducing long-term changes to code
• Automate repetitive tasks so you can focus on the intellectual and creative bits

Productivity comes from not repeating the same tasks over and over again manually.

• Built a development environment once? Script away QA, UAT, and production.
• Found a defect? Bake it into a regression test.
• Send a release note every time a master merge happens? Automate the process in the version control tool.

Leave the repetitive tasks to automation so you can focus on the intellectual and creative bits.

An application reflects its domain. So, to build an accurate representation, you must understand the domain. We do this through structured discovery workshops at three levels of granularity: project, release, and iteration.

After that, we carry out a domain decomposition exercise to align teams based on microsegments of the domain. Building teams around microsegments leads to increased decoupling and greater cohesion.

One of the critical aspects of our working principle is to embrace uncertainty. We understand that our customers are not living in a static business environment. They change and adapt as the need arises. Our approach and mindset reflect this belief—we welcome and promote change.

We aim to build greater alignment between business users and the development team. If priorities change, our plans will change.

Small teams formed around domain microsegments are our secret sauce to productivity and ownership. Decision-making is decentralized to the empowered decentralized teams. We tune all our internal processes towards empowering our people—hiring, onboarding, L&D, you name it.

Our secret sauce is our people, who make self-organizing teams possible.

A picture is worth a thousand words, they say. A UI artifact helps build a ubiquitous language between end users, domain experts, and the development team. We ideate, iterate, and align on the UX before embarking on the build.