# data[].attributes.body
The HDB Scrum Master Sharing event provides a platform for Scrum Masters in Singapore to exchange experiences and expand their knowledge. On November 22nd, I gained insights into the challenges faced by HDB, including evolving public expectations and demographics, rapid technological advancements, and paramount security concerns. I discovered that HDB manages a substantial volume of transactions and inquiries each month, averaging 170,000 counter transactions, over 100,000 phone inquiries, 60,000 correspondences, 25,000 appeals, and 20,000 house listings. Subsequently, I was introduced to the Agile Method, formalized in 2001 by 17 software engineers. The Agile Method is characterized by its principle-based, iterative approach, ongoing requirements discovery, and responsiveness. Additionally, I was exposed to notable frameworks such as Kanban, Scrum, XP Programming, and others. I also gained a comprehensive understanding of DevSecOps, including its history, principles, and three core practices.

# data[].attributes.body
I had the privilege to attend a Scrum Master Sharing by HDB. I managed to learn about the issues faced by major companies and how they overcome them. i learnt about agile, a project management and product development approach that emphasizes flexibility, customer satisfaction, continuous improvement, and high team involvement.

# data[].attributes.body
The talk covered topics like Waterfall vs Agile, the Agile Manifesto, Scrum and DevSecOps and many more. Through the sharing, I gained a deeper understanding and appreciation for the agile methodology. I’ve learnt that Scrum aims to control chaos when developing a project. For example, having periodic checkups/meetings like the daily standup and sprint retrospective will ensure that everyone is on the same page and knows what to do and what to improve on. Similarly, scrum time boxing will ensure that the team deliver when the deadlines come. I also found it interesting that major companies are shifting the way they structure each department to enable their employees to be more efficient.

# data[].attributes.body
The ADO talk by HDB provided valuable insights into the dynamic realm of scrum master practices.

agile is an improved version of working methodology than waterfall, as agile provides iterative feedback, and working in small increments of its product.

dev ops =/= dev sec ops. in recent years, security is also an important feature to be considered, hence the addition of security development of data pipelines/software engineering.

the role of scrum is not easy, orchestrating a project amidst potential chaos. scrum is sometimes only discussed in theory, but in the real world, it is still less used due to the challenges like resistance to change, a lack of understanding and training of scrum, etc.

during a weekly standup sprint review, members in the dev team can find it hard to share their difficulties faced. it is never easy to really ask for help for the members.

Overall, the talk has shed light on how major companies like HDB are reshaping their organisations, to enhance productivity and lessen risks of failure, by adapting data operation methodologies in place.

# data[].attributes.headline
HDB Scrum Master Sharing - Geraldine Koh

# data[].attributes.subject
HDB Scrum Master Sharing - Geraldine Koh

# data[].attributes.body
We attended a HDB Scrum Master Sharing on November 22nd by Mr Chen Xuanyi. He shared about scrum methodology such as Agile that we are learning in class. He also shared information on Scrum, the team and their operations. I learnt more about the processes and obstacles that are likely faced. Agile can be confusing, and that is where the scrum meetings and reviews come in place, ensuring everyone is on the right track. He also showed us the company hierarchy and where the Scrum teams belongs. I learnt new roles such as the COO,CFO and the different departments below them. Overall, the talk was really educational.

# data[].attributes.body
There are 2 different methods of agile, Waterfall and scrum method. All project managers are to handle chaos. Agile Manifesto focuses on individual and team beliefs, scrum focuses on how teams organise themselves for work and DevSecOps focuses on how to make work flow seamlessly. DevSecOps start off as cultural movement to bridge and development and operations team. The 3 ways of it is systems thinking and principles of flow, Amplify feedback loops and continuous learning & experimentation. The team structure of a scrum consist of sales department/production department which are the business users, product owner, scrum master, tech lead and 6 full-stack engineer. Thre is an interation loop where it consist of 4 cycles (try something, analyse outcome, improve based on insights, repeal). The nature of undertakings are fixed cost, fixed deadline, limited manpower, outsourcing and contracts. There are also ongoing changes where users are uncertain about what they want. These 2 lists has tension among each other. Dev Team 1 is the scrumban style where its focus is to develop public user fronting web app. the current nature of project is migrating one part on-prem to cloud, more fixed than loose requirements and fixed deadlines. The chaos control mechanism is no. of tickets in progress and it focus on closing. Dev Team 2 is scrum style where its focus is developing internal user web app. The nature of the projects are new initiatives, looser requirements than fixed and looser delivery date. The chaos control mechanism is 2 weeks timeboxing and sprint backlog. The cloud platform team follows the scrum style and its focus is developing commmon system services, distill cloud best practices and evangelise the above within organisation. its current nature of project is new initiatives, technology integration focus for common services, looser requirements than fixed and looser timeline. The chaos control mechanism is 2 weeks timeboxing and sprint backlog.

# data[].attributes.body
In this talk ive learnt a lot more about how Agile is implemented into HDB's team. Some things that were covered were:

values

individual and iterations

working software

customer collab

responding to change

Some principles that he highlighted were:

working with customers closely

sponsors, developers and users work together at a constant pace indefinitely

Simplicity (most things can be simplified)

He also covered the different types of scrum each team employs and their objectives:

Default Scrum:

Control chaos using time boxing and incremental development

DevSecOps

Scrum is not practised according to what we learn

The Product Owner knows the project the most

Possible new structure with delivery manager instead of scrum master, Infra team, security, DB, and other existing traditional team

Scrumban Style (dev team)

follows standard scrum ceremonies

Kanban in task management

chaos control: focus on closing, no of tickets in progress

focus on developing a public user-fronting web app

Scrum Style (dev team)

follows standard

scrum's way of task management

chaos control: 2 weeks timeboxing, sprint backlog

focus on developing an internal user web app

Cloud Platform Team: Scrum Style

focus on developing common system services