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…
https://www.youtube.com/watch?v=7o8YuisXZzc&w=768&h=432
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.
- Slides: http://nkdagility.net/dutch-alm-nexus
- Meeting: http://www.meetup.com/Dutch-Microsoft-ALM-Group/events/228588973/ This was done as an interactive 3 hour workshop with live hands on with Team Services. As this meeting was live only I can only refer you to the webcast above. However if you want me to come and do this workshop at your User Group then please let me know.
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!
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Big Scrum: All you need and not enough
Explores how to scale Scrum effectively by applying agile values, fostering professional teams, and adapting processes to fit unique …
My journey into Professional Scrum
Reflects on experiences with Professional Scrum, highlighting its impact on software development, team culture, training, and the challenges …
NDC London 2014: Why TFS no longer sucks and VSO is awesome
Overview of improvements in Team Foundation Server (TFS) and Visual Studio Online (VSO), including updated features, cloud integration, and …
Scaling Agility: Navigating the Dragons of Change in the Future of Work
Explores practical strategies for scaling agile practices, key metrics, virtual training adaptations, and global insights to navigate change …
Mastering Agile in a Distributed World: Tools and Strategies for Effective Team Management
Explore practical tools and strategies for managing Agile teams in distributed environments, including communication tips, tool comparisons, …
Professional Scrum Courses for 2016 in Oslo, Norway
Details 2016 Professional Scrum Master and Developer courses in Oslo and Kongsberg, covering advanced Scrum, coaching, DevOps, and Agile …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …