
> **Recap:** Our long-awaited visit to SP Group revealed that digital transformation in large enterprises faces more cultural than technical challenges. We discovered that successful partnerships require treating external engineers as part of one team, and that effective engineers need to understand industry-specific problems beyond just coding solutions.

We've always wanted to visit [SP Group](http://spgroup.com.sg/), one of our partners, but the pandemic made it impossible until now. This year, the opportunity finally came when we decided to attend Echelon X in Singapore.

Meeting the SPG team in person was insightful and rewarding. We learned more about the challenges of digital transformation for enterprises, remembered why SPG chose to work with us, and saw how we could promote a growth mindset for our engineers.

Plus, our friends at SPG make amazing soju beer bombs.

Everyone in our team for this visit would have their own takeaways, but a few things resonate with all of us.

- For a partnership to work, all engineers from SPG and Dwarves should act as one team. SPG treats our team as their own, which helps our collaboration. They train and lead everyone together, fostering unity.
- SPG showed us that digital transformation is more about people and their ways of working than technology. There's a gap between the tech department and the rest of the organization. True transformation starts by overcoming resistance to change and fostering a culture of learning and adaptability.
- SPG is so large that each department operates almost like an independent company. Employees are deeply rooted in their established workflows, and introducing new technology often feels like adding more work rather than simplifying it.
- Data security is a big concern at SPG. Internal teams have strict, lengthy processes to access data, and it's even harder for external partners like us. While AI and other tech are being discussed, the main issue is keeping data safe. Engineers must be aware of security and privacy, often dealing with regulatory challenges.
- While adopting trending tech like AI and AR is great, the real challenge is using them to solve business problems. What sets top engineers apart is their ability to understand industry-specific issues and use technology to address them.

All in all, visiting SPG for us reinforced our direction of how we should grow our team and how we should look at the bigger picture of the tech scene. Engineers need to expand their perspectives beyond just coding.

We are greatly grateful for how welcoming and open the SPG team was to us. We look forward to continue contributing to the changes SPG is making every day.

![Dwarves team with SP Group in Singapore](assets/sp-group-wala.webp)

---

**WALA: to walk around, learn around.**

In our line of work, we hear and talk about domain knowledge all the time. WALA aims for exactly that: we, people in tech, take a break from sitting in front of our computers, to go out, connect with new people, and get to understand other businesses.

Through stories collected from Techie WALAs, we hope our community members get the chance to learn from others' successes and failures, gain insights into what works and doesn't, and reflect on their own works and practices.

Besides, breaking away from the stereotype of "tech people are introverts" is always fun.


Our visit to SP Group offered valuable perspectives on enterprise digital transformation challenges. We learned that successful transformation depends more on people and organizational culture than technology, while strong partnerships require treating external teams as part of your own.

SP Group

#3 Digital transformation insights from the energy sector


In personal finance, the strategies we choose to manage our money can significantly impact our financial future. These strategies typically fall into three categories: saving, investing, and speculating. Each comes with its own levels of risk, timeframes, and methods. Understanding the distinctions and appropriate uses of each can guide us in making smarter financial decisions.

## What Are saving, investing, and speculating?

**Saving** involves putting money aside in secure forms like savings accounts or CDs. It’s characterized by very low risk and variable timeframes, suitable for short-term financial goals or as an emergency fund.
**Investing** is the process of purchasing assets, such as stocks, bonds, or real estate, with the expectation of long-term appreciation and profit. Investors take on moderate risks and typically aim for gradual wealth accumulation.
**Speculating**, on the other hand, involves taking significant risks for the potential of substantial, rapid returns. It’s often short-term and can involve high-volatility instruments like cryptocurrencies and options.

## Key differences

| Aspect    | Saving           | Investing            | Speculating       |
| --------- | ---------------- | -------------------- | ----------------- |
| Risk      | Very low         | Moderate             | High              |
| Timeframe | Variable         | Long-term            | Short-term        |
| Approach  | Regular deposits | Fundamental analysis | Market timing     |
| Mindset   | Security focus   | Growth focus         | Quick gains focus |

## Strategies and risk management

Effective financial management often involves utilizing all three strategies at different points in one’s life or simultaneously, depending on financial goals and risk tolerance.

### Saving

