Your SlideShare is downloading. ×
Keeping the spin - from idea to cash in 6 weeks (ICGSE2011)
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

Keeping the spin - from idea to cash in 6 weeks (ICGSE2011)

283
views

Published on

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
283
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
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. ©2011TietoCorporationKeeping the spin– from idea tocash in 6 weeks.ICGSE 2011Jaroslav Prochazka, Marcin KokottConsultantsTieto, Delivery and Qualityjaroslav.prochazka@tieto.com,marcin.kokott@tieto.com
  • 2. ©2011TietoCorporationTietotoday• Net sales approximately EUR1.8 billion• Listed in NASDAQ OMX Helsinkiand Stockholm• Founded in 1968Tietotoday• 18 000 IT professionals in close to30 countries• Customers on all continents• One of the leading IT servicecompanies in Northern Europe andglobal leader in selected segments
  • 3. © 2011 Tieto CorporationWho we are• Delivery Mentor Network• Core of the network• 8 coaches• 9+ years in IT (developers, architects, PMs)• Have been supporting transformations in different industries in last 5 years inTieto• Representing Tieto at international IT conferences3 2011-07-18
  • 4. ©2011TietoCorporationStory Context4 2011-07-18
  • 5. Market challengesCustomers requires following (Forrester, 2011)• Innovation and proactivity• IT should bring more business value• Aligning vendors’ goals with customer ones• Additional Dutch unit challenges• Traditional way of working followed• Global Delivery Model started recently emphasized• Chaotic communication and lack of project visibility• Lack of coordination causing delays and rework• Micro-management of Indian colleagues• Decreasing motivation• Lower customer satisfaction2011-07-18Context TrainingCrashcourseLessonslearnt
  • 6. © 2011 Tieto CorporationOur world is distributed (outsourcing)Dutch TeamPune TeamLow-cost broad-bandcommunication channelHigh-cost narrow-bandcommunication channelBoundaryspannerBoundaryspannerAmbassadorAnalystArchitectureDesign&CodeTesting
  • 7. ©2011TietoCorporationTrainingsessions7 2011-07-18
  • 8. © 2011 Tieto CorporationIntroduction training• Agile game as key part of this training• Learning by doing• Practical experience you can refer to when explaining concepts• Game experience ensured guys to start without our help• They received "practical experience„• Sales training created awareness8Context TrainingCrashcourseLessonslearnt
  • 9. © 2011 Tieto CorporationGlobal Delivery Awareness• Dutch people disappointed by cooperation with Indian colleagues• Big surprise! Different cultures• Hofstede’s model presented• Typical situations presented and explained• It was fun and they finally understood…9Context TrainingCrashcourseLessonslearnt
  • 10. © 2011 Tieto CorporationNext steps• Dutch culture made it interactive workshops• We came back to our office and stayed in touch• Few discussions and FAQ sessions• Dutch team have decided to run new project Agile …… but they have hit some struggles10Context TrainingCrashcourseLessonslearnt
  • 11. ©2011TietoCorporationOne WeekCrash Course2011-07-18
  • 12. © 2011 Tieto CorporationCrash course• Constraints:• Limited time to spent with the team (1 week) + 2 mentors availible• No possibility to „stop” to conduct the planned change• Our original approach haven’t fit• 14 weeks framework• Our experience: months to pass12Context TrainingCrashcourseLessonslearntNew approach needed !
  • 13. © 2011 Tieto CorporationCrash course13„A rapid and intense course of training or research (usually undertaken in anemergency); "he took a crash course in Italian on his way to Italy"; "his first jobwas a crash course in survival and in learning how to get along with people"; "acrash programme is needed to create new jobs„”Kaikaku (jap. „radical change”) means a radical change,during a limited time, of a production system.
  • 14. © 2011 Tieto CorporationSet-up• Small teams• Co-located, cross-funcitonal (also with coaches)• 1 week sprints• Culture, opennes, willing, highly innovative• …and authority• Toolbox (Practices, MCIF)• Mentors in place for complete iteration14Context TrainingCrashcourseLessonslearnt
  • 15. © 2011 Tieto CorporationGlobal co-operation• Limiting narrow communication channel• Teams connected by interfaces• Architecture around functionality/components• Kick-off with the whole team (stable velocity -> distribution)• Discuss even the mood• Personal relationships• „Co-location”• Participating in each meeting• Open window15Context TrainingCrashcourseLessonslearnt
  • 16. © 2011 Tieto CorporationInnovation16
  • 17. © 2011 Tieto CorporationInnovation• Visualize• Rapid learning cycles (also for mentors)• Instant feedback to the mentors• Also from team, customer• Simplify• Even change of WoW• Progress and status• Kaikaku• Breaking the habbits... and as side effect - fears• Open minded (TDD)17Context TrainingCrashcourseLessonslearnt
  • 18. © 2011 Tieto CorporationRadiators18
  • 19. © 2011 Tieto CorporationContract vs. results19Measure ResultsKeeping Schedule 32,7%Keeping Workload 46,2%PAI (Project Accuracy Index) 49,0%…but…Happy customer having more than requesting!Customer want us to develop another part of fucntionality in this way ofworking Customer selected Tieto as one of the sub-contractors for the biggestproject in Netherlands Telecom & MediaCustomer internal chnage started to be „more agile and alligned withour way of working”
  • 20. © 2011 Tieto CorporationCustomer results• Know the customer• Visiting the customer• Customer glasses• Customer and team driving the backlog• Stable flow as the enabler• Limiting work in progress• Ownership of the whole flow• Results KPIs vs Value created for the customer• Feedback from Controller and people• Software used by bigger group than originally planned• "New way of working" should be used in the customer premises more20Context TrainingCrashcourseLessonslearnt
  • 21. © 2011 Tieto Corporation21„We now use the functionalities which we didn’t figure out in the beginning of theproject. We removed functionalities which we thought we needed. We have seenweekly progress which helped us to think with the users instead of thinking for theusers. We were apart of the solution and feel proud of the result.”Customer representative„Of course the productivity went up because we all were aware of eachother’s work and we know where the overlap was and avoidedthis [...] And the funny thing is, in the end, they didn’t pay much attentionto the FD, they rather trust the demo results.”Business Consultant
  • 22. ©2011TietoCorporationLessons learnt22 2011-07-18
  • 23. © 2011 Tieto Corporation…and above lessons learned• IT and Business synergy• Visibility, transparency, control• Overcoming the fear!• …PEOPLE23
  • 24. © 2011 Tieto CorporationQuestions?24 2011-07-18
  • 25. ©2011TietoCorporationJaroslav ProchazkaMarcin KokottConsultantsTieto, Delivery and Qualityjaroslav.prochazka@tieto.com, marcin.kokott@tieto.com