Jem D’jelal


Expert Business Agility Coach

Connect with Jem D’jelal

LinkedIn

About Jem

Jem D’jelal is an experienced Agile Coach and Transformation Coach who has worked with several organizations to drive their agile transformations. In his first experience at Essence, he helped redesign the organization across technology’s 10 teams, creating feature teams where possible and helping existing component teams implement the Kanban method. He also introduced ideas and practices to create collaboration and transparency between multiple agile teams.

At Aimia Inc, Jem worked alongside the CPO and CTO to experiment with the concept of feature teams for a high-profile delivery. He coached several ScrumMasters and Product Owners on refining their application of Scrum practices and using Kanban techniques to optimize the flow of work. He also introduced the ScrumMaster communities of practice, generated and drove Kaizens for any issues and introduced the Agile book club.

In his last experience at Thomson Reuters, Jem served as a Delivery Lead/Scrum Master, leading more than five Scrum teams. He championed autonomy for teams and continually challenged the hierarchical and siloed approach to ‘requirement’ gathering to ensure the people doing the work provided the solutions. Jem broke paradigms of ‘leads’ to reduce the worshipping of tools and come back to Agile basics through communicating interactively.

Published Articles & Case Studies

What do Scrum Masters ACTUALLY do outside of meetings?

Does the aspiration set by the Product Owner come to life in the work that the team do? Or are we spending our time in different places? Let’s look at a simple tactic to figure out what we get done as a team & how this can serve us in starting the right conversations to move towards the desired direction.

Relative Sizing

Quick & Easy 101 estimation for Agile teams

Why is no one speaking in the Retrospective?

 

Lean Coffee

Managing bugs, Swapping Scrum Masters & Story point pain!

Scrum Master: Can you help write Sprint goals?

Scrum Masters provide a service to the Product Owner & that involves helping with the Product Backlog. Specifically in this case, understanding the Sprint Goals. But how do we write sprint goals and why are done so badly? Is there a template for this problem, or do we need to be thinking about something else?

Author