• Save
Real world experience from Microsoft - Deniz Ercoskun
Upcoming SlideShare
Loading in...5
×
 

Real world experience from Microsoft - Deniz Ercoskun

on

  • 1,182 views

Microsoft developer division has implemented SCRUM while developing Visual Studio 2012, and TFS 2012. In this talk we will cover information on this implementation. You will learn about why Microsoft ...

Microsoft developer division has implemented SCRUM while developing Visual Studio 2012, and TFS 2012. In this talk we will cover information on this implementation. You will learn about why Microsoft has decided to implement SCRUM, best practices that was helpful for us. How implementing SCRUM has changed our cadence and product delivery cycle. The content will be our developer division SCRUM journey. We are not pure SCRUM put at future leavel we are. I will also discuss which part of our process is SCRUm which part still is not.

Statistics

Views

Total Views
1,182
Views on SlideShare
629
Embed Views
553

Actions

Likes
1
Downloads
0
Comments
0

4 Embeds 553

http://agileisrael2013.com 394
http://agileisrael2014.com 132
http://www.agilesparks.com 26
http://www.agilesparks.co.il 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Cover: Don't worry about swapping out the image. Shorter titles can sit on two lines.
  • Agenda: Update with what you'll be covering in your session, typically wordedthe same as your section breaks.
  • Need some really good examples here… stories.
  • Why 3 weeks?Four weeks felt like a LONG time.Two weeks was very quick. Too much overheard.Three weeks fit our cadence and our schedule – it worked in our environment.
  • Closing page: Include your contact information and any social-media handles you’d like!

Real world experience from Microsoft - Deniz Ercoskun Real world experience from Microsoft - Deniz Ercoskun Presentation Transcript

  • Real World Experiences fromMicrosoftDeniz ErcoskunMicrosoft CorporationDPE Developer Tools Lead for MEA
  • Istanbul
  • IstanbulRedmond
  • Developer Division• Visual Studio• Team Foundation Server• .net• SilverlightWhich group?
  • Quality MilestoneAfter VS 2010 shipped
  • The Box & The Service
  • The Box• Multi-year cycles• Milestones and stabilizations• Debt
  • “Firms today experience a much higher velocity ofbusiness change. Market opportunities appear ordissolve in months or weeks instead of years.“Diego Lo Giudice and Dave West, ForresterFebruary 2011Transforming Application DeliveryWhy agile in the first place?
  • 1.Our Roles2.Our Organization3.Our Teams4.Our Cadence5.Our Plan6.Our PracticesOur Experience
  • Our RolesProgram Manager – Responsible to ensure we’re building theright thing.Development – Responsible to ensure we’re building productsthat are fast, reliable, and well engineered.QA – Responsible to ensure we’re building high quality productsthat meet customers needs.
  • Our OrganizationProgram Manager Development QA
  • Our TeamsProgram Manager Development QA
  • Our TeamsQADev QADev QADev QADevPM PM PM PMCollaboration Version Control Build Work Item Tracking
  • Sprint CadenceWeek 1 Week 2 Week 3
  • What’s Changed?6 weeks10 – 12 weeks3 weeks
  • 3 Week SprintsSprint 43Sprint 44Sprint 45Sprint 4642
  • 3 Week SprintsWeek 1 Week 2 Week 3 Week 4Week 1 Week 2 Week 3Sprint PlanningBacklogGroomingDeployment!Sprint PlanningBacklogGroomingDone!
  • Sprint Mechanics
  • Same code base used for bothWork in a single branchGated checkin only buildsRolling test system, including upgrade testsDisruptive changes integrated at the beginning of a sprintMerge to production branch, quarterly update CTPsThe service and the box
  • How about at Scale?Sprint 43Sprint 44Sprint 45Sprint 4642
  • Team ChatsTeam Chats Team Chats Team Chats3 questions:1. What’s next?2. How’s the team doing?3. Any issues?
  • Team ChatsCollaboration Version Control Build Work Item Tracking
  • Our Plan18 month vision
  • What does the work look like?Scenario –Alarge initiative in a release.Experience –An end-to-end set of userstories.User Story –Arequirement capturingthe role, functionality, and value.Task – Work the team does to fulfill aStory.ExperienceUser StoryTask
  • Work Items
  • Bugs
  • Rolling Tests
  • Waterfall• Big picture planning• Design• SpecsRules We FollowScrum• Sprint Planning• Daily Standup• Cross-functional teams• RetrospectivesKanban• Visual Tracking• WIP Limits
  • Rules We Break Waterfall• We change ourminds… a lot!• Design• SpecsScrum• No Sprint Reviews• Rotating Scrummaster• Bug tracking• Deploy one week afterthe sprintKanban• WIP Limits• Iterations• Schedule
  • What is the Value?
  • Our Delivery Cadence3-week service delivery sprintsFrequent updates for on-premise/boxed productsSeptember 2012 October 2012 November 2012 December 2012 January 2013……April2013
  • Cultural changeBuild an environment where your teams will thriveShip frequently!Measure alwaysTestUse Team Foundation Server Summary
  • Thank youDeniz ErcoskunMicrosoft CorporationDPE Developer Tools Lead for MEA
  • The service and the box• Same code base used for both• Work in a single branch• Gated checkin only builds• Rolling test system, including upgrade tests• Disruptive changes integrated at the beginning of a sprint• Merge to production branch, quarterly update CTPs
  • Differences• Service scales differently• Need cost model• Multi-tenant database• All content goes to Azure Blob Storage
  • Differences• Tight loop with support• Online upgrades• Automated deployment• No down time between cycles – engineering backlog