Planting Seeds...

1) Train in-house coaches to take over in a tactical coaching role (I'd have started this at the beginning). I generally expect there to be a guild of Scrum Masters at the core.
2) Train an agile governance or PMO function to provide organizational assurance of the Scrum process, both at team levels and at scale. The remit would include Scrum compliance (eliminating Scrum-but), and may include strategic coaching either directly or as an allied function. Again, this is best started at the beginning.

As the adoption has gone well and the product receiving a lot of visibility, this is indeed their own experience of success.

Take a photo with the Teams and share the photo to the team. That’s all.

Maybe you can give them your phone number. :)

Also try and get a case study out of this, preferably one which allows the client to be named. Ask for permission to do so now while there's a warm glow.

Hey Nitin,

Well done!


I agree with Ian.
Planting the seed is more than a good experience with one isolated team, it is leaving behind someone (a Scrum Master Guild) to continue the good flow and spread the (correct) agile way.
And the seed needs to be watered to grow. So make sure, the top management understands why the project was successful.


Also you can sell them a follow up project for scaling to the full.
(Or multiple projects, depends on the size of the company...)


Sebastian

I surely agree with Ian and Sebastian.

But I have a different point of view.

If the timing is before leaving, it is better to emphasize and recall the Team’s experiences of success.
There might be few chance to say training or coaching, especially when the Team just finished a big job.

I think the most valuable gift is your phone number for a new Scrum Team you coached.

If the timing is after leaving, write a letter of thanks to the MO.
Let the MO understand why the project was successful "AGAIN", and don’t forget to mention the outstanding Scrum Team you coached.

> write a letter of thanks to the MO. Let the MO
> understand why the project was successful
> "AGAIN", and don’t forget to mention the
> outstanding Scrum Team you coached.

That's a good idea. Such a letter of appreciation to one or more key stakeholders, especially if hand-written, is quite likely to be remembered and could help influence future outcomes.

Well done Nitin! Some great ideas here for you to take away.

I would also help the team create their own metaphor to help guide the team through into the future of turbulent or exciting times - a vision of high performance. The journey never ends ...

Thanks for the great feedback, folks!

My apologies for not writing sooner, but here are a few things I did --

+ Was in ample pictures with the Team (there was a paparazzi enthusiast!)
+ Offered my contact information
+ Encouraged and offered a path for formal training
+ Offered availability to HR on anything I could help with
+ Wrote and personally thanked some people who were "Managers" of Dev Members
+ Sporadically checked in a little after I left
+ Left some lightweight material to read
+ Offered my insights to various levels of the organization, including the CTO
+ ...and some other trinklets along the way

I do like the idea of getting permission for a case study. However, a more opportune time may be as the initiative is wrapping up completely.