Scaling Professional Scrum with Visual Studio Team Services

Audience

Everyone

Last week I was teaching a Professional Scrum Foundations in Farnborough and I had to make sure that I got a hotel with awesome internet access. As well as teaching the class I Have two additional tasks for the week. The first was to have the honour of talking on ScrumPulse, Scrum.org’s webcast, and the second was to talk at the prestigious Dutch ALM Meetup.

Both topics were the same with “Scaling Professional Scrum with Visual Studio Team Services” but the interactivity and available time was substantially different with only really 45 minutes in the webcast and nearly 3 hours for the workshop.

Scaling Professional Scrum with Visual Studio Team Services Webcast

Tools don’t solve problems, but they can help reduce the friction of Scaling Professional Scrum. The only way to successfully scale across multiple teams, maybe in multiple countries, is to create robust automation and orchestration for minimizing the risks, and time, of manual tasks. Visual Studio Team Services allows you to create a robust, platform agnostic, support structure that can start where you are, and grow as your needs mature. One Scrum Team, One Nexus, or many…

See how it grows…

You can also view the slides from docs.com

Before viewing the webcast please make sure that you have familiarised yourself with the Nexus Guide. I did not have time to go through the entire process and focused instead on how you might implement a single Nexus in VSTS with suggestions on how to implement many Nexus.

Although there were over 800 registrations for the event the meeting software only supported 100 participants. If you were signed up and were unable to attend then you can view the recording. Scrum.org is looking at options to support the larger number of participants in the future.

The event was recorded, and has been published as “Scaling Professional Scrum with Visual Studio Team Services” on the Scrum.org YouTube channel. We also have published the slides for you as well.

Scaling Professional Scrum with Visual Studio Team Services Workshop

Find out how to organize many teams of work in VSTS within a Nexus (3-9 teams) and control what data is shown to who. Martin will introduce Nexus as a compliment to Scrum and demonstrate how to setup VSTS to support it, then let you get your hands dirty…

This time no other than Martin Hinshelwood will join us for an interesting evening around Scrum for Team of Teams. Martin is an independent consultant at nkdAgility (https://nkdagility.com/) and runs his own business at customers all over the world.

Conclusion

While there are many tools out there to support Scrum only Visual Studio Team Services really support scaling scrum to the enterprise. If you have many teams working together on a single product then there is no better tool at scale than Visual Studio Team Services.

Get in touch if you want me to speak at a User Group, if I am going to be in your area then let me know!

Create a conversation around this article

Share on Facebook
Share on Twitter
Share on Linkdin

Read more

Martin Hinshelwood
In organizational development and team dynamics, Agile (as the Agile Manifesto delineates) and Scrum (as the Scrum Guide outlines) guide teams not by solving their problems but by illuminating the issues that demand attention. These frameworks aim to identify and spotlight the challenges within a team or organization’s processes, effectively …
Martin Hinshelwood
This week, I participated in a Scrum.org Webinar hosted by Sabrina Love (Scrum.org Product Owner) as well as my colleagues, Joanna Płaskonka, Ph.D. and Alex Ballarin to discuss the state of learning and how immersive learning is the future of training. You can watch the video below to hear what …
Martin Hinshelwood
For a long time now I have been searching for that perfect domain that epitomised the vision, the why, of what I am trying to achieve with my customers and the industry at large. Now I have found it in http://nkdagility.com
Martin Hinshelwood
At the MVP Summit I was appalled by the number of people who asked questions about new features for supporting hierarchical tasks! I shared a disgusted look with Peter Provost and we had a quick (and I mean really quick) conversation that resulted in this post. it really comes down …