- **Goal**: Safeguard capital, ensuring funds are available when needed.
- **Method**: Regular contributions to savings vehicles.
- **Risk management**: Emphasizes capital preservation, low-risk instruments.

### Investing

- **Goal**: Accumulate wealth through appreciation and returns on capital.
- **Method**: Buy and hold assets, diversify across different investments.
- **Risk management**: Uses diversification to mitigate risks.

### Speculating

- **Goal**: Achieve significant profits in a short time frame.
- **Method**: Engage in frequent trades, often in high-risk markets.
- **Risk management**: Involves aggressive strategies, accepting the possibility of high losses for potential high returns.

## Conclusions: practical advice

Understanding your **risk tolerance** is crucial in choosing the right strategy. Thorough research is essential, especially for investing and speculating. Your **investment horizon**—whether you’re planning for the long term or looking for quick gains—should guide your choice of strategy.

Diversification remains a fundamental principle of risk management across all types of financial strategies.
Remember, whether saving, investing, or speculating, tailor your strategies to align with your personal financial goals and risk appetite. Each method has its place in personal finance management, but they must be used wisely and with informed judgment.


In personal finance, the strategies we choose to manage our money can significantly impact our financial future. These strategies typically fall into three categories: saving, investing, and speculating. Each comes with its own levels of risk, timeframes, and methods. Understanding the distinctions and appropriate uses of each can guide us in making smarter financial decisions...

Understanding saving, investing, and speculating: key differences and strategies


**Industry**\
E-commerce

**Location**\
Vietnam and Southeast Asia

**Business context**\
Needed a better e-commerce platform to make dropshipping operations simpler and more efficient

**Solution**\
Built a modern, upgraded online system with improved user experience and business tools

**Outcome**\
Successfully launched Droppii for Business v3.0 that business users love, with better controls and insights for managing their operations

**Our service**\
Full-stack development / Agile project management

## In brief

Droppii teamed up with us to improve their e-commerce platform for dropshipping businesses. We built a new version called Droppii for Business v3.0 that's easier to use and helps businesses manage their operations better. The new platform includes a cleaner dashboard, better content management, and improved business tools. This upgrade has helped Droppii grow in the competitive e-commerce market and deliver more value to their users.

## Challenge

Droppii needed to update their platform to keep up with the changing e-commerce industry and support their growing business. Their existing system, which was quickly built during their early "90 Days Rushing" phase, couldn't handle their new needs anymore.

While Droppii's team was strong in backend development and handling business data, they needed help with creating a better user interface and expanding their development team. They were looking for a partner who could both build great technology and manage the project efficiently.

We started by taking a close look at Droppii's existing systems, how they managed their product, and their workflow. This helped us create a plan for building a user-friendly, scalable platform that would serve their business needs better.

## Solution

Droppii and our team worked together in two main phases to rebuild their platform:

In the first phase, our developers worked closely with Droppii's team to quickly build and launch Droppii for Business v3. This new version worked smoothly across web, iOS, and Android platforms, with an easy-to-use interface that made sense for their business users.

For the second phase, we focused on adding more advanced features. We built a new dashboard that gave users better visibility into their business, a content management system that made updating information easier, and upgraded their business management tools. We also kept improving the design to make everything more intuitive. To ensure everything worked properly, we set up automated testing that integrated smoothly with Droppii's existing systems.

## Outcome

Our partnership with Droppii produced great results. Business users responded positively to the new Droppii for Business v3 platform. The improved business tools and data management features gave businesses better control over their operations and more useful insights.

![Droppii for Business v3.0 interface showing the main dashboard with product management features](assets/droppii-business-dashboard.webp)

This project did more than just improve Droppii's technology – it strengthened their position in the e-commerce market. Our technical expertise and flexible approach to development played a key role in this transformation, helping Droppii adapt and grow in the fast-changing world of online commerce.

## Impact

Working together, we showed how combining technical skills with strategic planning can dramatically improve a business's online platform. By focusing on creating an excellent user experience and efficient operations, we not only improved how Droppii works today but also built a foundation for their continued growth and innovation.


We helped Droppii upgrade their e-commerce platform with a new user-friendly version that makes dropshipping easier for businesses. Working together, we built Droppii for Business v3.0 with a better dashboard, simplified content management, and improved business tools that led to positive user feedback and stronger market position.

