Your SlideShare is downloading. ×
0
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Beyond agile transition
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Beyond agile transition

129

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
129
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. www.devbliss.com © devblissWe deliver software and services that delight ourcustomers, sprint by sprint.Friday, April 26, 13
  • 2. NATO | INTERSHOP | WEB.DE | CDC |VZ | DEVBLISSTRAINING | CONSULTING | MANAGEMENT | COACHINGFriday, April 26, 13
  • 3. Friday, April 26, 13
  • 4. once upon a time...Friday, April 26, 13
  • 5. ... there was a social networkFriday, April 26, 13
  • 6. VZ - The CompanyManagementSoftwareEngineeringProductDevelopmentCustomerCareMarketingLegalHumanRessources AccountingPublicReleastionsSalesFriday, April 26, 13
  • 7. VZ - The CompanySoftwareEngineeringProductDevelopmentFriday, April 26, 13
  • 8. ➡ 32 Software Engineers➡ 3 Operations➡ 4 Scrum Masters➡ 2 Management➡ lead by Dr. Johann Kempe (CIO GvH) and Stephen Devlin (CTO Macmillan)➡ very strong agile mindset➡ 6 month preparation to carve out➡ Since May 1st 2012 we operate independent from VZdevbliss todayFriday, April 26, 13
  • 9. ➡ registered Users: 17 Million / 80% monthly actives➡ dynamic requests per month: 60 billion➡ delivered static Objects per month : 50 billion➡ peak time bandwidth: around 6 Gbit/s➡ Photos: approx. 1 Billion (3 Billion Files)➡ 120 TB structured and unstructured data➡ approx. 740 Servers (5700 Cores, 6 TB RAM)➡ around 30 services and tools➡ used programming languages:Java, Erlang, Python, PHP, Perl, C, C++, Objective C, Scala➡ approx. 25.000 (mySQL) TablesOur experience through VZFriday, April 26, 13
  • 10. Friday, April 26, 13
  • 11. Achievements of the last 3.5 years➡ Releases possible at any time➡ Shorthand changes are less painful➡ Less meetings - focused communication➡ Team members feel responsible and holdthemselves accountable for their work➡ Crowd architecture➡ Knowledge transfers within and between the teams➡ Prioritization - important things first (business value)➡ Very good code quality and development speed➡ decisions are made by the people who do the workFriday, April 26, 13
  • 12. Friday, April 26, 13
  • 13. Why do companies want scrum or agile?➡ shortens time2market➡ enhances productivity➡ optimizes processes➡ creates (painful) transparency➡ motivates employees➡ makes the company attractiveFriday, April 26, 13
  • 14. Transition will succeed only,if the organization breaks its "regular" habit.Friday, April 26, 13
  • 15. “…organizations which design systems … are constrained to produce designs whichare copies of the communication structures of these organizations”.Henry E. Conway April 1968ABCABCORGANIZATION=SYSTEMConways LawFriday, April 26, 13
  • 16. PlanDoCheckActThe Deming-Cycle - Key to the agile mindsetFriday, April 26, 13
  • 17. Educate ProductOwner(s)➡ PO = OWNER! of the product?➡ Whats my Vision!?➡ UserStories?!??➡ Prioritization➡ Backlog / Company BacklogFriday, April 26, 13
  • 18. ➡ Facilitator➡ Mediator➡ Organizer➡ Mentor➡ TherapistHave ScrumMaster(s)Friday, April 26, 13
  • 19. Prepare the Team➡ has to have the strong willingnessto change something➡ has to take over responsibility &➡ has to be aware of being held accountable➡ might also reject changesKeep in mind: Initially Scrum was meant for hyper-performant teams!!Friday, April 26, 13
  • 20. Fear of changefear of beeing transparent➧ avoid giving any meeting the look likethey are in place for reportingunwilling to take overresponsibility➧let the team make decisionsthemselves and hold themaccountable for them.„Nonsense“Disregarding the benefits➧Scrummaster must facilitate.Teams are recognizing the benefitfairly quickly.That does not fit the way wework➧search for Interfaces/interactions thatallow to fit in, but dont compromiseon the Rules (see 2nd comment)Talk, Talk, Talk…… do retrospectives on regular base and try to reduce the fears.Talk, Talk, Talk…… do retrospectives on regular base and try to reduce the fears.Talk, Talk, Talk…… do retrospectives on regular base and try to reduce the fears.Friday, April 26, 13
  • 21. afraid of makingmistakes ➧ Mistakes are expected! Repeated mistakes are unwanted.to say "No"➧ accept a „No", take away pressure,create transparency of whats the real velocitynot getting it done➧solving technical debt will result in a lower velocity. Let peopleget a feeling of their own velocity and accept commitmentsbut also demand those commitments.to change processesthat remaineduntouched a long time ➧ Convince people of the benefits and empower themChange with no fearFriday, April 26, 13
  • 22. Have A Transition Team:➡ Drives change throughout the wholeorganization➡ „Powerful“ Support for the ScrumMaster➡ Defines Interfaces between departments➡ Creates transparency throughout the companyFriday, April 26, 13
  • 23. Prepare Management➡ let the Boss/Client FEEL the improvements➡ learn how to handle the reporting tools toavoid a bad gut feeling➡ handle Uncertainty = reporting-artefacts inscrum are sufficient enough!➡ enforce lean managementFriday, April 26, 13
  • 24. Dont lie to yourself!➡ We certainly moved and changed (after the first sprint)➡ We "adjusted" the scrum process to fit our organization.➡ enough change, we need to work now.➡ the Teams are delivering new features constantly but we had toemploy a new bug-manager.Friday, April 26, 13
  • 25. ➡ Create a sense of urgency➡ Create the guiding coalition➡ Develop a vision and a strategy➡ Communicate this vision➡ Empower employees for broad-based action➡ Generate short-term wins➡ Consolidate the gains and produce more change➡ Anchor the new approaches in the cultureJohn P. Kotter Leading ChangeFriday, April 26, 13
  • 26. Friday, April 26, 13
  • 27. www.devbliss.com © devblissWe deliver software and services that delight ourcustomers, sprint by sprint.Friday, April 26, 13

×