Microsoft Visual Studio's Journey to Continuous Delivery
Microsoft Visual Studio is now releasing at a much faster pace and the Team Foundation Service has a deployment every sprint. We adopted agile practices across the board and made significant improvements to engineering processes and systems down the way. What are the impediments to agile and how you overcome them. How do you reimagine the role of developers and testers in this new era. What kind of tools do you need to make this transition a success for your team ?
Come and learn what it takes to adopt modern processes to ship complex products like Visual Studio with engineering teams spread across the globe to ship at cloud cadence.
Outline/structure of the Session
The structure of the session is pivoted around the journey of Visual Studio from 2005 onwards when we used to have longer release cycles to now when we ship every 3 months for our on-prem product and every 3 weeks for our online service.
- Visual Studio Team - Common Challenges with large distributed team development
- 3 Waves of learning - Techincal Debt (2005-2008), Amplified flow of Value (2008-2011), Improved Cycle Time (2012 and beyond)
- Modern Practices and Modern ALM for Continuous Delivery (Talks about Agile Lifecycle to enable continuous Delivery)
The key takeaways of the sessions are to believe that one can be succesful adopting agile practices for complex products like Visual Studio. Also some tips around how one can overcome common challenges when one goes down this journey.
The session is meant for decision makers to understand the challenges and solutions in adopting agile practices for complex products. At the same time it also caters to agile team members to understand how to put the processes into practice to deliver cus
schedule Submitted 3 years ago
People who liked this proposal, also liked:
Scaling XP Practices inside your organization using Train-the-Trainer Model
How do you effectively scale skill-based, quality training across your organization?
Over the years, I've experimented with different ideas/models to scaling skill-based training across an organization. In the last 4 years, I've pretty much settled down on the following model. Its very useful when mentoring teams on skills like Test-Drive-Development (TDD), Behavior-Driven Development (BDD), Product Discovery, Writing User Stories, Evolutionary Design, Design Patterns, Problem Solving, etc. I've successfully implemented this model at some very prominent fortune 500 enterprises.
The goal of this workshop is to explore what other successful models organized have used to scale skill-based training in their organization.
Continuous Deployment for iOS Game Development
"Release Early, Release Often" is a proven mantra and many companies have taken this one step further by releasing products to real users with every commit a.k.a Continuous Deployment (CD).
Over the years, I've built many web/infrastructure products, where we've effectively practiced CD. However at Edventure Labs, when we started building iPad games, we realized there was no easy was to practice CD, esp. given the fact that Apple review takes a few days.
Our main question was: As mobile app developers, how should we architect/design our apps for CD?
We were a young startup, learning new behavior about our users (kids aged 5-8) everyday. We could not afford any delay in releasing latest, greatest features to our users. To solve this problem, I believe we've built an innovative solution to enable any mobile app developer to achieve CD.
If you are building real products, which have platform/3rd-party dependencies and you want to practice CD, this session is for you.
SAMPLE PROPOSAL - Product Discovery Workshop
Many product companies struggle with a big challenge: how to identify a Minimal Viable Product that will let them quickly validate their product hypothesis?
Teams that share the product vision and agree on priorities for features are able to move faster and more effectively.
During this workshop, we’ll take a hypothetical product and coach you on how to effectively come up with an evolutionary roadmap for your product.
This 90 mins workshop teaches you how to collaborate on the vision of the product and create a Product Backlog, a User Story map and a pragmatic Release Plan.
This is a sample proposal to demonstrate how your proposal can look on this submission system.