Droppii

Helping Droppii build a better dropshipping platform that users love

When we conduct an estimation, it is recommended to abandon the transitional “exact hours” assessment method, instead, use the story point based on the Fibonacci number (1, 2, 3, 5, 8, 13, 21…). The number expresses an estimation of the overall effort required to fully implement a backlog item or any piece of work.

Below’s an example of an estimation table based on the matrix of complexity, uncertainty, and effort:

| Story Points | Reference | Uncertainty | Risk | Efforts | FE Example | BE Example |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ |
| 1 | 1. Stories that take < 0.25 day to complete 2. Stories that only involve FE OR BE 3. Stories that is clear, no need to investigate/find root cause | Low - 100% Clear | Low | Less than half a day: 1 hour or less | Small UI update that doesn’t require BE work: - Color, Font, Positioning that doesn’t require relayout - Sorting (no BE work) - Only impact 1-2 screens/controls | - Configurations only |
| 2 | 1. Stories that take < 0.5 day to complete 2. Stories that is more of FE OR BE work, the other is minimal 3. Behavioural work, involve calculation/ logics | Low - Involves some changes to current calculation/logic | Low | Around half a day to 1 day | - Calculate/Sum/Count numbers - Small UI change but on multiple screens (3 or more) | - Minor changes to existing API (Add/edit/remove fields...) - Minor change on calculations to current API |
| 3 | 1. Stories that take around 1 day to complete 2. Change behavior/calculation/logic of current function that we need to rework the function 3. New calculation/logic that is different than existing default from sources | Low - Need to spend time to check the logic/calculation/ reproduce | Low | Around 1 working Day | | |
| 5 | 1. Stories that take 1-2 days to complete 2. Only need single/simple new endpoint to complete 3. Little or no migration data needed 4. Little or no DevOps involvement | Low - Medium Some clarification needed but the main flow is clear | Medium | Around 3 working Days | | |
| 8 | 1. Stories that take half a Sprint to complete 2. New feature that requires multiple endpoints/screen 3. Need some research to figure out solutions 4. Migration data needed 5. Medium Server/DevOps involvement | Medium - High - Completely new feature - Need some research to figure out solution | Medium → High - Follows current architecture design - Might impact other feature(s) - Might need migration of data | Around 5 working Days | | |
| 13 | 1. We are not sure if it works 2. Need leaders to take a look into new approach/solution and test to see if it works 3. POC work 4. Architecture change and/or new coding approach | High - Research/POC/ Architecture Stories | High - We are not sure if it work or not | If cannot deliver in a working week, please break it down | | |

When we conduct an estimation, it is recommended to abandon the transitional “exact hours” assessment method, instead, use the story point based on the Fibonacci number (1, 2, 3, 5, 8, 13, 21…). The number expresses an estimation of the overall effort required to fully implement a backlog item or any piece of work.

Estimation guidelines


## Weekly activities

### Weekly points/effort report

**Every Friday**

