Enterprise Cloud Development and Agile Transformation Strategy - China 2012
•
1 like•1,072 views
This is a seminar I gave throughout China the week of Oct 29th 2012. It covers the topics of Agile Software Development (Scrum, Lean, XP) and the new framework of Enterprise Cloud Development that CollabNet has been socializing. Please contact me for similar private talks at your company.
Recommended
Recommended
More Related Content
What's hot
What's hot (18)
Viewers also liked
Viewers also liked (17)
Similar to Enterprise Cloud Development and Agile Transformation Strategy - China 2012
Similar to Enterprise Cloud Development and Agile Transformation Strategy - China 2012 (20)
More from Laszlo Szalvay
More from Laszlo Szalvay (14)
Recently uploaded
Recently uploaded (20)
Enterprise Cloud Development and Agile Transformation Strategy - China 2012
- 1. Enterprise Cloud Development Emerging Approaches to Software Development and Delivery Laszlo Szalvay VP Worldwide Scrum Business Sunday, November 04, 2012 ENTERPRISE 1 CLOUD DEVELOPMENT Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 2. CollabNet Company Background • Founded in 1999; Headquarters in Silicon Valley. • Global offices in Singapore, Shanghai, Seoul, Tokyo, Chennai, Munich, London, Amsterdam, Seattle, Portland. • Started Subversion project in 2000 • 50%+ Market share for Source Code Management. CollabNet named strategic leader by Gartner and Forrester • Founders include Brian Behlendorf (Founder of Subversion, Apache Project, Mozilla Board member, CTO of the World Economic Forum) and Tim O’Reilly (founder of O’Reilly Media) • Multiple Acquisitions along the way (VA Software, Danube, Codesion) • Primary product today is called TeamForge and is built on top of Subversion • 10,000 companies use our products and services 2 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 3. … Rapidly Expanding User and Customer Adoption… Total Customers Total Users (mm) 12,000 4.0 10,033 3.6 10,000 3.0 3.0 8,000 7,593 2.5 6,000 2.0 1.6 4,000 1.0 0.8 2,000 701 888 464 - - 2007 2008 2009 2010 2011 2007 2008 2009 2010 2011 New Customers 3,000 2,440 2,500 2,000 1,500 1,104 1,000 500 239 187 159 - 2007 2008 2009 2010 2011 3 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 4. Problem Statement We still don’t know what the best way to drive our Application Development • How do we successfully innovate? • How do we maximize scaled, outsourced and/or distributed teams? • Why do so many projects fail? • How do we gather and analyze data? • What is our tool chain strategy? • How and when do we leverage Open Source thinking? 4 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 5. Waterfall an Overview In 1970, Dr. Winston Royce published “Managing the Development of Large Software Systems,” in which the waterfall paradigm was first documented. He said, “I believe in this concept, but the implementation described above is risky and invites failure.” 5 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 6. The problems with phased construction • “Completeness” comes in horizontal slices, not working software • Feedback comes too late to make corrections • The software might meet the requirement, but not the business need 6 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 7. What is Agile? • Made popular in the early 2000s Agility is about a new way of thinking about complex product development and was a reactionary movement to the Waterfall methodology originating in the 1970s • Benefits: – Develop software in iterations – Delivering software increments – Reducing the cost of changes that come late in the game 7 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 8. Application Development Megatrends Dev Ops Continuous Delivery & Deployment • Agile / Lean / Scrum: Broad but shallow Adoption remains • DevOps: Integrated Dev & Ops transforming release management • Cloud: Going Hybrid - spanning public & private cloud IT • 75% Dev / PaaS by EO ‘12 • 50% SW Deployment by EO ‘14 8 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 9. Thought Leader Perspective The thing I have learned at IBM is that culture is everything. Louis V. Gerstner, Jr. former CEO IBM Transformation = disruptive culture change versus Adaption = learning techniques and practices Why is culture so important? Determines your management team Informs your metrics down to your employee selection Your platform & technology choices 9 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 10. Transformation patterns Organic / Viral Transformation Strategic Transformation Accidental Transformation accidental strategic organic 10 . Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 11. Transformation Patterns (part two) Establish Expand Scale • Identify Pilot(s) • Senior Management Alignment • Facilitate enterprise communication • Figure out where you are • Codify Organizational today (Agile readiness Understanding • Manage Change / Release assessment) • Terminology Management Integration • Metrics • Security • Identify Work Streams • Tools • Auditability • Identify Training curriculum • Reporting Formats • Traceability (online and in-person) • Establish internal and external • Establish Governance • Agile Evangelizing Coaching Model • large project parameters (management and others) • distributed project • Create Forums parameters • Sr. Mgmt Engagement • Gating Criteria • Project Selection Criteria (What is Done) • Agile Evangelizing • Reduce Project cycle time • ALM Platform • IP Re-use / Management 11 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 12. Introducing Enterprise Cloud Development ENTERPRISE 12 CLOUD DEVELOPMENT Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 13. What is Enterprise Cloud Development 13 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 14. Embrace Cloud - Consolidate Assets • Provide central access for development & deployment • Securely manage code, documents, conversations • Leverage point and legacy tools • Enforce access control, enterprise- wide 14 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 15. Customer Example: General Motors Multi-faceted approach for centralizing build, test, deploy functions at GM Challenges • Limited visibility & access to 2,000 SW App assets • No framework/tool to collect, store, provide visibility, and govern IP Assets • 5 Tier one vendors Benefits • Centralized repository to manage vendor developed SW assets • ALM solution for internal teams • Mechanism to provide quality scans 15 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 16. Implement Community Architecture • Drive collaborative development (wiki, mailing list & Subversion or git) • Create open source thinking inside your organization (innersourcing) • Organize software projects through Wiki is the oldest and simplest software that lets threaded conversations a community of strangers work together to build • Fast-track project launches something of surprising and lasting value. • Securely on/off-board project members Ward Cunningham through role based access controls Inventor of the Wiki Sent to Laz via LinkedIn in March 2012 16 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 17. Customer Example: USA Government Challenges: •Needed to improve the ability for the United States Dept of Defense (DoD) to rapidly deliver software & services for net-centric operations - Remove the Siloed development environments - Reduce expensive and time consuming start-up - Increase sharing and re-use across DoD projects - Reduce duplication of effort Solution: •TeamForge with Community Management services •Established collaborative development environment - Site taxonomy - Project templates - Standard governance model Benefits: •Agile development and testing •Cross-program sharing: software and services •Early and continuous collaboration •Integrated approach to development life cycle •Extensible platform to support delivery of partner capabilities 17 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 18. Codify Development Processes • Process change agents believe that lasting organizational change can begin with process because of the link between process and culture. • Increase investment in process always shows strong empirical return on investment 18 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
- 19. © 2012 CollabNet, Inc., All rights reserved. CollabNet is a trademark or registered trademark of CollabNet Inc., in the US Laszlo Szalvay and other countries. All other trademarks, brand names, or VP Worldwide Scrum Business product names belong to their respective holders. Laz@collab.net 1-971-506-7862 https://twitter.com/#!/ewok_bbq http://www.linkedin.com/in/laszloszalvay 19 Copyright ©2012 CollabNet, Inc. All Rights Reserved.
Editor's Notes
- Laz to tell his APAC story.Reid Hoffman story
- Competitive time to market pressures and innovation requirements, along with a host of new development and deployment options are resulting in an explosion of applications across a wide range of platforms (e.g., mobile, web, client-server, and embedded). To address the need to manage the development and deployment of this rash of new applications and platforms, industry is integrating 3 megatrends trends into its IT processes– agile, Devops, and the leveraging of hybrid cloud resources.The first trend is the adoption of agile processes. Agile adoption is growing fast and customers are realizing the value. The primary value realized is time to market and productivity improvements resulting from the rapid response to change that agile brings. A recent presentation from Forrester indicates that 40% of all development teams are implementing agile today. But most enterprises still use a hybrid mix of processes, and these companies need methods to manage this wide mix of hybrid approaches.The second megatrend is the convergence of development and operations into what today is being called DevOps. Much of this is actually being driven from the adoption of agile across the organization, and its extension from development into continuous IT service delivery. It’s also being seen in the increased collaboration that’s occurring between development, test, and IT operations staff in many organizations. We’re seeing developers taking more and more responsibility for deployment (as market analyst firm Ovum suggests in the quote included), with operations folks taking on more of an overseeing role. Agility and mixed processes are driving a rash of increasingly frequent application iterations into operations with less inconsistent application delivery processes which is affecting application quality, user satisfaction, and leading to spiraling costs. Companies need an integrated, collaborative, and automated process for managing this increasingly more complex set of application delivery techniques. Automating DevOps is still in its infancy in most enterprises today, but Gartner expects that by 2015, 20% of all large organizations will have merged development and operations processes, up from fewer than 5% today.The third megatrend is the use of the cloud for development and deployment, but more specifically the hybrid cloud. Hybrid cloud development and deployment is the distribution of development, test, deployment, and runtime tasks between on-premise, private and public clouds to optimize cost, performance and productivity. Workgroups from companies of all sizes are seeing the advantages of adopting cloud development and deployment more rapidly across the board than enterprises today as rapid provisioning of services with flexible pricing is offsetting the total cost of ownership of managing their development and runtime infrastructure themselves. The need for the use of hybrid cloud for development and deployment is primarily being driven by larger organizations that are looking to embrace the cloud incrementally in a hybrid way at their own pace, given their existing investments in on-premise tools, applications, and infrastructure. Larger enterprises are seeing a lot of value today, for example, in elastic access to build and test resources in the cloud, and deploying to public cloud PaaS and IaaS platforms, but over time they will look to the cloud for more. While workgroups are experiencing great benefits, this “shadow IT’ is leading to issues in enterprise architecture integration difficulty, lifecycle support costs, IP governance, and enterprise visibility.Saugatuck Research predicts that 75% of new software development projects will be in the cloud by the end of 2012, and 50% of software deployments will be in the cloud by the end of 2014. A flexible enterprise platform to manage agility and DevOps across a wide range of internal and external clouds is a requirement for companies to manage their increasingly diverse application development and platforms.
- Gmail was invented during 20% time
- To address the enterprise issues on the previous slide, new development approaches, technologies and resiliencies must be re-evaluated for the enterprise • to understand and implement realistic spans of control to manage hybrid cloud development and deployment • while still empowering the individual workgroups to work with the “right reusable set” of agile and mixed processes to meet their project objectives Led by CollabNet and its business partners and clients, we have developed this “balanced approach” do to just this – it’s called Enterprise Cloud Development (ECD). Enterprise Cloud Development (ECD) is an emerging IT category that represents the ongoing maturity of cloud development practices. It provides organizations a secure and compliant path to manage development and deployment in a hybrid cloud environment, and enables them to embrace the benefits of the cloud at their own pace. Achieving the large gains of Enterprise Cloud Development has its challenges, and requires a deliberate, well-conceived and well-executed blueprint. The CollabNet ECD Implementation Blueprint outlined on this page provides the approach.We’ve developed this ECD blueprint through a decade of innovative yet practical engagements working with companies of all sizes doing agile development in the cloud. CollabNet has supported customers from a few developers to tens of thousands of developers inside of the same company (i.e. 60K users at Cap Gemini). No other company in our space can speak to that kind of scale in the enterprise. Some development environments of our customers are in our cloud, some are on premise and in customer clouds, and some are actually in a combination of on premise private and public clouds. Depending upon the level of adoption, we’ve seen customers achieve anywhere from 10 to 80% improvements in cost savings, productivity, and time-to-market acceleration (based on the level of adoption of agility, collaboration, and enterprise rollout scale) through the adoption of Enterprise Cloud Development, all while meeting their corporate compliance requirements. Note that both value and enterprise wide collaboration and leverage will increase as organizations adopt the principles outlined in the Blueprint.
- Provide central access for development and deploymentGain control of software assetsConsolidate fractured and disparate teams and assetsCreate a centralized cloud Plug-in and collaborate Securely manage codeProtect IP assetsCentrally manage and securely access code and back-upsGovernance policiesManage all software assetsFormal (code, issues, builds) and informal (discussions, reference material) assetsVersion control, searching, indexing and associationsTraceabilityLeverage point and legacy toolsCommon platform servicesOrchestration and traceability across applicationsEnforce access control, enterprise-wideSecure access across the enterpriseEnforce access compliance
- Drive collaborative developmentOrganize software projectsOrganizational alignment, collaboration and reuseStandard community structures across organizationFast-track project launchesFast initiation of new projects with standard project templatesCodify enterprise development processes with project templatesShorten learning curve with common project templatesSecurely on/off-board project membersManage security across the enterprise – users and projectsEfficiently and quickly on and off-board project membersProvide transparency and traceabilityQuick access to assets and artifactsApplication of corporate security and permissions for searchesTraceability and association with any point in the application development and deployment lifecycle
- Optimization of software development processesCustomer satisfaction by rapid delivery of useful softwareBusiness responsive software development teams Highly motivated self organizing teams Improved productivity and release velocityOptimize pathway from product concept to deliveryImplement integration, automation and practicesSDLC Tools standardizationOptimization of common SDLC tools workflowVisibility and traceability through SDLC toolsProcess streamline through automationImproved visibility of development processProvide software development metricsOptimize communication to business and product stakeholdersImplementation of a visible development and release pipeline