Chronicles of a Scrum master #20 : The end of a journey and the start of another

Being a scrum master for the past few years, I am extremely grateful to be given the opportunity to guide, educate and motivate several product teams. This has allowed me to be a better servant leader.

In my previous journey, as a first time line manager with direct reports, there were long hours and many lessons learnt. Some of the most valuable points were the following :

  • Customer focus is important, be it internal users or external customers.
  • Open team communication and collaboration must be ever present and excellent to ensure there are actions that can be taken up and completed.
  • Agile is also a mindset as well as a path towards continuous improvement and delivering value over outcome.

By end of August 2023, I will end my tenure as a scrum master in my current company after several years in this position. The next path will bring me in as a scrum master and technical delivery expert.

Throughout this years, being focused on being an excellent scrum master, here are several important areas that I would like to impart to my avid readers :

  1. Be patient and resilient. Don’t be overcomed or distracted by ‘noises’ outside of the team.
  2. The path maybe difficult at times but bear with it and every step will be a lesson that will enrich you in life and experiences.
  3. Focus on the team well-being. Don’t let others influence you or your thoughts on team members. Find out for yourself the truth by having regular 1 on 1s.
  4. Work closely with your team and peers. Build rapport and relationship with those outside the team.
  5. Coach the team to be goal and result oriented. Internal team relationship must be built up and maintained together with open communication. Have an on-boarding with new joiners and off-boarding with those who are leaving the team to get their feedback.

Signing out for now, Jason.

Agile Scrum master

Chronicles of a Scrum master #19 : User stories guide to better development and further refinement

In the world of agile, requirements come in the form of user stories and it is important to understand that the details contained in the stories are needed to absolute clarity for anyone who is going to be working to get this stories done. Consequently, here are several practices which can be adapted to organizations […]

Read More
Agile Scrum master

Chronicles of a Scrum master #18 : Measuring agile

Agile development is fundamentally about the delivery of value to customer via a iterative and incremental process. This value can be a perceived or tangible value, depending on what the end goal is. Hence, in order to measure the success of an Agile project or product, it is imperative to establish the objectives and end […]

Read More
Agile Scrum master

Chronicles of a Scrum master #17 : Technical debt and Support tickets

In agile way of working, technical debt is still present as the team goes about completing stories based on definition of done. What then exactly is technical debt ? This is the accumulation of previous known anomalies, which were not discovered previously before release. It can be in the form of bugs, design changes, code […]

Read More