- **Action**: Fill out the weekly points/effort report.
- **Link**: [Weekly Report Spreadsheet](https://docs.google.com/spreadsheets/d/1KXUVyDrC9199Dp6wpT6ovIkIvZRtf455eaqwZmvTAFU/edit#gid=0).
- **Deadline for data sync**: Data is sync by EOD next Tuesday.
- **Outcome**: Weekly leaderboard on delivery.

![](assets/project-schedule-delivery-guidelines_project-delivery-schedule-and-guidelines-20231205231343953.webp)

### Sync-up between project lead and delivery manager

**Every Friday at 2:30 PM**

- **Topics**:
  - Project Health: Wins, Losses, Future Plans.
  - Milestone Progress.
  - Changelog for the week (will be sent out the following Monday.)

![](assets/project-schedule-delivery-guidelines_project-delivery-schedule-and-guidelines-20231205231409927.webp)

## Bi-weekly and monthly activities

### Project demo/showcase

**Every 3rd Wednesday**

- **Audience**: Consulting and Labs team.
- **Goals**:
  - Update on current projects.
  - Insights about the market and real projects.
  - Celebrate monthly wins.
- **Recap**: Sent out the following week and highlighted in the monthly community call.

![](assets/project-schedule-delivery-guidelines_project-delivery-schedule-and-guidelines-20231205231433316.webp)

### Community call

**Last Friday of the Month**

- **Contents**:
  - Delivery Monthly Report.
  - Demo/Showcase Recap.
  - Monthly Leaderboard of Delivery.
- **Rewards**: ICY reward and NFT Badge benefiting the holder's achievements.

![](assets/project-schedule-delivery-guidelines_project-delivery-schedule-and-guidelines-20231205231500387.webp)

### Project collect feedback

For every 3 or 6 months, by **Monday of the 1st week from the 1st month**, Delivery team or Project Leader will send out an email to client to gather feedbacks for our Dwarves members through this form: [Feedback Form](https://docs.google.com/forms/d/e/1FAIpQLScVkRDy9w5_j_Tkj2MXs2Yi_n8yTUqNNBqy8w1-E3Beauodsw/viewform)

**What we can collect from this form?**

- Metrics: to evaluate our members if they are working effectively or not.
- Start Stop Continue doing feedback model: to understand how we can improve our delivery better.
- Leadership metrics: how effectiveness on the management from our Team Leader and Team Members.

## Important reminders

- **Weekly report completion**: Complete the report every Friday. For estimation help, check [estimation-guidelines]().
- **Project achievements**: If you have significant milestones or cool aspects of your project, notify the Consulting team for potential demo/showcase inclusion. Recognition is guaranteed.

![](assets/project-schedule-delivery-guidelines_project-delivery-schedule-and-guidelines-20240122161522695.webp)


Dwarves Foundation Team's guide on our project delivery process. This post will serve as your go-to resource for understanding our weekly, bi-weekly, and monthly activities, ensuring that we stay on track and excel in our deliveries as well as handle feedback.

Project delivery schedule and guidelines


**Industry**\
Beverage Technology

**Location**\
Australia / New Zealand

**Business context**\
Keg rental company needed advanced tracking technology to reduce asset loss

**Solution**\
Built a cloud-native platform with real-time tracking and comprehensive analytics

**Outcome**\
Delivered a reliable system that helps breweries maintain visibility of their kegs throughout the supply chain

**Our service**\
Backend development / Cloud architecture / DevOps

## Technical highlights

- **Cloud architecture**: Kubernetes with GitOps for scalable infrastructure
- **Backend**: Custom geolocation API in Go for cost-effective tracking
- **Performance**: Redis caching with third-party services for improved response times
- **Monitoring**: Sentry, Prometheus, Grafana, and Loki for comprehensive system visibility
- **Deployment**: Continuous delivery with ArgoCD for zero-downtime updates
- **Infrastructure**: AWS EKS for reliable, scalable cloud hosting

## What we did with Konvoy

Konvoy came to us with a vision to revolutionize how breweries track and manage their kegs. Beer kegs are valuable assets that frequently go missing, costing breweries significant money each year. Konvoy wanted to create a tech-driven rental system that would solve this problem.

We partnered with them to build a platform that provides real-time keg tracking and analytics. This system helps breweries maintain visibility of their assets throughout the supply chain, reducing losses and improving their bottom line.

By combining modern tracking technology with flexible rental options, Konvoy offers breweries a compelling alternative to purchasing and managing their own kegs. Their solution helps customers save money while gaining better insights into their keg utilization and movement patterns.

![Konvoy keg tracking system showing asset locations on a digital map](assets/konvoy-main.webp)

## The challenge Konvoy was solving

Breweries face a common challenge: kegs frequently disappear in their supply chain. Traditional tracking methods are manual and inefficient, leading to lost assets and wasted money.

For breweries, these losses represent a significant expense:

- Each keg costs hundreds of dollars to replace
- Manual tracking systems are labor-intensive and error-prone
- Limited visibility makes it difficult to identify where losses occur
- Inventory management becomes increasingly complex as a brewery grows

Konvoy launched in Australia and New Zealand in October 2019 to address this issue. By October 2020, they had integrated comprehensive keg services into their business, combining innovative technology with industry expertise.

Their solution offers breweries flexible options:

- Short-term keg rentals for one-way trips with transparent pricing
- Long-term leasing that frees up capital businesses would otherwise spend on buying kegs

With a focused mission to track every keg's location, Konvoy helps breweries reduce losses and increase profits. Their team of 30 professionals provides exceptional service and maintenance, minimizing keg downtime.

To make this business model work effectively, Konvoy needed a robust technical platform that could reliably track thousands of kegs across multiple locations while providing easy-to-understand data for both their team and their customers.

## How we built it

We created a robust technology platform that could handle the complex requirements of real-time keg tracking and management. Our approach focused on building a reliable, scalable system that would grow with Konvoy's business.

### Technical approach

**Cloud-native architecture**: We built the entire system using Kubernetes on AWS EKS, creating a platform that could scale seamlessly as Konvoy added more kegs and customers. This approach provided:

- Automatic scaling during peak usage periods
- Improved system reliability with self-healing capabilities
- Easier deployment of new features and updates
- Better resource utilization and cost efficiency

**Custom geolocation services**: We developed a specialized geolocation API in Go that significantly reduced costs compared to commercial mapping services. This custom solution:

- Processed location data more efficiently
- Reduced external API costs by handling common queries internally
- Maintained accuracy while improving performance
- Scaled automatically based on demand

**Performance optimization**: We implemented Redis caching with third-party services to reduce costs and improve response times. This was particularly important for:

- Handling high-volume tracking data
- Generating real-time location updates
- Creating history views of keg movements
- Supporting analytical queries without performance degradation

**Continuous deployment**: Using GitOps with ArgoCD, we established a deployment pipeline that allowed Konvoy to release new features and fix bugs with zero downtime. This approach ensured:

- Reliable, consistent deployments
- Automatic rollbacks if issues were detected
- Full visibility into deployment history
- Improved development velocity

**Comprehensive monitoring**: We implemented a complete observability stack with Sentry, Prometheus, Grafana, and Loki to quickly identify and resolve any system issues. This monitoring system provided:

- Real-time alerts for potential problems
- Detailed performance metrics
- Comprehensive logging for troubleshooting
- Visual dashboards for system health

![Konvoy dashboard interface showing keg tracking analytics](assets/konvoy-dashboard.webp)

### How we collaborated

Our partnership with Konvoy spanned two years and involved close collaboration with their team. We established clear communication channels and regular check-ins to ensure the project stayed on track and aligned with their business objectives.

Key aspects of our collaboration included:

- Regular planning sessions to prioritize features and improvements
- Knowledge transfer to help their team understand the technology
- Clear documentation of system architecture and components
- Responsive support for addressing operational issues
- Iterative development based on user feedback and business needs

This collaborative approach ensured that the technical implementation supported Konvoy's unique business model and helped them deliver maximum value to their brewery customers.

## What we achieved

Our partnership with Konvoy over two years delivered significant improvements to their platform:

**Smooth cloud migration**: We carefully moved their system from EC2 to Kubernetes EKS, improving scalability and management. This migration:

- Reduced infrastructure management overhead
- Improved system reliability
- Enabled more efficient resource utilization
- Provided better support for future growth

**Containerization**: We modernized their applications for better efficiency and easier deployment. This transformation:

- Standardized the deployment process
- Reduced environment-specific issues
- Improved development velocity
- Made it easier to roll out updates

**Enhanced monitoring**: We implemented the PLG stack (Prometheus, Loki, Grafana) for comprehensive system health tracking. This monitoring system:

- Provided early warning of potential issues
- Gave insights into system performance
- Helped identify opportunities for optimization
- Improved overall reliability

**Better user experience**: We completely redesigned the admin dashboard to be more intuitive and visually appealing. The new interface:

- Made it easier to track keg locations
- Provided clearer data visualizations
- Simplified common management tasks
- Improved overall usability

**Major performance gains**: We dramatically improved the speed of fetching keg location history and routes, reducing response times from tens of seconds to just seconds. These optimizations:

- Enhanced the user experience
- Allowed for more complex analytics
- Supported larger data volumes
- Improved system responsiveness

These improvements have helped Konvoy provide a more reliable, efficient service to breweries across Australia and New Zealand, supporting their mission to transform keg management with technology. By creating a robust, scalable platform, we've helped Konvoy establish themselves as an innovative leader in their industry, providing a solution that delivers real business value to their customers.


We helped Konvoy create technology that makes tracking and managing beer kegs simple and efficient. Their solution combines smart tracking with flexible rental options to help breweries save money and reduce lost kegs.

Konvoy

Making keg management smarter for breweries


**Industry**\
Banking and finance

**Location**\
Southeast Asia

**Business context**\
Needed to modernize wealth management services as part of digital transformation

**Solution**\
Built a backend system that connects new customer-facing platform with legacy systems

**Outcome**\
Successfully launched a streamlined digital investment platform that improved user experience and operational efficiency

**Our service**\
Tech consulting / Staff augmentation

## What we did with CIMB

We helped CIMB Malaysia, one of Southeast Asia's leading banks, create a modern digital platform for their wealth management services. Our team focused specifically on building the backend foundation that connects their new customer-facing application with their existing banking systems.

The project was part of CIMB's larger digital transformation initiative aimed at improving how customers manage their investments, particularly through their ASNB (Amanah Saham Nasional Berhad) investment products. By making these services more accessible digitally, CIMB could better serve both their preferred and mass-affluent customers.

Working alongside CIMB's team and our partner Netizen, we delivered the technical backbone that powers this new digital experience, helping the bank set new standards in Malaysia's digital banking landscape.

![CIMB's digital wealth management platform interface](assets/cimb-wealth-platform.webp)

## Technical highlights

Our work centered on creating robust backend systems that could reliably connect CIMB's new platform with their existing infrastructure:

- **Java Spring Boot**: We used this framework for building the core backend services
- **MySQL**: For database management and data storage
- **API Gateway**: We built a custom gateway to manage communication between different systems
- **Legacy integration**: Developed connectors to work with CIMB's existing databases and APIs

This technical approach ensured the new platform would work reliably while maintaining compatibility with the bank's established systems.

## The challenge CIMB faced

CIMB Malaysia needed to keep pace with rapidly changing customer expectations in banking. Their existing wealth management services weren't meeting the digital-first demands of modern customers.

The main challenges included:

- Their investment processes required too many manual steps and branch visits
- Customers couldn't easily track or manage their investments through digital channels
- Relationship managers lacked efficient digital tools to help their clients
- Legacy banking systems made it difficult to create new digital experiences

The bank needed a solution that would make investment management simpler and more accessible for customers while working seamlessly with their existing backend systems.

## How we built it

Our approach focused on creating solid backend foundations that would support CIMB's customer-facing improvements.

### Technical approach

We concentrated on two key areas:

**API Gateway Construction**: We built a flexible API gateway that serves as the communication hub between different parts of the system. This gateway manages data flow between the customer-facing application and CIMB's core banking systems, ensuring secure and efficient information exchange.

**Legacy System Integration**: We created custom connectors that allow the new platform to work with CIMB's existing databases and APIs. This was crucial for maintaining data consistency and ensuring that customer information remained accurate across all systems.

### How we collaborated

Working on a project with multiple stakeholders required careful coordination. We established a clear communication structure:

1. **Quick team formation**: We rapidly assembled a team of senior engineers from our talent network who had the right skills for this financial project.
2. **Three-party collaboration**: The project involved Dwarves, Netizen (design partner), and CIMB's team working together. We set up:
   - Regular alignment meetings to keep everyone on the same page
   - Clear documentation of responsibilities to avoid overlap
   - Direct communication channels with developers for quick problem-solving
3. **Progress tracking**: We maintained a weekly changelog that documented all new features, fixes, and changes. This kept everyone informed about progress and facilitated feedback.

This structured approach helped us deliver quality work while meeting the project timeline.

## What we achieved

The collaboration between CIMB, our team, and Netizen produced significant results for both customers and the bank:

**For customers:**

- A more intuitive interface that makes managing investments easier
- Self-service options that reduce the need for branch visits
- A consistent experience that works for both younger and older users

**For CIMB:**

- Reduced manual processing, increasing operational efficiency
- Position as an innovator in Malaysia's digital banking space
- A more flexible technical architecture that can adapt to future needs

The new wealth management platform represents an important milestone in CIMB's digital transformation journey. By building strong technical foundations, we helped the bank create a system that not only improves today's customer experience but can also evolve to meet future banking needs.


We helped CIMB Malaysia transform their wealth management services by building a robust backend system that connects their new user-friendly platform with existing bank systems, enabling customers to manage investments more easily.

CIMB

Building CIMB's digital wealth platform for better customer experience

### Behavior driven development (BDD) Three Practices

- First, take a small upcoming change to the system – a User Story – and talk about concrete examples of the new functionality to explore, discover and agree on the details of what’s expected to be done.
- Next, document those examples in a way that can be automated, and check for agreement.
- Finally, implement the behaviour described by each documented example, starting with an automated test to guide the development of the code.
 The aim is to:
- make small changes rapidly
- back up 1 level when need more info
- automate and implement a new example to get feedback
 BDD Example:

```
- Feature: User Login
*As a user I want to login into the Company's website using my existing account so that I can use other features*
- Scenario Outline: Login with valid credential
Given I navigate to <Company Login Page>
When I input <Username>
and I input <Password>
and I click Login Button
Then I should be able to login successfully
- Examples:
| Email | Password
| abc@company.info | password 1
| abc2@company.info | Password@
```

> Personal note on implementing BDD and TDD:
>
> - Mistakes are that people only implement BDD/TDD practices at **Testing phase** when they implemented automation test. However it should be as early as possible. Using "BDD" to only cover automation test is not **BDD**.
> - BDD helps products and developers realize different scenarios of a same feature, then cover as much as they could at requirement and implementation phase.
> - BDD borrows _ubiquitous language_ concept from domain driven design so that everyone in the team can understand the term the same way.

Source: <https://cucumber.io/docs/bdd/>

Behavior driven development (BDD) is a software development process that encourages collaboration among developers, QA, and non-technical stakeholders.

Behavior driven development


**Project: Archive**

- [ ] Collect and put all artifact to Google Drive.
- [ ] Write a case study to share experience.
- [ ] Thank you and ask for referral if possible.
- [ ] Update audience database.


The checklist shows how the project will be archive

Project archive


The case study should focus on what the audience want to read

**Non tech Client**
The clients want to know if you have capability to deliver their things

- [ ] Does it reflect the problem, solution and value proposition from the Dwarves?
- [ ] Does it show the familiar / personas of previous client?
- [ ] Does it contain the demonstration of final delivery?

**Tech Manager & Potential new hire**
The tech guys want to know how cool you are in tech perspective

- [ ] Does it contain the technical challenge?
- [ ] Does it contain the system design & architecture design?


The checklist outline the criteria of a project case study article

Project case study


**Transparency**

- [ ] Email communication should follow [email communication and use](https://www.notion.so/3703ec7baf5d438fb817175044898c7b?pvs=21).
- [ ] Work related discussion which is common knowledge for the team must be discussed in the public/shared channel
- [ ] In case the work related discussion which is common knowledge for the team is unintentionally chat privately, the person should update with the related people or the rest of the team

**Professionalism**

- [ ] The message sent out should be professional and polite in any case
- [ ] Avoid NSFW chat in work related discussion
- [ ] Be responsive to the discussion
- [ ] Avoid ignoring people. There should be at least a signal for getting back later
- [ ] Loop the related people if the discussion need him/her
- [ ] No swearing
- [ ] Do not babble in the discussion in which you do not have any responsibility.


The checklist shows the rule of communication in a project

Project communication


**Source code**

- [ ] Detailed diagrams created.
- [ ] Source code up to standard.
- [ ] All tests must be passed prior to the handover.
- [ ] Provide HOW-TOs to guide the new member to the development process.
- [ ] New team member has been able to compile, run, test, deploy code to all involved systems.
- [ ] Code walkthrough done.
- [ ] New member has written and deployed code to QA without supervision. It could be a bugfix or small feature.
- [ ] New members know how and where to find information why certain design/implementation decisions are done.
- [ ] Do pair programming for at least 1 hour (an old member with a new member).
- [ ] Code review time is scheduled weekly.


The checklist shows the process of project handover

Project handover


**Paperwork**

- [ ] NDA (depends on clients)
- [ ] Legally signed Agreements ([hellosign.com](http://hellosign.com/) for the e-contract)
- [ ] All related papers such as agreements are put on Drive

**Process**

- [ ] Resources prepared and ready
- [ ] Got deposit after the agreements are signed (depends on the agreements)
- [ ] Communication channel setup
- [ ] Task and project management tool setup
- [ ] Project meeting scheduled
- [ ] Requirements are clear
- [ ] Project init and setup


The checklist shows the process of project initialization