Upgrade to Pro — share decks privately, control downloads, hide ads and more …

The elastic IT organization

Jure
May 04, 2011

The elastic IT organization

Conference JAX 2011 keynote presentation

Jure

May 04, 2011
Tweet

More Decks by Jure

Other Decks in Technology

Transcript

  1. Copyright © 2011 Accenture All Rights Reserved. Accenture, its logo,

    and High Performance Delivered are trademarks of Accenture. The elastic IT Organization by Jure Zakotnik and Thomas M. Michelbach 04.05.2011
  2. Copyright © 2011 Accenture. All rights reserved. 2 How to

    work efficiently in a large IT organization? Thomas Jure If only someone could help me with this MapReduce service... There must be someone in this IT organization knowing Spring.. Thomas http://allmystery.de
  3. Copyright © 2011 Accenture. All rights reserved. 3 • Contribute

    to other projects • Learn new skills • Build our network (quality and quantity) but... • We don't know about each other • We rely on the orgchart • We have no shared development architecture We would like to
  4. Copyright © 2011 Accenture. All rights reserved. 4 The elastic

    IT organization needs three components People & Collaboration Organization & Culture Technology "Without loosing time on tooling" "With enough organizational support" "Let's work together"
  5. Copyright © 2011 Accenture. All rights reserved. 5 The use-case

    Jure Thomas Find each other and collaborate? Develop together using the right architecture?
  6. Copyright © 2011 Accenture. All rights reserved. 6 Collaboration People

    & Collaboration Organization & Culture Technology
  7. Copyright © 2011 Accenture. All rights reserved. 7 • We

    like to work with people, not with –Functional roles and pools –Organizational entities and processes People and Collaboration People are motivated if they can work with interesting teams and people again
  8. Copyright © 2011 Accenture. All rights reserved. 8 Team How

    we find each other today? Jure‘s boss Boss2 Thomas Jure Other contacts
  9. Copyright © 2011 Accenture. All rights reserved. 9 Team Problems

    in current collaboration processes Slow ramp- up for new joiners Long roundtrip times to find right people Jure‘s boss Boss2 Thomas Jure Other contacts Changes in network not transparent (if people leave)
  10. Copyright © 2011 Accenture. All rights reserved. 10 Project Team

    • Skills: Defined and attributed to a person (node) • Context: Emerging from the interaction between people (links) Skills and context are key JAX 2011 Agile Tester, REST Expert
  11. Copyright © 2011 Accenture. All rights reserved. 11 Example: Facebook

    Social Graph Bank project Communication project Business Technology article team
  12. Copyright © 2011 Accenture. All rights reserved. 12 • Freedom

    to tag connections • Connections might decay over time • Integrates with other tools (sharepoints, skill matrix) • Easy management of my graph –Replacement of nodes –Navigation in graph • Shows my company in real-time like a "living organism" Our dream tool
  13. Copyright © 2011 Accenture. All rights reserved. 13 • Managing

    my social graph requires –The skills and understanding –The incentive to maintain it • Generation gap –Digital natives expect to use collaboration tools in a company context (i.e. facebook, twitter) –Old generation is used to eMail, phone, orgcharts Challenges
  14. Copyright © 2011 Accenture. All rights reserved. 14 Implemented using

    neo4j, grails and neoclipse for visualization Implementation of our use-case
  15. Copyright © 2011 Accenture. All rights reserved. 15 The use-case

    Jure Thomas Shared Development architecture?
  16. Copyright © 2011 Accenture. All rights reserved. 16 Organization &

    Culture Collaboration tools enable us to find each other People & Collaboration Organization & Culture Technology √
  17. Copyright © 2011 Accenture. All rights reserved. 17 • In

    a complex IT organization, it is difficult to manage skill allocation • Interesting activities remain unknown until the hooray- announcement • Skilled people are stuck in the section of their orgchart Flexibility of IT organizations IT Java Spring Thomas Other sections Security Help!
  18. Copyright © 2011 Accenture. All rights reserved. 18 • Social

    graph enables visualization of skills with a filter • Self-organization of trending connection tags Tag: MapReduce Organization graph
  19. Copyright © 2011 Accenture. All rights reserved. 19 • Trending

    connection tags create migration of skilled people towards these topics • Indication for Communities of Practice (and potentially organizational entities?) Organization dynamics Tag: JAX 2011
  20. Copyright © 2011 Accenture. All rights reserved. 20 • Activities

    (e.g. user stories) are published in company’s dashboard • Interested people get notified and can join • Activities can be "pulled" • Dashboard could be… –Yammer, Chatter, Tibbr, company-wide community –Pivotal, Scrum dashboard –Twitter, completely open Publishing and pulling
  21. Copyright © 2011 Accenture. All rights reserved. 22 The use-case

    Jure Thomas Shared Development architecture?
  22. Copyright © 2011 Accenture. All rights reserved. 23 • Increased

    transparency in which activities people are engaged • Bottom-up contribution to organizational structures through self-organization • Analytics on graph can provide information on skills and skill dynamics • Management might fear loss of control • Likely to be a hybrid of existing structures and the presented approach Benefits & Challenges
  23. Copyright © 2011 Accenture. All rights reserved. 24 • Self-organizing

    companies –The connected company (Dave Gray) –The end of the middle manager (Lynda Gratton) • Extending beyond the company boundaries –Fraunhofer Open Innovation initiative –Open Source Projects –Accenture Current trends
  24. Copyright © 2011 Accenture. All rights reserved. 25 Cloud-enabled architecture

    The organization supports collaboration Organization & Culture Cloud- enabled architecture People & Collaboration Organization & Culture Technology √ √
  25. Copyright © 2011 Accenture. All rights reserved. 26 • Using

    the Cloud, architecture becomes more flexible • We can clone the complete dev stack for a short time and decommission it again later • Capacity not our problem, we can focus on creative solutions • Common standards for development needed Cloud-enabled architecture
  26. Copyright © 2011 Accenture. All rights reserved. 27 Use Case

    Pull user story Clone environment and support team Develop Find other team and publish user stories Thomas Jure Dashboard + Social Graph Development Environment stack Clone
  27. Copyright © 2011 Accenture. All rights reserved. 28 Cloning of

    dev in cloud Template Sees user story Thomas & Team Clone Link to auto-generate environment CloudFormation GIT Init Repo
  28. Copyright © 2011 Accenture. All rights reserved. 29 AMIs with

    Development Environment Amazon Web Services in action Simple DB • Link in Yammer uses the Amazon CloudFormation template • Use case contains AMIs and SimpleDB
  29. Copyright © 2011 Accenture. All rights reserved. 30 • The

    repository contains –Scripts to initialize dev environment –Test data –Source code • In order to share code and configuration, Git was used –GitHub –Egit plugin for Eclipse Updating the repository
  30. Copyright © 2011 Accenture. All rights reserved. 31 • Technically

    feasible, easy to do • Not expensive We have not solved the problem of missing vertical skills What we have learned Amazon RDS Service $ 0.74 Amazon Simple Notification Service $ 0.00 Amazon Elastic Compute Cloud $ 38.59 Taxes $ 7.46 Total due in US Dollars $ 46.80
  31. Copyright © 2011 Accenture. All rights reserved. 32 Success factors

    People & Collaboration Organization & Culture Technology The Cloud provides the architecture for our collaboration√ √ √
  32. Copyright © 2011 Accenture. All rights reserved. 33 • It

    is not about Agile, Cloud or Social Networks • It is about bringing skilled and creative people together to solve problems • And empowering them with the tools and processes in an elastic organization Vision Summary
  33. Copyright © 2011 Accenture. All rights reserved. 35 • Usage

    of yammer, chatter, tibbr –Publish activities –Facilitate discussions • Focus on twitter-like communication • Tags within conversations • Org-chart functionality limited Tools available
  34. Copyright © 2011 Accenture. All rights reserved. 36 Entrepreneurial Innovation

    through… • A flat, data-driven organizational structure • A “20 percent time” policy • Services and tools to help launch, test, and get user feedback as early as possible • Generous rewards and recognition for successful innovation The Google way Active Projects 2,000 Builds per day 100,000 Code changes 20 per minute Source: “Entrepreneurial Innovation at Google“, Alberto Savoia and Patrick Copeland.
  35. Copyright © 2011 Accenture. All rights reserved. 37 Total Responses:

    673 Potential % Enable speed, flexibility and responsiveness 59% Permanently and significantly lower operating costs 53% Enable new, innovative processes 46% Support product/service innovation 40% Improve decision making 34% Expand operations to new markets 32% Other 1% Cloud computing has no potential for our organization 1% How does Cloud support innovation? Global Cloud Computing Survey, Accenture Institute for High Performance, 2010.