Back to Forum

Scrum Transformation path to eSAFE agile

Last post 06:11 pm June 9, 2023 by Ian Mitchell
1 reply
Vignesh Saravanan Lakshmanan
08:14 am June 9, 2023

Hi,

In my organization we have 5 different projects holding team members from 2 different vendors and working in 2 week sprint( though the sprint window varies for each project). Each team also holds one PO from the client side and SM from Vendor.

Earlier, we had a transformation journey in adaption of agile from Waterfall methodology, wherein, training commenced in a ring fenced manner.

The coaching started with the identified team members and then moved to PO and Business ( both PO and Business were from client side). It was extremely challenging to change the mindset during the initial stage, but the development team got adapted to the scrum practices and they are following it showing a progressive improvement.

At the moment, our organization has 2 challenges.

(a) Though we are practising scrum, the PO's and Business are not ready to completely follow. They participate reluctantly and the burden increases to SM who also need to align with PO in framing the Product backlog items ( with the guidance and supervision from PO)

(b)  The 5 working team has some interdependencies for which the SM's decided to progress towards the eSAFE agile.  We are aiming that many of the inter dependent items could be identified earlier and effectively planned for progression. But we are not having the visibility on the steps/ transformation journey to transform our current agile team to adapt this scrum of scrum. Need assistance on the steps /stages to be adapted to achieve this milestone.

 

Thanks.

 

Ian Mitchell
06:11 pm June 9, 2023

Scrum Transformation path to eSAFE agile

I'm not sure there is one. There are transformational paths to implementing Scrum. If that was the objective, however, the Scrum Master would not be framing Product Backlog items. Also, rather than delegating to a Scrum of Scrums, the Developers on each team would co-ordinate and manage their integration dependencies for themselves. What you've described might actually be the avoidance of a transformational path which achieves such things

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.